FM-JC-002 — Selective Enforcement

Open archive search
Archive registry entry

FM-JC-002 — Selective Enforcement

Selective Enforcement occurs when a justice, governance, institutional, contractual, platform, security, legal, compliance, or restoration system applies rules, penalties, protections, remedies, audits, rights, obligations, or standards unevenly across actors, classes, roles, cases, or contexts based on power, status, convenience, loyalty, risk, optics, extraction value, or basin preservation rather than coherent principle, causing legitimacy, trust, auditability, and justice integrity to collapse.

draftid: FM-JC-002version: 0.1.0updated: 2026-06-20
Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation
Online

The section has a stable overview route and basic reader context.

Technical Layer
Online

A deeper technical overview is available.

Registry
Current

334 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

0. Justice Scope Note

This entry is conceptual and systems-oriented.

It does not treat all discretion, prioritization, contextual judgment, proportional enforcement, triage, mercy, equity adjustment, phased remediation, risk-based enforcement, prosecutorial choice, moderation prioritization, or resource-aware justice as inherently failed.

Not every difference in enforcement is selective enforcement.

A coherent justice system may vary enforcement based on:

  • severity
  • evidence
  • risk
  • intent
  • capacity
  • proportionality
  • repair possibility
  • recurrence risk
  • affected-state burden
  • public safety
  • legitimate context
  • due process
  • scarce resources
  • staged remediation
  • restorative priority

The failure begins when enforcement differences follow power rather than principle.

A coherent system can explain why different cases require different treatment.

A failed system cannot show that differences are principled, auditable, and justice-preserving.

Selective Enforcement occurs when the rule binds some actors and not others, protects some actors and not others, punishes some actors and not others, or grants remedy to some actors and not others for reasons unrelated to coherent justice.

The problem is not discretion.

The problem is unprincipled asymmetry in the application of rules, protections, obligations, penalties, or remedies.


1. Definition

Selective Enforcement occurs when a justice, governance, institutional, contractual, platform, security, legal, compliance, or restoration system applies rules, penalties, protections, remedies, audits, rights, obligations, or standards unevenly across actors, classes, roles, cases, or contexts based on power, status, convenience, loyalty, risk, optics, extraction value, or basin preservation rather than coherent principle, causing legitimacy, trust, auditability, and justice integrity to collapse.

The uneven enforcement may involve:

  • rules
  • penalties
  • sanctions
  • protections
  • exemptions
  • remedies
  • rights
  • appeals
  • account access
  • contract obligations
  • reporting duties
  • safety standards
  • due process
  • investigation thresholds
  • audit thresholds
  • disciplinary action
  • moderation action
  • compliance action
  • policy enforcement
  • disclosure requirements
  • evidence standards
  • retaliation protections
  • enforcement timelines
  • repair obligations
  • restoration access

The asymmetry may be based on:

  • power
  • status
  • wealth
  • role
  • rank
  • institutional value
  • political value
  • public visibility
  • reputational risk
  • legal risk
  • loyalty
  • proximity to authority
  • extraction value
  • strategic usefulness
  • platform value
  • market value
  • public-relations cost
  • convenience
  • internal politics
  • fear of retaliation
  • basin preservation
  • preferred narrative
  • scapegoat usefulness

The core failure is:

textScroll
rule exists
→ enforcement varies by power, status, convenience, or optics
→ weaker nodes carry more constraint
→ stronger nodes receive exemption or protection
→ legitimacy debt accumulates
→ justice coherence collapses

Selective Enforcement is not merely inconsistency.

It is inconsistency aligned with power, convenience, control, or basin protection.


2. Core Pattern

The core pattern is:

  1. A rule, contract, standard, policy, protection, right, or remedy is defined.
  2. Cases arise that require application of the rule.
  3. The system applies the rule strictly to some actors and loosely to others.
  4. Enforcement differences correlate with status, power, value, convenience, optics, loyalty, leverage, or institutional risk.
  5. The system explains differences through process language, discretion, context, safety, pragmatism, or confidentiality.
  6. Weaker, lower-status, less-protected, less-visible, or less-useful nodes carry higher enforcement load.
  7. Stronger, more-useful, more-protected, or more-exposed nodes receive exemptions, delays, softer interpretation, private handling, or non-enforcement.
  8. Affected nodes experience rule reality as asymmetric.
  9. Auditability is reduced because the official rule and the lived rule diverge.
  10. Legitimacy decays because justice no longer appears principle-bound.

A healthy system says:

textScroll
different treatment must be justified by coherent principle

A selectively enforcing system says:

textScroll
the rule applies, except where applying it would cost the system too much

The failure is often hidden because the formal rule may look coherent.

The written policy may be neutral.

The stated standard may be universal.

The procedure may appear fair.

But the applied rule differs from the written rule.

The real law of the system becomes visible only in enforcement patterns.


3. Failure Signature

Typical signature:

textScroll
formal rule consistency↑
actual enforcement asymmetry↑
power-weighted exemption↑
weak-node penalty load↑
protected-node accountability↓
auditability↓
legitimacy debt↑
trust↓
O↓

Extended signature:

textScroll
same rule,
different burden

same breach,
different consequence

same right,
different access

same protection,
different recipient

principle declared,
power enforced

Common verbal signatures include:

textScroll
this case is different
we have to be pragmatic
we cannot treat every case the same
they are too important to lose
we handled this privately
we have discretion here
this would create too much risk
we need to preserve stability
the policy allows exceptions
they made a mistake, but their value is clear
we need to send a message in this case
we cannot disclose why enforcement differed
the process was followed

Common system signatures include:

textScroll
a low-power actor is punished for a violation tolerated in high-power actors
a platform enforces policy strictly against small users while exempting valuable accounts
an institution disciplines visible dissent while protecting leadership misconduct
a contract imposes obligations on weaker parties while allowing stronger parties informal flexibility
a governance body investigates opponents more aggressively than allies
a safety standard is applied publicly to outsiders but waived internally
an appeal is available in theory but practically granted only to high-status actors
a security rule is used against inconvenient nodes but ignored for favored nodes
a remedy exists, but only powerful nodes can access it quickly

The defining condition is not difference.

The defining condition is difference without principle symmetry.


4. Primary U-Layer Origin

Common origin layers:

  • U1 — Power / Budgets: enforcement follows authority, liability, revenue, institutional value, legal risk, political risk, or survival pressure.
  • U2 — Configuration / Boundaries: rules contain discretionary channels that can be used asymmetrically.
  • U3 — Execution / Runtime: enforcement decisions are made case by case without principled consistency.
  • U4 — Information / Truth: asymmetry is narrated as context, discretion, privacy, safety, or pragmatism.
  • U5 — Coordination / Time: enforcement is delayed for protected actors until pressure fades.
  • U6 — Coherence Field: legitimacy is preserved through universal-rule language despite selective application.
  • U7 — Memory / Recurrence: enforcement precedents are hidden, forgotten, or inconsistently recorded.
  • U8 — Environment / Field: external incentives reward protecting high-value actors and disciplining expendable ones.

Common manifestation layers:

  • U1 — Power: powerful actors receive softer constraints.
  • U2 — Boundaries: rule boundaries are selectively opened or closed.
  • U3 — Execution: enforcement differs in practice.
  • U4 — Truth: formal equality language hides applied asymmetry.
  • U6 — Field: trust decays because rule reality diverges from rule claim.

Selective Enforcement is primarily a Γ / Au / O / K failure.

Selection decides who receives constraint.

Auditability declines when enforcement criteria are opaque.

Constraint load becomes unevenly distributed.


5. Typical Development Sequence

A common development sequence is:

  1. A rule, standard, right, policy, or contract obligation is created.
  2. The system claims uniform applicability.
  3. A high-cost case appears involving a powerful, valuable, protected, or strategically important actor.
  4. Strict enforcement would threaten revenue, stability, reputation, authority, loyalty, or basin preservation.
  5. The system creates or invokes an exception.
  6. A lower-cost case appears involving a weaker, less-protected, or more disposable actor.
  7. The system enforces strictly.
  8. Official language maintains that enforcement is fair and contextual.
  9. Affected nodes observe asymmetry.
  10. Trust declines.
  11. The rule becomes a control instrument rather than a justice structure.
  12. Hidden legitimacy debt accumulates.

The loop often looks like:

textScroll
universal rule → high-power exception → low-power punishment → legitimacy decay

Another common loop is:

textScroll
asymmetry exposed → discretion invoked → audit denied → pattern repeats

Selective Enforcement becomes durable when enforcement records are opaque enough that affected nodes cannot prove the pattern.


6. Diagnostic Markers

Diagnostic markers include:

  • Similar violations produce different consequences.
  • Enforcement severity correlates with status, power, revenue, loyalty, or visibility.
  • Protected actors receive private handling.
  • Weaker actors receive public punishment.
  • Rules are written broadly but enforced narrowly.
  • Exceptions are not logged or justified.
  • Discretion is invoked more often for powerful actors.
  • Affected nodes cannot compare cases.
  • Enforcement data is unavailable or selectively disclosed.
  • Remedies are easier to access for high-capacity actors.
  • The same standard is framed as strict or flexible depending on who is involved.
  • Appeal outcomes differ by leverage.
  • Enforcement delays benefit powerful actors.
  • The system cannot explain asymmetry using stable principles.

Useful diagnostics:

  • Enforcement Symmetry: Measures whether similar cases receive principled treatment.
  • Rule Application Consistency: Tests whether written rules match applied rules.
  • Power-Weighted Outcome Drift: Measures whether outcomes correlate with power or status.
  • Protection Asymmetry: Tracks who receives protection and who does not.
  • Remedy Access Symmetry: Measures whether remedies are accessible across power gradients.
  • Exception Density: Measures frequency and distribution of exceptions.
  • Discretion Auditability: Tests whether discretionary decisions are inspectable.
  • Selective Accountability Index: Measures uneven accountability burden.
  • Legitimacy Debt: Tracks trust and coherence loss from asymmetric enforcement.
  • Post-Enforcement Recurrence: Tracks repeated asymmetry after exposure.

Relevant gates include:

  • Enforcement Symmetry Gate: Fails when like cases are not treated by like principles.
  • Principle Consistency Gate: Fails when enforcement differs without coherent justification.
  • Rule Integrity Gate: Fails when written rules diverge from applied rules.
  • Accountability Gate: Fails when accountability follows power rather than responsibility.
  • Remedy Access Gate: Fails when remedies are available only to high-leverage actors.
  • Protection Symmetry Gate: Fails when protections are unevenly distributed.
  • Exception Audit Gate: Fails when exceptions are unrecorded or unprincipled.
  • Discretion Audit Gate: Fails when discretionary enforcement is opaque.
  • Legitimacy Gate: Fails when enforcement asymmetry destroys trust.
  • Hidden Debt Gate: Fails when asymmetry debt is not counted.

The first common gate failure is usually the Enforcement Symmetry Gate.

Once enforcement is visibly asymmetric, even valid enforcement decisions become harder to trust because the system has damaged its principle field.


Relevant operators include:

  • Γ — Selection: Primary operator; selects who receives enforcement, protection, exemption, remedy, or penalty.
  • Au — Auditability: Needed to reveal enforcement pattern asymmetry.
  • O — Coherence: Declines when rule claims and enforcement reality diverge.
  • K — Constraint / Load: Constraint load is distributed unevenly.
  • H — Hidden Debt: Legitimacy and justice debt accumulate under asymmetry.
  • M — Meaning: Fairness, discretion, context, pragmatism, or safety language can mask asymmetry.
  • BΣ — Boundary Integrity: Boundary protections may hold for some actors and collapse for others.
  • R — Restoration Capacity: Repair access may be selective.
  • Ψ — Observation / Interface: Displays universal rules while hiding selective application.
  • Φ — Flow / Resource Movement: Enforcement and remedy flows follow power or value.
  • E — Exit: Weaker nodes may have no exit from asymmetric rules.
  • Τ — Trajectory / Time: Selective delays preserve protected actors.
  • Λ — Compatibility: Tests whether enforcement is compatible with stated principles.
  • D — Damping: Can prevent overreaction or suppress accountability for favored actors.

Common operator pattern:

textScroll
Γ selects by power
K imposed asymmetrically
Au↓
M justifies discretion
H↑
O↓

The core operator inversion is:

textScroll
rules bind the weak and bend around the powerful

instead of:

textScroll
rules bind according to principle, with auditable exceptions

Selective Enforcement converts law, policy, or contract into a status-sensitive control surface.


  • Rules Must Bind Across Power Gradients: principle must survive differences in power.
  • Enforcement Must Preserve Principle Symmetry: like cases must be governed by like principles.
  • Justice Requires Symmetric Accountability: responsibility, not status, determines accountability.
  • Protection Must Not Be Status-Weighted: safeguards must not follow prestige or leverage.
  • Rights Must Not Depend on Leverage: access to rights and remedies cannot require power.
  • Remedy Access Must Not Be Selective: repair must be available where burden exists.
  • Legitimacy Requires Non-Arbitrary Enforcement: arbitrary asymmetry destroys trust.
  • Auditability Must Expose Enforcement Asymmetry: enforcement data must be inspectable.
  • Procedural Theater: process can hide selective enforcement.
  • Enforcement Capture: enforcement can be captured by protected interests.
  • Manufactured Consent: asymmetric conditions can be hidden beneath formal agreement.
  • Hidden Debt Accumulation: enforcement asymmetry accumulates legitimacy debt.
  • Like Cases Must Be Treated by Like Principles: variation requires coherent justification.
  • Rules Must Bind the Powerful and the Weak: power cannot create exemption.
  • Enforcement Criteria Must Be Inspectable: discretionary criteria must be reviewable.
  • Remedy Access Must Be Symmetric: access to repair must not depend on status.
  • Protection Must Not Follow Status: safety and due process must not be selective.
  • Discretion Must Remain Auditable: discretion without audit becomes hidden power.
  • Exceptions Must Be Principled and Recorded: exceptions require reasons, scope, and review.
  • Selective Enforcement Must Be Counted as Legitimacy Debt: asymmetry damages the justice field.

10. Common False Positives

Not every difference in enforcement is Selective Enforcement.

Common false positives include:

  • Different consequences based on severity.
  • Different remedies based on different affected-state burden.
  • Different timing based on evidence availability.
  • Legitimate triage under constrained resources.
  • Proportional response to intent, recurrence risk, or harm.
  • Mercy applied through principled, auditable criteria.
  • Risk-based enforcement with transparent standards.
  • Staged remediation for low-risk cases.
  • Different treatment because cases are materially different.
  • Equity adjustments that reduce structural asymmetry rather than deepen it.
  • Confidential handling that preserves auditability and protection symmetry.
  • Non-enforcement where enforcement would create greater incoherence and reasons are documented.

Clarifying rule:

This is not Selective Enforcement unless enforcement, protection, remedy, penalty, audit, or obligation differs for reasons that track power, status, convenience, optics, loyalty, extraction value, or basin preservation rather than coherent principle.

Context-sensitive enforcement can be coherent.

It fails when context becomes cover for power-sensitive rule application.


11. Common False Repairs

Common false repairs include:

  • restating that the rule applies equally
  • publishing universal policy language
  • adding appeal procedures without exposing enforcement patterns
  • punishing one low-power actor as proof of seriousness
  • creating private exceptions while claiming consistency
  • adding diversity of reviewers without changing criteria
  • increasing documentation without releasing comparative data
  • calling unequal outcomes “case-specific”
  • promising future consistency without auditing past asymmetry
  • expanding procedural review while preserving captured discretion
  • creating dashboards that omit protected actors
  • blaming individual discretion while preserving incentive structure
  • adding training without changing enforcement authority
  • treating public outrage cases as special one-time corrections
  • closing asymmetry claims because each case was reviewed separately

False repair often produces the loop:

textScroll
selective enforcement exposed
→ universal principle restated
→ enforcement data remains opaque
→ asymmetry persists

Another common loop is:

textScroll
protected actor exempted
→ weaker actor punished to restore optics
→ rule legitimacy declines
→ system demands trust

The repair fails because it preserves the gap between the stated rule and the applied rule.


12. Restoration Direction

Restoration requires auditing enforcement patterns, comparing like cases, exposing exception logic, rebalancing protections and remedies, correcting past asymmetries, and binding discretion to principle with reviewable evidence.

Primary restoration direction:

textScroll
make enforcement principle-bound, symmetric, and auditable across power gradients

A fuller restoration path includes:

  1. Name the rule or standard. Identify what is being enforced, protected, remedied, or penalized.
  2. Collect comparable cases. Compare like cases across actors, roles, power levels, and contexts.
  3. Map enforcement outcomes. Track penalties, exemptions, remedies, delays, appeals, and protections.
  4. Test for power weighting. Determine whether outcomes correlate with status, leverage, loyalty, value, or optics.
  5. Audit exceptions. Require reasons, scope, duration, and review for every exception.
  6. Separate legitimate context from asymmetry. Identify which differences are principled and which are not.
  7. Repair affected cases. Correct outcomes harmed by selective application.
  8. Restore remedy access. Ensure weaker nodes can access repair and appeal.
  9. Rebind discretion. Make discretionary authority transparent, reviewable, and principle-bound.
  10. Publish appropriate pattern data. Protect privacy while making enforcement symmetry inspectable.
  11. Correct protected actor immunity. Apply accountability where exemptions were unprincipled.
  12. Count legitimacy debt. Name trust loss caused by asymmetry.
  13. Monitor recurrence. Track whether selective enforcement returns after exposure.
  14. Revalidate rule legitimacy. A rule regains legitimacy only after applied symmetry is restored.

A valid restoration path should reduce:

textScroll
power-weighted enforcement
status-based exemption
remedy access asymmetry
protection asymmetry
opaque discretion
exception density
hidden justice debt
rule legitimacy loss
post-exposure recurrence

Selective Enforcement is not repaired by saying the rule is universal.

It is repaired by proving that the applied rule is principle-bound across power gradients.


  • Justice: Primary family; justice fails when accountability, protection, and remedy follow power rather than principle.
  • Contracts: Contract terms and enforcement can bind weaker parties while powerful parties receive flexibility or immunity.
  • Restoration: Selective enforcement creates repair asymmetry and hidden burden debt.
  • Governance: Governance legitimacy collapses when rules apply unevenly across factions, offices, classes, or institutions.
  • Institutions: Institutions may enforce against low-power members while protecting leadership or high-value contributors.
  • Platforms: Platform policy can be applied strictly to ordinary users while exempting high-value accounts, partners, advertisers, or strategic actors.
  • Security: Security rules can target inconvenient nodes while shielding authorized or high-status violations.
  • AI Governance: AI policies, safety thresholds, content standards, or redress pathways can be selectively applied by user class, region, partner status, or political pressure.
  • Compliance: Compliance can become paper symmetry with applied asymmetry.
  • Civilization Interface: Selective enforcement across civilizations, groups, or interface classes produces legitimacy drift.
  • Coherence: Coherence requires rules, protections, and remedies to remain principle-bound under pressure.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry / Canon-Aligned

This mode maps upward to:

  • FM-JC-001 — Procedural Theater
  • FM-JC-009 — Enforcement Capture
  • FM-CORE-004 — Auditability Collapse
  • FM-CORE-006 — U4 Truth Substitution
  • FM-R-018 — Basin-Protective Pseudo-Repair

Sibling or related Justice & Contract modes include:

  • FM-JC-001 — Procedural Theater
  • FM-JC-003 — Punitive Drift
  • FM-JC-004 — Under-Resourced Justice
  • FM-JC-005 — Amnesty Without Repair
  • FM-JC-006 — Emergency Normalization
  • FM-JC-007 — Manufactured Consent
  • FM-JC-009 — Enforcement Capture
  • FM-JC-010 — Proxy-Relay Obfuscation
  • FM-JC-011 — Locked-In Renegotiation Failure
  • FM-JC-012 — Parasitic Contracting

Related Restoration modes include:

  • FM-R-004 — Repair Burden Externalization
  • FM-R-012 — Capacity-Inverting Restoration
  • FM-R-013 — Victim Burden Inversion
  • FM-R-017 — Audit-Suppressed Repair
  • FM-R-018 — Basin-Protective Pseudo-Repair
  • FM-R-019 — Premature Closure

Related cross-family modes include:

  • FM-CORE-004 — Auditability Collapse
  • FM-CORE-006 — U4 Truth Substitution
  • FM-MT-009 — Scapegoat Collapse
  • FM-MT-011 — Managed Optics Failure
  • FM-SEC-002 — Audit Suppression Inversion
  • FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
  • FM-PX-008 — Justice Theater
  • FM-AIX-004 — Institutional Optics Attractor
  • FM-C-018 — Goodhart Collapse
  • FM-REI-002 — Reduction-to-Authority Lock

Aliases preserved from source material:

  • Selective Enforcement
  • Unequal Enforcement
  • Asymmetric Enforcement
  • Biased Enforcement
  • Discretionary Enforcement Abuse
  • Power-Weighted Enforcement
  • Status-Weighted Enforcement
  • Rules for Some
  • Enforcement Asymmetry
  • Protection Asymmetry
  • Selective Accountability
  • Selective Remedy

15. Minimal Entry Version

Definition: Selective Enforcement occurs when a justice, governance, institutional, contractual, platform, security, legal, compliance, or restoration system applies rules, penalties, protections, remedies, audits, rights, obligations, or standards unevenly across actors, classes, roles, cases, or contexts based on power, status, convenience, loyalty, risk, optics, extraction value, or basin preservation rather than coherent principle, causing legitimacy, trust, auditability, and justice integrity to collapse.

Signature:

textScroll
formal rule consistency↑
actual enforcement asymmetry↑
power-weighted exemption↑
weak-node penalty load↑
protected-node accountability↓
auditability↓
legitimacy debt↑
trust↓
O↓

Restoration direction:

  • name the rule or standard
  • collect comparable cases
  • map enforcement outcomes
  • test for power weighting
  • audit exceptions
  • separate legitimate context from asymmetry
  • repair affected cases
  • restore remedy access
  • rebind discretion
  • publish appropriate pattern data
  • correct protected actor immunity
  • count legitimacy debt
  • monitor recurrence
  • revalidate rule legitimacy

16. Machine-Readable Summary

yamlScroll
failure_mode:
  id: "FM-JC-002"
  name: "Selective Enforcement"
  family: "Justice & Contracts"
  production_treatment: "Standalone Entry / Canon-Aligned"
  source_lineage:
    - "Justice & Contracts"
    - "JGL Extended"
    - "Restoration / Justice / Contracts Family"
  parent_modes:
    - "FM-JC-001 — Procedural Theater"
    - "FM-JC-009 — Enforcement Capture"
    - "FM-CORE-004 — Auditability Collapse"
    - "FM-CORE-006 — U4 Truth Substitution"
    - "FM-R-018 — Basin-Protective Pseudo-Repair"
  primary_failure: "A justice, governance, institutional, contractual, platform, security, legal, compliance, or restoration system applies rules, penalties, protections, remedies, audits, rights, obligations, or standards unevenly across actors, classes, roles, cases, or contexts based on power, status, convenience, loyalty, risk, optics, extraction value, or basin preservation rather than coherent principle, causing legitimacy, trust, auditability, and justice integrity to collapse."
  scope_note: "Conceptual and systems-oriented; does not treat all discretion, prioritization, contextual judgment, proportional enforcement, triage, mercy, equity adjustment, phased remediation, risk-based enforcement, prosecutorial choice, moderation prioritization, or resource-aware justice as inherently failed."
  aliases:
    - "Selective Enforcement"
    - "Unequal Enforcement"
    - "Asymmetric Enforcement"
    - "Biased Enforcement"
    - "Discretionary Enforcement Abuse"
    - "Power-Weighted Enforcement"
    - "Status-Weighted Enforcement"
    - "Rules for Some"
    - "Enforcement Asymmetry"
    - "Protection Asymmetry"
    - "Selective Accountability"
    - "Selective Remedy"
  signature:
    - "formal rule consistency↑"
    - "actual enforcement asymmetry↑"
    - "power-weighted exemption↑"
    - "weak-node penalty load↑"
    - "protected-node accountability↓"
    - "auditability↓"
    - "legitimacy debt↑"
    - "trust↓"
    - "O↓"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U1 — Power"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U6 — Field"
  state_variables:
    - "Γ"
    - "Au"
    - "O"
    - "K"
    - "H"
    - "M"
    - "BΣ"
    - "R"
    - "Ψ"
    - "Φ"
    - "E"
    - "Τ"
    - "Λ"
    - "D"
  first_gate_failure: "Enforcement Symmetry Gate"
  restoration:
    - "Enforcement Symmetry Audit"
    - "Rule Application Review"
    - "Exception Inventory"
    - "Discretion Audit Restoration"
    - "Remedy Access Repair"
    - "Protection Symmetry Restoration"
    - "Selective Accountability Review"
    - "Legitimacy Debt Accounting"
    - "Principle Rebinding"
    - "Post-Enforcement Recurrence Monitoring"