FM-R-015 — Secret Settlement as Restoration

Open archive search
Archive registry entry

FM-R-015 — Secret Settlement as Restoration

Secret Settlement as Restoration occurs when a private settlement, sealed agreement, non-disclosure arrangement, quiet payout, confidential resolution, liability-management agreement, or private closure mechanism is treated as restoration while truth, auditability, affected-state repair, recurrence prevention, public accountability, legitimacy repair, or hidden debt accounting remains incomplete or suppressed.

draftid: FM-R-015version: 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. Restoration Scope Note

This entry is conceptual and systems-oriented.

It does not treat every settlement, private agreement, confidentiality clause, mediation outcome, legal compromise, negotiated payment, sealed process, or non-public resolution as inherently failed.

Some privacy is legitimate.

Some parties need confidentiality for safety.

Some details should not be public.

Some agreements can reduce conflict, protect affected nodes, preserve dignity, resolve liability, and support repair.

Some settlements can be part of real restoration when they include:

  • affected-state repair
  • consent-valid agreement
  • adequate capacity support
  • truth preservation
  • recurrence prevention
  • repair obligations
  • auditability appropriate to risk
  • non-retaliation
  • boundary correction
  • debt accounting
  • compensation
  • restoration verification
  • pattern visibility where systemic risk exists
  • future disclosure pathways where safety requires them

The failure begins when the settlement is treated as restoration while the restoration state remains unverifiable or incomplete.

A coherent settlement may resolve part of a conflict.

A failed settlement is used to close the appearance of debt while hiding the conditions that created it.

Secret Settlement as Restoration occurs when private closure is substituted for public, structural, affected-state, or audit-valid repair.

The problem is not settlement.

The problem is settlement being used as a repair substitute while hidden debt remains sealed beneath closure.


1. Definition

Secret Settlement as Restoration occurs when a private settlement, sealed agreement, non-disclosure arrangement, quiet payout, confidential resolution, liability-management agreement, or private closure mechanism is treated as restoration while truth, auditability, affected-state repair, recurrence prevention, public accountability, legitimacy repair, or hidden debt accounting remains incomplete or suppressed.

The settlement mechanism may include:

  • private settlement
  • sealed agreement
  • non-disclosure agreement
  • confidentiality clause
  • quiet payout
  • private mediation
  • confidential arbitration
  • informal hush agreement
  • liability release
  • non-disparagement clause
  • closed-door apology
  • private restitution
  • confidential contract amendment
  • private severance condition
  • platform-side private resolution
  • internal institutional settlement
  • reputational risk management agreement
  • quiet reinstatement or removal
  • private safety remediation
  • sealed audit result

The unrepaired or hidden condition may include:

  • unverified repair
  • suppressed truth
  • hidden pattern
  • uncounted recurrence risk
  • undisclosed systemic issue
  • uncorrected boundary failure
  • unrepaired affected state
  • unresolved public legitimacy debt
  • concealed accountability gap
  • unaddressed future victims
  • no independent audit
  • no recurrence prevention
  • no structural change
  • no disclosure pathway
  • no review of power imbalance
  • capacity-invalid consent
  • settlement under pressure
  • settlement under exhaustion
  • settlement under threat or retaliation risk

The core failure is:

text id="r7m4qx"Scroll
harm or debt becomes visible
→ private settlement closes exposure
→ settlement is treated as restoration
→ truth and audit are sealed
→ affected-state repair remains unverified
→ recurrence conditions persist
→ hidden debt accumulates beneath closure

Secret Settlement as Restoration is not simply confidentiality.

It is confidentiality plus restoration substitution.


2. Core Pattern

The core pattern is:

  1. A harm, breach, extraction, injustice, violation, contract failure, platform failure, institutional failure, or legitimacy debt appears.
  2. The responsible system faces exposure, liability, reputational risk, operational risk, or governance pressure.
  3. A private settlement or confidential resolution is created.
  4. The settlement resolves visible conflict, liability, or escalation pressure.
  5. The system treats the settlement as repair.
  6. Auditability is reduced or sealed.
  7. Truth becomes unavailable to affected fields, future nodes, or legitimacy review.
  8. The affected state may receive partial compensation but not full restoration.
  9. Recurrence conditions may remain unchanged.
  10. The settlement itself becomes evidence that the matter is closed.
  11. Hidden debt persists beneath private closure.

A healthy system says:

text id="m8q2vx"Scroll
settlement may resolve claims, but restoration must still be verified

A secret-settlement system says:

text id="p6v8rq"Scroll
the matter is resolved because the settlement is complete

The failure is especially strong when settlement closure protects the responsible system more than the affected node.

The system may pay.

It may apologize privately.

It may offer compensation.

It may improve one person’s condition.

It may reduce conflict.

It may meet legal requirements.

But if the settlement blocks truth, audit, recurrence prevention, or broader legitimacy repair, the closure creates hidden debt.


3. Failure Signature

Typical signature:

text id="q8r4vx"Scroll
private settlement↑
public auditability↓
truth visibility↓
liability exposure↓
closure claim↑
affected-state verification↓
recurrence prevention↓
hidden debt↑
legitimacy repair↓
O↓

Extended signature:

text id="v7m3qx"Scroll
agreement signed,
truth sealed

payout made,
pattern hidden

liability reduced,
restoration unverified

closure declared,
recurrence condition remains

settlement complete,
debt persists

Common verbal signatures include:

text id="m2q8rx"Scroll
the matter has been resolved privately
both parties have agreed to move forward
we cannot comment due to confidentiality
the settlement addresses the issue
this is now closed
the agreement speaks for itself
the affected party accepted the terms
we have taken appropriate action
there is no further public interest
we handled this internally
disclosure would violate privacy
the terms are confidential
we have resolved this amicably

Common system signatures include:

text id="k9v4rx"Scroll
an institution settles privately while the underlying pattern remains active
a platform compensates a user quietly while preserving the harmful mechanism
a contract dispute is closed through confidentiality while power imbalance remains
a safety failure is resolved privately without recurrence prevention
a worker accepts settlement under exhaustion while institutional audit is avoided
a governance body uses private resolution to avoid legitimacy review
an AI system harm is compensated individually while affected-class exposure remains unknown
a public apology is avoided because liability was resolved privately
a secret settlement prevents future affected nodes from seeing pattern evidence

The defining condition is not that a settlement exists.

The defining condition is that settlement closure is treated as restoration while truth, audit, repair, or recurrence prevention remains hidden or incomplete.


4. Primary U-Layer Origin

Common origin layers:

  • U1 — Power / Budgets: settlement protects money, liability, control, reputation, or authority.
  • U2 — Configuration / Boundaries: legal and procedural boundaries seal information from audit fields.
  • U3 — Execution / Runtime: settlement, NDA, arbitration, mediation, or private agreement closes the case.
  • U4 — Information / Truth: the agreement is narrated as resolution while truth is suppressed.
  • U5 — Coordination / Time: closure accelerates before restoration is verified.
  • U6 — Coherence Field: public legitimacy is preserved by private closure.
  • U7 — Memory / Recurrence: the official record marks resolution while hidden pattern persists.
  • U8 — Environment / Field: external incentives reward risk containment over transparent repair.

Common manifestation layers:

  • U2 — Boundaries: confidentiality restricts truth flow.
  • U3 — Execution: settlement is executed.
  • U4 — Truth: resolution narrative replaces restoration audit.
  • U5 — Time: the matter is closed before recurrence prevention.
  • U6 — Field: legitimacy is maintained through non-disclosure.

Secret Settlement as Restoration is primarily an Au / H / R / M failure.

Auditability is reduced.

Hidden debt is sealed.

Meaning of “resolution” replaces evidence of restoration.


5. Typical Development Sequence

A common development sequence is:

  1. Harm, breach, extraction, injustice, or failure becomes visible.
  2. The responsible system faces liability, reputational, legal, operational, or legitimacy risk.
  3. A private settlement path becomes attractive.
  4. The affected node may receive compensation, terms, relief, reinstatement, severance, or private concession.
  5. The agreement includes confidentiality, release, non-disparagement, or limited disclosure.
  6. The system treats the agreement as restoration.
  7. Public truth, pattern visibility, or independent audit is blocked.
  8. Recurrence prevention is incomplete or unverifiable.
  9. Future affected nodes cannot access pattern memory.
  10. The responsible system avoids broader accountability.
  11. The official record shows closure.
  12. Hidden debt remains inside the system.

The loop often looks like:

text id="q4v9rx"Scroll
harm → exposure risk → private settlement → closure claim → audit suppression → hidden recurrence

Another common loop is:

text id="m8r2vq"Scroll
pattern appears → individual payout → pattern hidden → future harm → new settlement

Secret Settlement as Restoration becomes durable when the system learns to convert repair demand into private risk containment.


6. Diagnostic Markers

Diagnostic markers include:

  • Settlement is used to claim repair without showing affected-state restoration.
  • Confidentiality prevents meaningful audit.
  • The same pattern recurs across sealed cases.
  • Public legitimacy is restored while truth remains unavailable.
  • Affected nodes are unable to warn future affected nodes.
  • Settlement terms resolve liability more clearly than restoration.
  • Non-disclosure prevents systemic learning.
  • The responsible system cannot show recurrence prevention.
  • Compensation occurs without boundary correction.
  • Settlement is accepted under capacity pressure, exhaustion, threat, or asymmetry.
  • The agreement closes further investigation.
  • The settlement protects reputation more than affected-state repair.
  • Internal records mark the matter resolved while operational causes remain.
  • The public is asked to trust that appropriate action occurred.

Useful diagnostics:

  • Settlement-to-Restoration Gap: Measures difference between agreement completion and actual restoration.
  • Confidentiality Suppression Load: Measures how much audit-relevant truth is sealed.
  • Repair Auditability: Tests whether repair can be independently verified.
  • Affected-State Repair: Measures whether burden changed for the affected node.
  • Hidden Settlement Debt: Tracks unresolved debt hidden by settlement closure.
  • Truth Preservation: Tests whether necessary truth survives confidentiality.
  • Recurrence Risk: Measures whether causal conditions remain active.
  • Consent Capacity Validity: Tests whether agreement was made under sufficient capacity and freedom.
  • Pattern Visibility: Measures whether systemic pattern remains visible to future repair.
  • Legitimacy Repair Integrity: Tests whether legitimacy is restored through repair or merely through silence.

Relevant gates include:

  • Settlement Integrity Gate: Fails when settlement is treated as restoration without verification.
  • Auditability Gate: Fails when confidentiality blocks repair inspection.
  • Truth Preservation Gate: Fails when necessary truth is sealed.
  • Affected-State Repair Gate: Fails when settlement does not change burden.
  • Confidentiality Boundary Gate: Fails when privacy protection becomes accountability suppression.
  • Consent Validity Gate: Fails when agreement occurs under depletion, coercion, threat, or asymmetry.
  • Hidden Debt Gate: Fails when settlement debt is not counted.
  • Recurrence Prevention Gate: Fails when causal conditions remain active.
  • Legitimacy Repair Gate: Fails when legitimacy is restored by non-disclosure.
  • Closure Gate: Fails when private agreement is treated as full repair.

The first common gate failure is usually the Settlement Integrity Gate.

Once settlement completion is equated with restoration, audit and recurrence prevention become optional or hidden.


Relevant operators include:

  • Au — Auditability: Primary operator; settlement can reduce visibility into repair, truth, and recurrence.
  • H — Hidden Debt: Debt persists beneath private closure.
  • R — Restoration Capacity: May be bypassed when settlement resolves exposure rather than affected state.
  • O — Coherence: Declines when resolution is claimed without verifiable repair.
  • M — Meaning: “Resolved,” “amicable,” “confidential,” and “closed” language substitutes for restoration.
  • BΣ — Boundary Integrity: Confidentiality boundaries may protect privacy or suppress accountability.
  • K — Constraint / Load: Settlement may transfer load to the affected node through silence, release, or non-disparagement.
  • E — Exit: Affected nodes may be forced to choose between compensation and truth.
  • Φ — Flow / Resource Movement: Money or terms flow to close risk while repair flow remains incomplete.
  • Ψ — Observation / Interface: Public interface displays closure while inner state remains hidden.
  • Τ — Trajectory / Time: Closure occurs before recurrence prevention matures.
  • Γ — Selection: Selects private risk containment over public repair.
  • Λ — Compatibility: Tests whether confidentiality is compatible with repair, safety, and legitimacy.

Common operator pattern:

text id="v3r8qm"Scroll
Au↓ through confidentiality
M↑ through resolution language
Φ routes compensation to closure
R incomplete
H↑
O↓

The core operator inversion is:

text id="x9q2mv"Scroll
settlement completion is treated as restoration completion

instead of:

text id="p5m8rx"Scroll
settlement is one possible component of auditable restoration

Secret Settlement as Restoration converts liability closure into repair theater when truth and recurrence remain unaddressed.


  • Settlement Does Not Equal Restoration: agreement resolution is not automatically affected-state repair.
  • Private Closure Cannot Cancel Public Debt: debt affecting wider legitimacy or future nodes cannot be sealed away.
  • Repair Requires Auditability: restoration must be inspectable to the degree required by risk.
  • Truth Cannot Be Sealed Without Debt: confidentiality that hides repair-relevant truth creates debt.
  • Liability Resolution Is Not Affected-State Repair: legal closure and restoration are different operations.
  • Restoration Requires Recurrence Prevention: repair must address future pattern risk.
  • Hidden Debt Must Remain Countable: sealed debt still exists.
  • Legitimacy Requires Inspectable Repair: legitimacy cannot rest only on private claims.
  • Symbolic Repair Substitution: settlement can become symbolic closure.
  • Audit Evasion in Repair: confidentiality can suppress verification.
  • Procedural Theater: formal resolution can replace justice.
  • Manufactured Consent: settlement can appear consent-valid despite capacity asymmetry.
  • Settlement Must Not Erase Repair Debt: agreement does not cancel unresolved restoration obligations.
  • Confidentiality Must Not Suppress Safety-Critical Truth: privacy cannot hide recurrence risk.
  • Closure Must Preserve Auditability: closure requires appropriate inspection.
  • Affected-State Restoration Must Be Verified: burden reduction must be checked.
  • Recurrence Conditions Must Be Repaired: future harm pathways must be closed.
  • Legitimacy Debt Must Be Counted: public trust debt cannot disappear through private agreement.
  • Consent to Settlement Must Be Capacity-Valid: agreement requires adequate freedom, capacity, information, and alternatives.
  • Private Resolution Must Not Hide Systemic Pattern: repeated harm cannot be dissolved into isolated settlements.

10. Common False Positives

Not every confidential settlement is Secret Settlement as Restoration.

Common false positives include:

  • A private agreement that fully repairs the affected state.
  • Confidentiality chosen freely by the affected node for safety or dignity.
  • Settlement paired with independent audit and recurrence prevention.
  • Non-public details with public pattern disclosure.
  • Liability resolution that explicitly does not claim full restoration.
  • Confidential compensation with visible structural correction.
  • Private mediation where all parties retain consent-valid closure and support.
  • Settlement that preserves future disclosure for safety or systemic risk.
  • Confidentiality that protects vulnerable nodes without hiding responsible-system failure.
  • Agreement with third-party review, implementation tracking, and repair verification.
  • Legal closure that leaves restoration obligations active.

Clarifying rule:

This is not Secret Settlement as Restoration unless private settlement or confidentiality is treated as repair while truth, auditability, affected-state restoration, recurrence prevention, or hidden debt accounting remains incomplete or suppressed.

Confidentiality can protect.

It fails when it becomes a shelter for unrepaired debt.


11. Common False Repairs

Common false repairs include:

  • increasing settlement amount without repairing recurrence conditions
  • adding confidentiality carve-outs that are too narrow to preserve audit
  • claiming privacy while hiding systemic pattern
  • using private apology as accountability
  • marking the issue resolved after payment
  • offering individual compensation without affected-class repair
  • replacing public audit with internal review
  • sealing facts needed for future safety
  • adding non-retaliation language without enforcement
  • treating capacity-constrained agreement as consent-valid
  • resolving one case while preserving the harmful mechanism
  • offering a private benefit for silence
  • using mediation closure to avoid accountability
  • reducing liability exposure while leaving hidden debt uncounted
  • claiming all parties are satisfied without verifying restoration

False repair often produces the loop:

text id="r8q3vx"Scroll
secret settlement questioned
→ confidentiality defended
→ audit remains blocked
→ restoration claim persists

Another common loop is:

text id="m2v7rq"Scroll
pattern appears
→ cases settled individually
→ pattern stays hidden
→ recurrence continues

The repair fails because settlement management replaces restoration verification.


12. Restoration Direction

Restoration requires separating settlement from restoration, auditing what the settlement did and did not repair, preserving necessary truth, counting hidden debt, preventing recurrence, and verifying affected-state repair without violating legitimate privacy.

Primary restoration direction:

text id="k4r9vx"Scroll
treat settlement as a possible repair component, not proof of restoration

A fuller restoration path includes:

  1. Identify the settlement function. Determine whether the agreement resolved liability, conflict, compensation, access, truth, safety, or restoration.
  2. Separate legal closure from repair. Clarify which obligations remain after settlement.
  3. Audit affected-state repair. Verify whether burden, risk, access, capacity, boundary, or legitimacy changed.
  4. Review confidentiality boundaries. Determine whether secrecy protects affected nodes or suppresses accountability.
  5. Preserve necessary truth. Maintain pattern visibility, safety-relevant facts, and audit access where needed.
  6. Test consent capacity. Assess whether agreement was made with adequate capacity, information, support, and alternatives.
  7. Count hidden settlement debt. Identify unresolved debt sealed beneath closure.
  8. Repair recurrence conditions. Change the mechanisms that produced the original failure.
  9. Create safe disclosure pathways. Allow truth to surface when future safety, legitimacy, or systemic audit requires it.
  10. Verify non-retaliation. Ensure agreement does not create hidden coercive constraints.
  11. Restore public legitimacy where needed. If the debt affects a wider field, private closure is insufficient.
  12. Track pattern recurrence. Aggregate sealed cases without exposing protected details.
  13. Revalidate closure. Closure is valid only where repair, truth, and recurrence prevention are adequate.
  14. Prevent settlement laundering. Block future use of confidential agreements as proof of restoration.

A valid restoration path should reduce:

text id="x4m8rq"Scroll
settlement-to-restoration gap
confidentiality suppression load
hidden settlement debt
truth loss
audit blockage
recurrence risk
capacity-invalid consent
legitimacy debt
pattern invisibility

Secret Settlement as Restoration is not repaired by better settlement language.

It is repaired by making private resolution accountable to restoration reality.


  • Restoration: Primary family; settlement fails when it replaces affected-state repair.
  • False Repair: Strongly linked to Symbolic Repair Substitution, Audit Evasion in Repair, and Forced Forgiveness.
  • Justice: Justice fails when private closure suppresses truth, pattern visibility, or accountability.
  • Contracts: Contract mechanisms can resolve liability while preserving restoration debt.
  • Governance: Governance repair fails when legitimacy debt is sealed rather than repaired.
  • Institutions: Institutions may use confidential agreements to preserve reputation while recurrence conditions remain.
  • Platforms: Platforms may quietly compensate users while preserving harmful systems.
  • AI Governance: AI harm redress can fail when individual settlements hide systemic model, data, or deployment failures.
  • Security: Security failures can be privately resolved while boundary violations or surveillance overreach remain hidden.
  • Economy: Payments can close exposure while leaving extraction pathways intact.
  • Coherence: Coherence requires settlement, truth, audit, and repair to remain distinguishable.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

  • FM-R-008 — Audit Evasion in Repair
  • FM-R-011 — Symbolic Repair Substitution
  • FM-JC-005 — Amnesty Without Repair
  • FM-JC-007 — Manufactured Consent
  • FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Restoration modes include:

  • FM-R-001 — Cosmetic Restoration
  • FM-R-002 — Process Inflation
  • FM-R-003 — Insight Without Load Reduction
  • FM-R-004 — Repair Burden Externalization
  • FM-R-008 — Audit Evasion in Repair
  • FM-R-011 — Symbolic Repair Substitution
  • FM-R-012 — Capacity-Inverting Restoration
  • FM-R-013 — Victim Burden Inversion
  • FM-R-014 — Forced Forgiveness
  • FM-R-017 — Audit-Suppressed Repair

Related Justice / Contract modes include:

  • FM-JC-001 — Procedural Theater
  • FM-JC-005 — Amnesty Without Repair
  • FM-JC-007 — Manufactured Consent
  • FM-JC-008 — Post-Signing Environmental Incoherence
  • FM-JC-009 — Enforcement Capture
  • FM-JC-011 — Locked-In Renegotiation Failure
  • FM-JC-012 — Parasitic Contracting

Related cross-family modes include:

  • FM-CORE-002 — Hidden Debt Accumulation
  • FM-CORE-004 — Auditability Collapse
  • FM-CORE-006 — U4 Truth Substitution
  • FM-MT-011 — Managed Optics Failure
  • FM-SEC-002 — Audit Suppression Inversion
  • FM-SEC-004 — Consent Theater / Invalid Authorization
  • FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
  • FM-AIX-016 — Standingless Instrumentalization
  • FM-C-004 — Exposure Inversion
  • FM-REI-003 — Unbounded Extraction

Aliases preserved from source material:

  • Secret Settlement as Restoration
  • Secret Settlement Debt
  • Settlement-as-Restoration
  • Private Closure Substitution
  • Confidential Settlement Repair
  • Sealed Repair
  • NDA Closure
  • Quiet Settlement Repair
  • Liability Settlement as Restoration
  • Private Payout as Repair
  • Closed-Door Restoration
  • Confidential Closure Failure

15. Minimal Entry Version

Definition: Secret Settlement as Restoration occurs when a private settlement, sealed agreement, non-disclosure arrangement, quiet payout, confidential resolution, liability-management agreement, or private closure mechanism is treated as restoration while truth, auditability, affected-state repair, recurrence prevention, public accountability, legitimacy repair, or hidden debt accounting remains incomplete or suppressed.

Signature:

text id="q9v3rx"Scroll
private settlement↑
public auditability↓
truth visibility↓
liability exposure↓
closure claim↑
affected-state verification↓
recurrence prevention↓
hidden debt↑
legitimacy repair↓
O↓

Restoration direction:

  • identify the settlement function
  • separate legal closure from repair
  • audit affected-state repair
  • review confidentiality boundaries
  • preserve necessary truth
  • test consent capacity
  • count hidden settlement debt
  • repair recurrence conditions
  • create safe disclosure pathways
  • verify non-retaliation
  • restore public legitimacy where needed
  • track pattern recurrence
  • revalidate closure
  • prevent settlement laundering

16. Machine-Readable Summary

yaml id="s7m4rq"Scroll
failure_mode:
  id: "FM-R-015"
  name: "Secret Settlement as Restoration"
  family: "Restoration / False Repair"
  production_treatment: "Standalone Entry"
  source_lineage:
    - "FM-RX-007 — Secret Settlement as Restoration"
    - "Restoration / JGL Extended"
    - "False Repair Family"
  parent_modes:
    - "FM-R-008 — Audit Evasion in Repair"
    - "FM-R-011 — Symbolic Repair Substitution"
    - "FM-JC-005 — Amnesty Without Repair"
    - "FM-JC-007 — Manufactured Consent"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "A private settlement, sealed agreement, non-disclosure arrangement, quiet payout, confidential resolution, liability-management agreement, or private closure mechanism is treated as restoration while truth, auditability, affected-state repair, recurrence prevention, public accountability, legitimacy repair, or hidden debt accounting remains incomplete or suppressed."
  scope_note: "Conceptual and systems-oriented; does not treat every settlement, private agreement, confidentiality clause, mediation outcome, legal compromise, negotiated payment, sealed process, or non-public resolution as inherently failed."
  aliases:
    - "Secret Settlement as Restoration"
    - "Secret Settlement Debt"
    - "Settlement-as-Restoration"
    - "Private Closure Substitution"
    - "Confidential Settlement Repair"
    - "Sealed Repair"
    - "NDA Closure"
    - "Quiet Settlement Repair"
    - "Liability Settlement as Restoration"
    - "Private Payout as Repair"
    - "Closed-Door Restoration"
    - "Confidential Closure Failure"
  signature:
    - "private settlement↑"
    - "public auditability↓"
    - "truth visibility↓"
    - "liability exposure↓"
    - "closure claim↑"
    - "affected-state verification↓"
    - "recurrence prevention↓"
    - "hidden debt↑"
    - "legitimacy repair↓"
    - "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:
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
  state_variables:
    - "Au"
    - "H"
    - "R"
    - "O"
    - "M"
    - "BΣ"
    - "K"
    - "E"
    - "Φ"
    - "Ψ"
    - "Τ"
    - "Γ"
    - "Λ"
  first_gate_failure: "Settlement Integrity Gate"
  restoration:
    - "Settlement Integrity Audit"
    - "Confidentiality Boundary Review"
    - "Hidden Settlement Debt Accounting"
    - "Affected-State Restoration Review"
    - "Truth Preservation Protocol"
    - "Recurrence Prevention Repair"
    - "Consent Capacity Revalidation"
    - "Legitimacy Repair Review"
    - "Pattern Visibility Restoration"
    - "Post-Settlement Repair Verification"