Asymmetry Exception Register¶
Register — instantiates Directed Asymmetry Mapping and Calibration
A standing log of every asymmetry the system has chosen to keep — each entry carrying its justification, its owner, and its expiry — so no differential treatment survives unexamined.
Asymmetries accumulate quietly — an exception granted here, a privileged access there, a differential rule adopted for a good reason nobody wrote down — until no one can say which are still justified. Asymmetry Exception Register is the standing ledger that prevents this: every deliberate departure from symmetric treatment gets an entry recording what differential is in force, why it was warranted, who owns it, and when it must be re-justified or expire. Its distinguishing discipline is the default it enforces — symmetry unless registered: an asymmetry with no entry is treated not as grandfathered but as a defect to be removed or documented. It is a system of record, not a judge; it stores the warrant that other mechanisms produce and makes sure it is never quietly lost.
Example¶
An international airport controls access to its secure areas — ramps, baggage systems, the tarmac — and a large set of workers legitimately need it: baggage handlers, fuel crews, maintenance, some airline staff. That access is a real, warranted asymmetry between credentialed and non-credentialed workers, but left untracked it rots: contractors finish a job and keep their badges, staff change roles, a vendor's pass outlives its contract. The register fixes each credential as an entry — the specific zones it opens, the relevant difference that justifies it (this person fuels aircraft), the accountable owner (the employer of record), and an expiry tied to the contract or role.
When the contract ends, the entry lapses and the badge with it, by default — rather than persisting until an audit years later finds a stranger with tarmac access. The register does not decide who should be credentialed; it guarantees that everyone who is holds a recorded, expiring warrant rather than a forgotten one.
How it works¶
- One entry per deliberate asymmetry: the differential in force, the relevant-difference warrant behind it, an accountable owner, and an expiry or review date.
- A hard default of no entry, no asymmetry: un-registered differential treatment is flagged for removal, not tolerated on inertia.
- Entries expire by default; continuation requires an affirmative re-justification, never silence.
What distinguishes it is that it is storage-and-default, not evaluation: it does not generate warrants or hear appeals — it holds the record and enforces the clock.
Tuning parameters¶
- Registration threshold — how significant an asymmetry must be to require an entry. Too low and the register drowns in trivia; too high and consequential differentials slip under the bar.
- Expiry default — how long an entry lives before forced re-justification. Short expiries keep the list honest but cost review effort; long ones let stale exceptions persist.
- Warrant depth — a one-line reason versus a full relevant-difference argument per entry. Deeper warrants are harder to fake but raise the cost of every grant.
- Ownership granularity — a named individual versus a team as the accountable owner. Named owners are more answerable; teams survive turnover.
- Lapse behavior — whether an expired entry fails safe (asymmetry auto-revoked) or merely flags for review. Fail-safe is stricter; flag-only avoids disruption but relies on follow-through.
When it helps, and when it misleads¶
Its strength is defeating the drift by which "temporary" asymmetries become permanent and untraceable: by demanding an owner and an expiry per entry, it makes every differential answerable to someone on a clock. It pairs naturally with least-privilege regimes, where the register is what keeps granted exceptions from silently outliving their reason.[n1]
Its central weakness is that a register is only as honest as its expiries are enforced — if lapses merely "flag for review" and no one reviews, it becomes an inventory of rubber-stamped permanence wearing the costume of control. It can be gamed by under-registration (keep the asymmetry off the books) or by boilerplate warrants copied across entries, and because it records justifications without testing them, a well-written but hollow warrant passes. The discipline that guards against this is to make expiry the true default, audit for unregistered asymmetries, and route the actual re-justification to a real review rather than an autopilot renewal.
How it implements the components¶
The register realizes the memory side of the archetype — the components that keep a calibrated asymmetry accountable over time:
justified_asymmetry_record— each entry is a justified-asymmetry record: the differential plus the owner, expiry, and reason that license keeping it.relevant_difference_warrant— the register stores, per entry, the relevant-difference warrant that licenses the asymmetry, though it neither produces nor tests that warrant.
It does not evaluate whether a warrant actually holds — that is the Relevant Asymmetry Test's job, and it produces the warrant this register merely files. It does not run the periodic re-examination of entries (the Asymmetry Sunset Review, normalization_or_sunset_path) or hear challenges to one (the Countervailing Review Panel, appeal_or_review_path).
Related¶
- Instantiates: Directed Asymmetry Mapping and Calibration — the register is where the archetype's kept asymmetries live as accountable, expiring records.
- Consumes: Relevant Asymmetry Test supplies the warrant each entry files; Compensating Control Selection supplies the controls attached to a kept asymmetry.
- Sibling mechanisms: Asymmetry Sunset Review · Relevant Asymmetry Test · Countervailing Review Panel · Compensating Control Selection · Role-Specific Policy Table · Burden–Benefit Balance Sheet · Asymmetry Dimension Scorecard · Directed Relation Matrix · Direction-Sensitive Metric Dashboard · False Symmetry Review · Side-Swap Test
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: A standing log of every asymmetry the system has chosen to keep — each entry carrying its justification, its owner, and its expiry — so no differential treatment survives unexamined, making its operative form a durable account of actual events, decisions, or transitions whose value depends on history or provenance.
Independent corroboration: The frozen evidence defines Asymmetry Exception Register as 'A standing log of every asymmetry the system has chosen to keep — each entry carrying its justification, its owner, and its expiry — so no differential treatment survives unexamined', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Legal and regulatory exception registers supply documented warrants, owners, review dates, and expiry for departures from a norm.
Related originating lineages:
- Computer Science & Software Engineering — Least-privilege access governance supplies the model of justified exceptional grants.
- Organizational & Management Science — Governance and compliance practice maintain exception ledgers as systems of record.
Review resolution: Law and governance are the agreed primary lineage. Software policy exceptions and managerial registers materially shape implementation, and the specific focus on asymmetry makes the artifact an Encyclopedia synthesis across those practices.
Attribution caveat: The asymmetry-specific register combines established exception governance with access-control and organizational review practices.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The register is deliberately dumb — it stores and expires, and hands judging to the Relevant Asymmetry Test and re-examination to the Asymmetry Sunset Review. That is a feature: a system of record that also adjudicates can be argued with and lobbied, whereas a register that only remembers and enforces a clock is hard to talk out of expiring an entry. Its trustworthiness comes from doing less, not more.
[n1] The principle of least privilege holds that each actor should have only the access its role genuinely requires. A register of asymmetry exceptions is how that principle is kept true over time — every grant beyond the baseline is an entry that must justify itself and expire, rather than a permanent widening of the default. ↩