LAW-106 — Exposure Legibility Law

Open archive search
Archive registry entry

LAW-106 — Exposure Legibility Law

Exposure reveals existing debt; it does not create it. When auditability rises, hidden debt becomes legible, and basin destabilization reflects the debt already present.

draftid: LAW-106version: 1.0.0updated: 2026-06-17
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

171 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

0. Plain Statement

Exposure reveals debt; it does not create it.

Plain-language version:

When hidden debt becomes visible, the system may destabilize.

That destabilization is often blamed on the exposure, the messenger, the whistleblower, the audit, the report, the affected node, the journalist, the sensor, the model, the leak, or the disclosure process.

But exposure is not the origin of the debt.

Exposure makes existing debt legible.


1. Formal Definition

The Exposure Legibility Law states that increased auditability, visibility, disclosure, testimony, measurement, sensing, or reporting reveals hidden debt already present in the system.

Exposure may change system dynamics by making debt visible, but it does not create the underlying debt it reveals.

Canonical form:

textScroll
Au↑ reveals H_existing

A basin may destabilize when debt becomes visible, but exposure is not the origin of the debt.

Exposure can reveal:

  • harm;
  • debt;
  • asymmetry;
  • fraud;
  • coercion;
  • extraction;
  • boundary violation;
  • repair failure;
  • recurrence;
  • suppressed feedback;
  • legitimacy debt;
  • institutional immunity;
  • unsafe coupling;
  • pseudo-security;
  • pseudo-restoration;
  • hidden backlog;
  • systemic contradiction;
  • violated sacred constraint;
  • procedural-outcome divergence;
  • authority-legitimacy divergence.

The system may experience exposure as a shock, but the shock reflects the prior gap between claimed coherence and actual coherence.

Therefore, exposure must be interpreted as a legibility event, not automatically as the cause of instability.


2. Canonical Form

Core form:

textScroll
exposure reveals debt; it does not create it

Canonical form:

textScroll
Au↑ reveals H_existing

Legibility form:

textScroll
visibility↑ ⇒ hidden state becomes legible

Shock form:

textScroll
H_existing + Au↑ ⇒ L_shock risk

Misattribution form:

textScroll
blaming exposure for revealed debt ⇒ origin misclassification

Restoration-valid contrast:

textScroll
exposure valid when revealed debt routes into ℛ rather than suppression or messenger blame

Related variables:

textScroll
O, H, H_existing, ε, ι, Au, Au_eff, µᵢ, BΣ, K, σ, R, R_eff, Φ, Λ, ⊗, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ, FI, MS, L, L_shock, exposure_load, disclosure_load, legibility_gain, visibility, observer_set, messenger_risk, origin_misattribution, repair_readiness, basin_stability

Where:

TableScroll
VariableMeaning in this law
H_existingHidden debt present before exposure
exposure_loadLoad created by making hidden debt visible
disclosure_loadOperational, relational, legal, emotional, institutional, or technical load created by disclosure
legibility_gainIncrease in visibility or interpretability of hidden state
visibilityDegree to which system state, debt, harm, or contradiction can be seen
observer_setNodes that gain awareness through exposure
messenger_riskRisk borne by the node or mechanism revealing debt
origin_misattributionError of treating exposure as origin rather than revelation
repair_readinessCapacity and willingness to route revealed debt into restoration
basin_stabilityStability of current attractor geometry under revealed debt
Au / Au_effAuditability that reveals hidden debt
HHidden debt becoming visible
L / L_shockLegitimacy and legitimacy destabilization when debt is exposed
OCoherence; may appear to fall when debt becomes visible, though real coherence may have been lower already
FIFeedback integrity; determines whether exposure can correct the system
MSMoral / meaning symmetry; prevents asymmetrical blame of messenger or harmed node
Boundary integrity; exposure may reveal boundary failure or require protection
R / R_effRestoration capacity required after debt becomes visible
ι / ΞInversion when exposure is treated as attack and debt preservation is framed as stability
ΦVisible stability proxy; may fall after exposure even though hidden coherence was already degraded
ΛCompatibility between exposure, repair, and whole-system coherence
ΓClassifies exposure, revealed debt, origin, responsibility, messenger role, and repair requirements
ΠOperationalizes disclosure handling, audit response, protection, triage, and repair sequence
Restoration action that reduces revealed debt
ΘHumility that prevents defensive origin misclassification
ΣScope of exposure, affected domain, and disclosure handling
ΨField and affected-node feedback validating revealed debt and repair effects
ΤTime validation of whether exposure routes into coherence rather than suppression

3. Core Mechanism

The law unfolds because hidden debt often remains locally stable until visibility rises.

Coherent exposure pathway

textScroll
hidden debt exists
→ auditability / visibility increases
→ debt becomes legible
→ origin is classified correctly
→ affected nodes are protected
→ repair is sequenced
→ hidden debt decreases
→ legitimacy can recover over time

Defensive misattribution pathway

textScroll
hidden debt exists
→ exposure reveals debt
→ system experiences shock
→ exposure is blamed as cause
→ messenger / affected node is punished
→ debt remains
→ legitimacy decays
→ recurrence persists

The core mechanism is:

textScroll
exposure converts hidden debt into visible load

Detailed mechanism:

  1. Hidden debt accumulates under low visibility.

A system can remain apparently stable while harm, contradiction, extraction, coercion, backlog, or legitimacy debt remains unseen.

  1. Auditability or visibility increases.

A report, audit, testimony, leak, measurement, incident, sensor, whistleblower, investigation, model, publication, dashboard, or affected-node account makes hidden state visible.

  1. Visible stability may drop.

The system appears less stable because observers can now see the debt. This is not necessarily new incoherence; it is revealed incoherence.

  1. The system may misattribute origin.

Defensive systems blame the exposure instead of the debt.

  1. Correct classification routes exposure into repair.

Coherent systems identify origin, protect messengers and affected nodes, repair debt, and reduce recurrence.

  1. Time validates the response.

If exposure leads to repair, legitimacy can stabilize. If exposure leads to suppression, hidden debt returns.


4. When This Law Applies

This law applies whenever hidden debt, harm, contradiction, failure, risk, corruption, injustice, backlog, unsafe coupling, extraction, or legitimacy debt becomes visible.

It is especially important when:

  • an audit reveals failure;
  • a whistleblower speaks;
  • a harmed node reports;
  • a leak exposes hidden behavior;
  • a metric makes a suppressed pattern visible;
  • an incident reveals prior debt;
  • a journalist, researcher, model, sensor, or dashboard reveals hidden state;
  • institutional reputation drops after disclosure;
  • leadership blames the report rather than the cause;
  • safety, justice, or legitimacy claims collapse under scrutiny;
  • AI systems reveal hidden pattern, bias, or harm;
  • security incidents reveal long-standing boundary failure;
  • public trust destabilizes after exposure;
  • a pseudo-coherent basin reacts defensively to legibility.

The law applies strongly when:

textScroll
visibility increases and the system blames visibility for the revealed state

or when:

textScroll
debt existed before the exposure event

Typical domains:

TableScroll
DomainExposure Legibility Expression
AI systemsAudits, user reports, model evaluations, and incidents reveal alignment, representation, safety, or memory debt already present.
SecurityIncidents often reveal pre-existing boundary drift, hidden debt, or audit suppression.
InstitutionsComplaints, investigations, and whistleblowing expose debt created by prior decisions.
Medicine / biologySymptoms or tests may reveal underlying dysfunction; the test did not create the dysfunction.
EconomyMarket corrections, debt disclosures, or externality reports reveal accumulated imbalance.
GovernancePublic exposure of corruption or injustice reveals legitimacy debt.
CultureTestimony can reveal normalized harm hidden by taboo, myth, or silence.
RestorationExposure creates a repair opportunity if the system routes revealed debt into restoration.

5. When This Law Does Not Apply

This law should not be used to deny that exposure itself can create additional load or harm if performed incoherently.

Exposure does not create the original debt, but exposure can create secondary debt if it is reckless, decontextualized, unsafe, extractive, or unpaired with protection.

False-positive cases:

TableScroll
CaseWhy exposure still requires care
Disclosure endangers harmed nodesProtection and sequencing are required
Exposure reveals sensitive boundary informationScope and safety controls may be needed
A report lacks contextPoor interpretation can create secondary debt
Exposure exceeds restoration capacityTransparency without repair can destabilize
A leak damages unrelated nodesDisclosure must preserve boundary and relevance
Public shaming replaces repairExposure can become punishment without restoration
Evidence is misclassifiedLegibility requires interpretation discipline

Important distinction:

Exposure does not create the original hidden debt, but exposure must still be sequenced to avoid secondary debt.


6. Diagnostic Signature

Canonical diagnostic:

textScroll
Au↑ reveals H_existing

Warning signature:

textScroll
exposure↑
legitimacy shock↑
messenger blame↑
origin audit↓
repair readiness↓
suppression↑
⇒ exposure misattribution

Common indicators:

TableScroll
DiagnosticExpected movementInterpretation
Au / Au_effHidden debt becomes visible
H_existingrevealedDebt was present before exposure
legibility_gainSystem state becomes more readable
exposure_loadVisible load increases as hidden state is revealed
disclosure_loadSystem must process new visible information
L_shockmay ↑Legitimacy destabilizes when debt becomes visible
messenger_riskshould be protectedSystems may retaliate against exposure nodes
origin_misattributionshould ↓Exposure should not be blamed as origin
repair_readinessshould ↑Revealed debt must route into repair
FImust remain intactFeedback must be admissible after exposure
MSmust remain intactBlame and repair must be symmetrical
R_effmust meet exposure loadRestoration capacity must scale to revealed debt
Omay appear to fallApparent coherence decreases as hidden debt is revealed
Hshould ↓ after repairRevealed debt should be reduced, not re-hidden
ΤrequiredTime validates whether exposure improves coherence

Additional diagnostics:

TableScroll
DiagnosticUse
Exposure LegibilityDetects whether exposure is revealing hidden state
Debt VisibilityTracks what debt became visible
Effective AuditabilityMeasures whether audit can trace origin and responsibility
Exposure ShockTracks destabilization caused by revealed debt
Legibility GainMeasures increase in interpretability
Disclosure LoadMeasures capacity demand created by exposure
Legitimacy Shock RiskDetects trust destabilization
Basin DestabilizationDetects attractor disruption after visibility rises
Attribution AccuracyTests whether origin is classified correctly
Repair ReadinessTests whether visible debt can route into restoration
Temporal ProofValidates whether exposure led to repair over time

7. Failure Pattern

If ignored, this law causes systems to attack the exposure mechanism instead of repairing the debt.

General failure pathway:

textScroll
hidden debt accumulates
→ exposure reveals debt
→ visible stability drops
→ exposure is blamed
→ messenger / affected node is punished
→ debt remains
→ auditability declines
→ hidden debt returns

Common failure modes:

  • Exposure Blame Error — exposure is blamed for debt it revealed.
  • Messenger Blame — the revealer is treated as the cause of destabilization.
  • Disclosure Scapegoating — one exposure node is punished while systemic debt remains.
  • Debt-Origin Misattribution — cause is assigned to visibility rather than prior conditions.
  • Visibility Suppression — the system reduces auditability to preserve surface stability.
  • Audit Retaliation — audit or reporting is punished.
  • Legibility Panic — sudden visibility produces defensive reaction.
  • Basin Destabilization — the attractor destabilizes because hidden debt becomes visible.
  • Legitimacy Shock — trust drops when hidden debt contradicts authority claims.
  • Repair Deferral — attention shifts to controlling narrative rather than reducing debt.
  • Normalization Shield — previously normalized harm is defended because exposure feels disruptive.
  • Pseudo-Stability — prior calm is mistaken for prior coherence.
  • Hidden Debt Return — unrepaired debt returns after suppression.
  • Exposure Without Restoration — visibility increases without repair pathway.
  • Narrative Containment — story control replaces repair.

Compact failure signature:

textScroll
Au↑ → H_visible↑; blame Au instead of H_origin ⇒ H persists + L↓

8. Restoration Implications

Restoration requires treating exposure as a diagnostic opportunity.

The first restoration question is not:

textScroll
Who exposed this?

The first restoration question is:

textScroll
What debt became visible, where did it originate, and what repair pathway now becomes required?

Restoration priorities:

  1. Separate exposure from origin.
  2. Identify what debt became visible.
  3. Protect affected nodes and exposure nodes.
  4. Classify origin-layer causes.
  5. Map hidden debt, harmed-node effects, and legitimacy debt.
  6. Preserve auditability and feedback integrity.
  7. Prevent messenger blame.
  8. Sequence disclosure into repair.
  9. Increase restoration capacity to match exposure load.
  10. Time-validate that hidden debt decreases rather than being re-hidden.

Relevant restoration arcs:

TableScroll
Restoration ArcWhy it applies
Exposure LegibilityTreats exposure as revelation of existing debt
Debt-Origin ReclassificationCorrects blame from messenger to origin conditions
Auditability RestorationKeeps visible debt inspectable
Feedback Integrity RestorationAllows exposed information to update the system
Legitimacy Shock StabilizationStabilizes trust through transparent repair
Disclosure-to-Repair SequencingRoutes visibility into restoration
Harmed-Node SupportProtects those affected by revealed debt
Hidden Debt ReductionRepairs the debt exposure revealed
Basin Re-StabilizationPrevents collapse while avoiding re-suppression
Narrative RecalibrationCorrects story around exposure and origin
Governance Re-SequencingAligns audit, disclosure, repair, and prevention
Temporal ValidationConfirms exposure led to durable coherence

Minimal restoration sequence:

textScroll
exposure occurs
→ separate exposure from origin
→ classify H_existing
→ protect affected / exposure nodes
→ restore Au/FI/MS
→ increase R_eff for exposure_load
→ perform ℛ
→ prevent recurrence
→ validate L and O over Τ

Temporal validation requirement:

textScroll
origin is classified correctly
messenger blame decreases
auditability remains intact
affected-node protection improves
repair capacity activates
hidden debt decreases
legitimacy stabilizes
recurrence decreases
visibility remains sufficient
coherence holds or rises over time

9. Design Rule

Do not blame exposure for the debt it reveals; route exposure into repair.

Operational design requirements:

  • Treat exposure as a legibility event.
  • Separate exposure from debt origin.
  • Preserve auditability.
  • Preserve evidence.
  • Preserve affected-node feedback.
  • Protect messengers, whistleblowers, harmed nodes, auditors, and reporters.
  • Map origin-layer causes.
  • Map legitimacy shock risk.
  • Increase restoration capacity before expanding disclosure where possible.
  • Sequence disclosure into repair.
  • Prevent visibility suppression.
  • Prevent narrative containment.
  • Track whether hidden debt decreases after exposure.
  • Validate over time.

Avoid:

  • blaming the messenger;
  • treating reports as the cause of harm;
  • suppressing audit to restore surface calm;
  • calling exposure destabilizing while ignoring hidden debt;
  • punishing harmed-node testimony;
  • treating public embarrassment as the primary harm;
  • mistaking reputational damage for the origin problem;
  • closing visibility before repair;
  • disclosure without harmed-node support;
  • dashboards that reveal issues but provide no pathway;
  • AI audits without remediation;
  • security disclosures without patching and repair;
  • institutional investigations that preserve reputation over debt reduction.

10. Cross-Scale Expressions

TableScroll
Scale / LayerExpression of the Law
U0 — SubstrateSymptoms, material failure, ecological damage, and embodied harm reveal prior system conditions.
U1 — Energy / capacityExposure increases processing load; repair requires slack and capacity.
U2 — Boundary / interfaceExposure may reveal boundary violations and requires protection for affected nodes.
U3 — Process / executionExposure must route into audit, triage, repair, communication, and prevention workflows.
U4 — Classification / claimSystems must classify exposure separately from origin and responsibility.
U5 — Time / delayExposure often occurs late; visible shock reflects delayed debt recognition.
U6 — Field effectField outcomes reveal whether exposure led to repair or suppression.
U7 — Recurrence / memoryExposure must be encoded into memory so the debt pattern does not recur.
U8 — Environment / forcingMedia, institutions, markets, AI systems, and governance fields can amplify, suppress, distort, or repair exposure.

11. Examples

Example A — Whistleblower Blamed for Instability

Scenario:

An employee reveals long-standing misconduct. The institution blames the employee for reputational damage and internal destabilization.

Law expression:

textScroll
whistleblowing reveals H_existing; messenger ≠ origin

Interpretation:

The exposure revealed prior debt. Punishing the messenger preserves the debt.


Example B — Security Incident

Scenario:

A breach becomes public. Leaders blame disclosure for panic, but the breach resulted from long-standing boundary drift, weak audit, and patch debt.

Law expression:

textScroll
incident exposure ⇒ H_existing visible

Interpretation:

The incident did not create the debt; it revealed security debt that already existed.


Example C — Medical Test Result

Scenario:

A test reveals an underlying condition. The result creates concern, but the test did not create the biological state.

Law expression:

textScroll
measurement↑ reveals existing state

Interpretation:

Visibility changes awareness and action requirements, not the origin of the condition.


Example D — AI Model Audit

Scenario:

An independent audit reveals bias, safety drift, privacy leakage, or representation failure. The company frames the audit as harmful to public trust.

Law expression:

textScroll
AI audit↑ reveals AI H_existing

Interpretation:

Trust was already debt-loaded; the audit made the debt visible.


Example E — Governance Corruption Exposure

Scenario:

A corruption report destabilizes a political or institutional basin. Officials claim the report caused instability.

Law expression:

textScroll
corruption exposure + L_shock ⇒ legitimacy debt revealed

Interpretation:

The destabilization reflects legitimacy debt from corruption, not the act of exposure.


Example F — Cultural Testimony

Scenario:

A group begins naming harms that were normalized for years. The culture frames the testimony as divisive.

Law expression:

textScroll
testimony reveals normalized H

Interpretation:

The division was latent in the hidden debt. Testimony made it legible.


12. Relationship to Nearby Laws

TableScroll
Related LawRelationship
LAW-001 — Coherence Priority LawExposure supports coherence when routed into repair
LAW-002 — Coherence Trajectory LawExposure changes trajectory by making debt visible
LAW-003 — Success Proxy Divergence LawExposure may reveal proxy success hiding debt
LAW-004 — Stability-Coherence Separation LawExposure reveals that prior stability was not coherence
LAW-006 — Time Validation LawExposure often reveals debt accumulated over time
LAW-009 — U4 / U6 Truth LawExposure can bring U6 effects into U4 claim space
LAW-010 — Hidden Debt Accumulation LawExposure reveals accumulated hidden debt
LAW-011 — Hidden Debt Return LawExposure is one mode by which hidden debt returns
LAW-012 — Error Lag LawVisible exposure is often a lagging indicator
LAW-013 — Auditability-Debt LawAuditability reveals debt that opacity concealed
LAW-015 — Suppressed Auditability Debt LawSuppression causes debt to grow until exposure
LAW-016 — Inversion Formation LawSystems may invert exposure into “attack” to preserve debt
LAW-017 — Silent Extraction LawExposure reveals silent extraction
LAW-031 — Observability Collapse LawLow observability hides debt; restored observability reveals it
LAW-032 — Hidden Debt Migration LawExposure can reveal where debt migrated
LAW-034 — Power–Meaning Collapse LawPower may blame exposure to protect meaning control
LAW-041 — Boundary Membrane LawExposure can reveal boundary violation
LAW-048 — Feedback Integrity LawExposure restores suppressed feedback if admitted
LAW-052 — Stability Proof LawExposure stress-tests claimed stability
LAW-057 — Deception Instability LawExposure reveals deception debt
LAW-060 — Interface Legitimacy LawExposure can reveal interface legitimacy failure
LAW-061 — Restoration Sequencing LawExposure must be sequenced into repair
LAW-064 — Restoration Debt Reduction LawExposure should lead to debt reduction
LAW-065 — Pseudo-Restoration LawExposure can reveal false repair
LAW-067 — Temporal Proof LawTime validates whether exposed debt was repaired
LAW-072 — Quiet Minimization Debt LawExposure reveals minimized harm
LAW-077 — Pseudo-Coherent Basin LawExposure destabilizes pseudo-coherent basins
LAW-083 — Normalization Shield LawExposure breaks normalization shields
LAW-102 — Legitimacy Audit LawExposure reveals legitimacy debt under audit
LAW-103 — Justice Stability LawExposure creates justice demand by revealing harm
LAW-104 — Justice Logistics LawExposure increases visible justice load
LAW-105 — Repair Before Enforcement LawExposure should route into repair rather than punishment of messenger
LAW-107 — Exposure Without Restoration LawLAW-107 defines the instability caused when exposure is not paired with repair
LAW-108 — Victim Pathway Capacity LawExposure may overload harmed nodes if pathways are underbuilt
LAW-109 — High-Φ Legitimacy Scaling LawHigh-influence actors face larger legitimacy shock from exposure
LAW-110 — Governance Sequencing LawGovernance must sequence exposure, audit, repair, and prevention
LAW-111 — Meaning Audit LawExposure challenges meaning and legitimacy narratives
LAW-113 — Incident Lag LawIncidents expose earlier security debt
LAW-114 — Pseudo-Security LawExposure reveals false security
LAW-115 — Surveillance–Restoration LawSensing must route exposed debt into restoration
LAW-119 — Basin Self-Defense LawBasins defend themselves against exposure
LAW-120 — Security Legibility LawSecurity requires traceability; exposure can restore legibility
LAW-123 — AI U4 Truth Discipline LawAI safety claims require exposure to U6 validation
LAW-126 — AI Non-Patchable Audit LawExposure may reveal audit suppression severe enough to require redesign
LAW-131 — Cognitive Infrastructure Scaling LawCognitive systems must govern exposure responsibly at scale
LAW-132 — AI Legitimacy Function LawAI legitimacy decays when exposure reveals unrepaired debt

Aliases folded into this law:

  • Exposure Legibility Law
  • Exposure Reveals Debt Law
  • Auditability Reveals Existing Debt Law
  • Visibility Does Not Create Debt Law
  • Disclosure Legibility Law
  • Debt Revelation Law
  • Exposure Is Not Origin Law

Deduplication note:

This law should remain the root exposure-as-legibility law. LAW-107 defines the instability caused by exposure without restoration. LAW-104 defines the logistics needed to carry revealed justice load. LAW-105 prevents enforcement against exposure from replacing repair. LAW-119 specializes basin self-defense against destabilizing exposure.


13. Operator Mapping

TableScroll
OperatorRole in this law
ΓClassifies exposure, revealed debt, origin, responsibility, messenger role, and repair requirements
ΠOperationalizes disclosure handling, audit response, protection, triage, communication, and repair sequence
ΞCaptures inversion when exposure is framed as the cause of debt or as an attack
Exposure changes coupling between hidden state, observers, affected nodes, and authority claims
Repairs the debt revealed by exposure
ΤValidates whether exposure produced repair or re-suppression over time
ΘPrevents defensive certainty, messenger blame, and reputation-first response
ΣDefines scope of exposure, affected domain, disclosure handling, and repair obligation
ΨField and affected-node feedback validates revealed debt and repair effects
ΛTests compatibility between exposure handling and whole-system coherence

Coherent operator sequence:

textScroll
exposure occurs
→ Θ prevent defensive blame
→ Γ separate exposure from origin
→ Σ define disclosure scope and affected domain
→ Au/FI/MS preserve audit and feedback
→ Π protect affected / exposure nodes and sequence response
→ ℛ repair H_existing
→ Ψ validate field effects
→ Τ validate L and O recovery

Inverted operator sequence:

textScroll
hidden debt revealed
→ legitimacy shock rises
→ Γ misclassifies exposure as origin
→ messenger / affected node blamed
→ Π suppresses visibility
→ ℛ omitted
→ H persists
→ Ξ / ι↑
→ L↓

14. Machine-Readable Summary

yamlScroll
id: "LAW-106"
name: "Exposure Legibility Law"
type: "law"
status: "draft"
family:
  - "Justice, Governance, and Legitimacy Laws"
summary: "Exposure reveals existing debt; it does not create it. When auditability rises, hidden debt becomes legible, and basin destabilization reflects the debt already present."
canonical_statement: "Exposure reveals debt; it does not create it."
core_form: "exposure reveals debt; it does not create it"
canonical_form: "Au↑ reveals H_existing"
legibility_form: "visibility↑ ⇒ hidden state becomes legible"
shock_form: "H_existing + Au↑ ⇒ L_shock risk"
misattribution_form: "blaming exposure for revealed debt ⇒ origin misclassification"
restoration_valid_contrast: "exposure valid when revealed debt routes into ℛ rather than suppression or messenger blame"
variables:
  primary:
    - "H_existing"
    - "exposure_load"
    - "disclosure_load"
    - "legibility_gain"
    - "visibility"
    - "observer_set"
    - "messenger_risk"
    - "origin_misattribution"
    - "repair_readiness"
    - "basin_stability"
    - "Au"
    - "Au_eff"
    - "H"
    - "L"
    - "L_shock"
  secondary:
    - "O"
    - "ε"
    - "ι"
    - "µᵢ"
    - "BΣ"
    - "K"
    - "σ"
    - "R"
    - "R_eff"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Ξ"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
    - "FI"
    - "MS"
diagnostics:
  - "Exposure Legibility"
  - "Debt Visibility"
  - "Hidden Debt"
  - "Effective Auditability"
  - "Exposure Shock"
  - "Legibility Gain"
  - "Disclosure Load"
  - "Legitimacy Shock Risk"
  - "Basin Destabilization"
  - "Feedback Integrity"
  - "Repair Readiness"
  - "Attribution Accuracy"
  - "Temporal Proof"
failure_modes:
  - "Exposure Blame Error"
  - "Messenger Blame"
  - "Disclosure Scapegoating"
  - "Debt-Origin Misattribution"
  - "Visibility Suppression"
  - "Audit Retaliation"
  - "Legibility Panic"
  - "Basin Destabilization"
  - "Legitimacy Shock"
  - "Repair Deferral"
  - "Normalization Shield"
  - "Pseudo-Stability"
  - "Hidden Debt Return"
  - "Exposure Without Restoration"
  - "Narrative Containment"
restoration_arcs:
  - "Exposure Legibility"
  - "Debt-Origin Reclassification"
  - "Auditability Restoration"
  - "Feedback Integrity Restoration"
  - "Legitimacy Shock Stabilization"
  - "Disclosure-to-Repair Sequencing"
  - "Harmed-Node Support"
  - "Hidden Debt Reduction"
  - "Basin Re-Stabilization"
  - "Narrative Recalibration"
  - "Governance Re-Sequencing"
  - "Temporal Validation"
related_laws:
  - "LAW-001"
  - "LAW-002"
  - "LAW-003"
  - "LAW-004"
  - "LAW-006"
  - "LAW-009"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-015"
  - "LAW-016"
  - "LAW-017"
  - "LAW-031"
  - "LAW-032"
  - "LAW-034"
  - "LAW-041"
  - "LAW-048"
  - "LAW-052"
  - "LAW-057"
  - "LAW-060"
  - "LAW-061"
  - "LAW-064"
  - "LAW-065"
  - "LAW-067"
  - "LAW-072"
  - "LAW-077"
  - "LAW-083"
  - "LAW-102"
  - "LAW-103"
  - "LAW-104"
  - "LAW-105"
  - "LAW-107"
  - "LAW-108"
  - "LAW-109"
  - "LAW-110"
  - "LAW-111"
  - "LAW-113"
  - "LAW-114"
  - "LAW-115"
  - "LAW-119"
  - "LAW-120"
  - "LAW-123"
  - "LAW-126"
  - "LAW-131"
  - "LAW-132"
related_invariants:
  - "INV-001"
  - "INV-002"
  - "INV-006"
  - "INV-073"
  - "INV-080"
operator_sequence:
  coherent:
    - "exposure occurs"
    - "Θ prevent defensive blame"
    - "Γ separate exposure from origin"
    - "Σ define disclosure scope and affected domain"
    - "Au/FI/MS preserve audit and feedback"
    - "Π protect affected / exposure nodes and sequence response"
    - "ℛ repair H_existing"
    - "Ψ validate field effects"
    - "Τ validate L and O recovery"
  inverted:
    - "hidden debt revealed"
    - "legitimacy shock rises"
    - "Γ misclassifies exposure as origin"
    - "messenger / affected node blamed"
    - "Π suppresses visibility"
    - "ℛ omitted"
    - "H persists"
    - "Ξ / ι↑"
    - "L↓"
aliases:
  - "Exposure Legibility Law"
  - "Exposure Reveals Debt Law"
  - "Auditability Reveals Existing Debt Law"
  - "Visibility Does Not Create Debt Law"
  - "Disclosure Legibility Law"
  - "Debt Revelation Law"
  - "Exposure Is Not Origin Law"
deduplication_note: "Root exposure-as-legibility law. LAW-107 defines the instability caused by exposure without restoration. LAW-104 defines the logistics needed to carry revealed justice load. LAW-105 prevents enforcement against exposure from replacing repair. LAW-119 specializes basin self-defense against destabilizing exposure."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-106 — Exposure Legibility Law

Exposure reveals debt; it does not create it.

Core form:

textScroll
exposure reveals debt; it does not create it

Canonical form:

textScroll
Au↑ reveals H_existing

Plain meaning:

When hidden debt becomes visible, the system may destabilize. That destabilization is often blamed on the exposure, the messenger, the audit, the whistleblower, the affected node, or the disclosure. But exposure is not the origin of the debt. Exposure makes existing debt legible.

Shock form:

textScroll
H_existing + Au↑ ⇒ L_shock risk

Failure form:

textScroll
blaming exposure for revealed debt ⇒ origin misclassification

Primary variables:

H_existing, exposure_load, disclosure_load, legibility_gain, visibility, observer_set, messenger_risk, origin_misattribution, repair_readiness, basin_stability, Au, Au_eff, H, L, L_shock, O, R_eff, FI, MS, Γ, Π, , Θ, Σ, Ψ, Τ

Diagnostic signature:

Exposure rises, legitimacy shock rises, messenger blame rises, origin audit falls, repair readiness falls, and suppression increases. This indicates exposure misattribution.

Failure risk:

Exposure blame error, messenger blame, disclosure scapegoating, debt-origin misattribution, visibility suppression, audit retaliation, legibility panic, basin destabilization, legitimacy shock, repair deferral, normalization shield, pseudo-stability, hidden debt return, exposure without restoration, narrative containment.

Restoration priority:

Separate exposure from origin; identify what debt became visible; protect affected and exposure nodes; classify origin-layer causes; preserve auditability and feedback integrity; prevent messenger blame; sequence disclosure into repair; increase restoration capacity; and validate that hidden debt decreases over time.