0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Economic Legibility repairs systems where economic flows, debts, externalities, contracts, dependencies, subsidies, burdens, extraction paths, or hidden costs are difficult to see, trace, audit, or assign.

It applies when value appears to be created, stabilized, optimized, or exchanged, but the real flow of cost, debt, burden, dependency, or externality is hidden.

This arc repairs economic opacity by:

• revealing flows;
• revealing debts;
• revealing externalities;
• revealing contracts;
• revealing dependencies;
• mapping hidden H;
• distinguishing visible price from total burden;
• distinguishing revenue from coherence;
• distinguishing efficiency from cost export;
• identifying who pays, who benefits, who carries risk, and who has exit;
• making economic repair, clearance, recoupling, or attractor shift possible.

Economic Legibility is the canonical precursor arc for economic restoration when hidden cost structure must become visible before repair can route.

1.2 Core Restoration Function

This arc restores economic auditability by making flows, debts, externalities, contracts, dependencies, and burden pathways visible enough to map hidden H and route repair.

Economic Legibility prevents economic success from being certified by visible exchange alone.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• economic flows are hidden, fragmented, or hard to audit;
• debt exists but is dispersed, deferred, renamed, securitized, offloaded, or obscured;
• externalities are treated as outside the accounting boundary;
• contracts are unclear, asymmetrical, buried, or difficult to interpret;
• users, workers, vendors, communities, ecosystems, downstream systems, or future actors carry unpriced burden;
• a platform, institution, or market captures value while obscuring extraction pathways;
• public metrics show profit, efficiency, growth, or stability while hidden H rises;
• dependency paths are not visible enough to assess consent or exit;
• settlement, compliance, or accounting artifacts hide unresolved burden;
• repair cannot begin because no one can see where cost, debt, obligation, or benefit is flowing.

Examples:

• a platform’s revenue rises while unpaid moderation, creator instability, or user dependency carries hidden cost;
• a company appears profitable by externalizing environmental, labor, or infrastructure burden;
• a contract hides dependency, penalty, or data-use obligations in obscure terms;
• debt is moved between entities until responsibility becomes unclear;
• an AI product appears cheap because users supply training value, attention, labor, or data without legible compensation;
• a public system reports budget efficiency while deferred maintenance and social burden accumulate elsewhere.

2.2 When Not to Apply

Do not apply this arc when:

• flows, debts, contracts, dependencies, and externalities are already sufficiently visible;
• active harm requires immediate stabilization first;
• the issue is not economic legibility but known economic coercion requiring slack regeneration or recoupling repair;
• disclosure would violate privacy, consent, trade-secret, safety, or third-party boundaries without scoped audit;
• legibility is being used to delay material repair already known to be owed;
• the system refuses to reveal or audit economic flows;
• the correct immediate move is clearance, slack regeneration, contract revalidation, or economic recoupling;
• legibility becomes surveillance of vulnerable nodes rather than audit of power and burden.

Economic Legibility must not become audit without repair.

2.3 Required Preconditions

Before this arc begins, the following must be true:

If required preconditions fail:

Arc cannot validly begin.

The system must route to Audit Surface Expansion, Observability Restoration, Hidden Debt Reduction, Responsibility Gradient Mapping, Contract Revalidation, Economic Slack Regeneration, Economic Clearance, or Governance-Level Restoration.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Economic coherence cannot be assessed while flows, debts, externalities, contracts, and dependencies remain illegible.

4. Restoration Objective

4.1 Canonical Objective

Restore economic legibility by making hidden flows, debts, externalities, contracts, dependencies, and burden pathways visible enough to map hidden H and route repair.

Formal objective:

Au_eff ↑
flow_visibility ↑
debt_visibility ↑
externality_visibility ↑
contract_visibility ↑
dependency_visibility ↑
burden_traceability ↑
H_hidden ↓ through exposure
H_export visible then ↓ through repair routing
FI ↑
Φ/O divergence ↓

Expanded objective:

Convert economic opacity into a repairable map of flows, debts, externalities, obligations, dependencies, and hidden burden.

4.2 Non-Goals

This arc does not aim to:

• make every private transaction public;
• expose vulnerable actors for transparency optics;
• confuse data availability with usable legibility;
• perform accounting without repair routing;
• treat price as the full measure of cost;
• treat profit as coherence proof;
• treat legal contract visibility as consent validity;
• use complexity to excuse burden transfer;
• reveal hidden H only to preserve the same structure;
• replace economic repair with dashboards.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Au economic flow / debt / burden trace → Π boundary-safe disclosure scope → Σ total-burden legibility invariant → FI affected-field feedback → Θ profit / efficiency / accounting proxy damping → ℛ repair / clearance / slack / recoupling routing → Λ economic-fit test → Τ burden and recurrence proof

Reference sequence from the registry:

reveal flows
→ reveal debts
→ reveal externalities
→ reveal contracts
→ reveal dependencies
→ map hidden H

Universal grammar alignment:

Au + Π → Σ → FI → Θ → ℛ → Λ → Τ

Economic Legibility may route into Hidden Debt Reduction, Contract Revalidation, Economic Slack Regeneration, Economic Clearance, Economic Attractor Shift, Consent-Valid Economic Recoupling, Circulation Repair, Coherence Drift Restoration, or Governance-Level Restoration.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is audit-gated, boundary-gated, and repair-routing-gated.

The sequence must distinguish:

price
cost
flow
debt
externality
contract
dependency
burden
hidden H
repair obligation

The following steps cannot be skipped:

flow mapping
debt mapping
externality mapping
contract mapping
dependency mapping
hidden H map
boundary-safe disclosure
repair routing
temporal burden proof

If flows are revealed but hidden debt is not mapped, the arc is incomplete.

If hidden debt is mapped but no repair route exists, the arc becomes inert.

If disclosure exposes vulnerable nodes while protecting high-power opacity, the arc fails.

6. Restoration Phases

Phase 0 — Identify Economic Object

Purpose: Name the system whose economic legibility is being restored.

Actions:

• identify market, platform, contract, exchange, debt structure, supply chain, labor system, pricing system, resource flow, subsidy, settlement, or dependency;
• identify visible claims of value, efficiency, stability, compliance, or growth;
• identify affected nodes;
• identify likely hidden burden surfaces.

Validation:

economic object named
affected field visible
audit target defined

Phase 1 — Reveal Flows

Purpose: Make movement of value, cost, labor, risk, data, attention, and resources visible.

Actions:

• map money flows;
• map resource flows;
• map labor flows;
• map data and attention flows where relevant;
• map risk flows;
• map benefit flows;
• map subsidy flows;
• map timing and delay of flows;
• distinguish visible exchange from hidden contribution.

Validation:

flow_visibility ↑
Au_eff ↑
benefit and cost paths clearer

Phase 2 — Reveal Debts

Purpose: Identify obligations and deferred burdens.

Actions:

• map formal debt;
• map informal debt;
• map deferred maintenance;
• map unpaid labor or underpriced support;
• map obligation transfer;
• map settlement debt;
• map future burden;
• map debt hidden by accounting treatment, contract structure, or institutional narrative.

Validation:

debt_visibility ↑
H_hidden visible
future burden clearer

Phase 3 — Reveal Externalities

Purpose: Bring exported costs back inside coherence accounting.

Actions:

• map ecological externalities;
• map social externalities;
• map labor externalities;
• map infrastructure externalities;
• map cognitive or attention externalities;
• map downstream operational burden;
• map future-system cost;
• identify who absorbs the burden.

Validation:

externality_visibility ↑
H_export visible
externality denial ↓

Phase 4 — Reveal Contracts

Purpose: Make obligations, authority, terms, and hidden constraints visible.

Actions:

• identify relevant contracts and terms;
• map obligation asymmetry;
• map penalty structures;
• map unilateral change clauses;
• map data-use rights;
• map exit conditions;
• map renewal, lock-in, and dependency clauses;
• map repair, appeal, and dispute paths.

Validation:

contract_visibility ↑
contract fog ↓
consent-validity review possible

Phase 5 — Reveal Dependencies

Purpose: Identify where economic choice has narrowed.

Actions:

• map dependency on platform, employer, vendor, buyer, contract, debt, infrastructure, identity, data, reputation, or access;
• map exit cost;
• map switching cost;
• map dependency concentration;
• map bargaining asymmetry;
• map survival-edge conditions;
• map dependency feedback loops.

Validation:

dependency_visibility ↑
K baseline visible
coercive coupling risk visible

Phase 6 — Map Hidden H

Purpose: Consolidate hidden burden into a repairable map.

Actions:

• combine flows, debts, externalities, contracts, and dependencies;
• identify who benefits;
• identify who pays;
• identify who carries risk;
• identify who lacks exit;
• identify who has authority;
• identify who owes repair;
• identify which burdens are clearable, reducible, compensable, internalizable, or structural.

Validation:

hidden H map complete enough for routing
burden_traceability ↑
repair obligations visible

Phase 7 — Route Repair and Validate Over Time

Purpose: Ensure legibility leads to action.

Actions:

• route debt to clearance;
• route survival-edge pressure to slack regeneration;
• route coercive contracts to contract revalidation or recoupling repair;
• route externalities to internalization or compensation;
• route hidden extraction to governance correction;
• route circulation failures to circulation repair;
• track whether hidden H decreases after exposure.

Validation:

R ↑
H_hidden ↓ through exposure and routing
H_export ↓ through repair
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Economic Legibility cannot validly proceed in that form.

The system must either:

• expand audit surface;
• protect disclosure boundaries;
• map missing flows;
• map hidden debt;
• map externalities;
• map contracts;
• map dependencies;
• route to hidden debt reduction, economic clearance, slack regeneration, or governance-level restoration;
• withhold economic coherence claims until legibility is sufficient.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

Au_eff ↑
flow_visibility ↑
debt_visibility ↑
externality_visibility ↑
contract_visibility ↑
dependency_visibility ↑
burden_traceability ↑
H_hidden ↓ through exposure
H_export visible then ↓ through repair routing
FI ↑
Φ/O divergence ↓

Economic Legibility is not complete if:

flows remain hidden
debt remains unnamed
externalities remain outside scope
contracts remain unreadable or unusable
dependencies remain concealed
burden carriers are not identified
hidden H is mapped but not routed
audit protects powerful opacity while exposing vulnerable nodes
profit or efficiency remains the dominant proof of coherence

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• dashboards replace burden maps;
• accounting reports hide externalities;
• contracts are technically disclosed but practically illegible;
• debt is renamed as efficiency;
• unpaid labor or downstream burden is treated as outside scope;
• externalities are acknowledged but not assigned;
• audit focuses on vulnerable actors rather than burden-producing structures;
• dependency is framed as customer preference;
• hidden H is revealed but no repair route is created;
• economic growth is used to dismiss coherence concerns.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Economic Legibility cannot be certified by a one-time map. It requires repeated burden tracking and repair routing.

Template:

Completion requires Au_eff ↑,
flow_visibility ↑,
debt_visibility ↑,
externality_visibility ↑,
contract_visibility ↑,
dependency_visibility ↑,
burden_traceability ↑,
H_hidden ↓ through exposure,
H_export visible then ↓ through repair routing,
and economic decisions changing in response to the revealed burden map.

Minimum temporal proof:

• flows remain traceable;
• debts remain visible;
• externalities are not pushed back outside accounting;
• contracts remain usable and reviewable;
• dependencies remain monitored;
• burden carriers and beneficiaries remain identifiable;
• hidden H routes to repair, clearance, slack, recoupling, or governance correction;
• economic success is no longer certified by Φ metrics alone.

10.3 Completion Statement

Canonical format:

This arc is complete only when economic flows, debts, externalities, contracts, dependencies, and burden pathways are legible enough to map hidden H, identify responsibility, protect affected-node boundaries, and route repair over time.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

Au, Au_eff, H, H_hidden, H_export, O, ε, ι, BΣ, K, R, FI, flow_visibility, debt_visibility, externality_visibility, contract_visibility, dependency_visibility, burden_traceability, Φ/O divergence

11.4 Related Laws / Invariants

INV — Economic coherence requires visible burden.
INV — Price is not total cost.
INV — Profit is not coherence proof.
INV — Externalities must remain inside restoration accounting.
LAW — Hidden flows create unassigned responsibility.
LAW — Debt opacity compounds hidden H.
LAW — Dependency concealment degrades consent.
LAW — Φ economic success is not O restoration.

12. Domain Notes

12.1 Economy

Check:

• money flows;
• labor flows;
• debt flows;
• externalities;
• contracts;
• dependency paths;
• hidden subsidies;
• burden carriers;
• exit cost;
• repair obligations.

Economic restoration begins with legibility because repair cannot route if burden, benefit, and obligation remain hidden.

12.2 Platform Governance

Check:

• creator compensation;
• data and attention extraction;
• moderation labor;
• algorithmic visibility;
• platform fees;
• dependency on account access;
• appeals and reversals;
• hidden infrastructure burden;
• user switching cost.

Platforms often hide economic H behind growth, engagement, efficiency, and “free” services. Legibility must include data, attention, moderation, reputation, and dependency.

12.3 AI / Cognitive Infrastructure

Check:

• user data value;
• training contribution;
• memory value;
• cognitive labor;
• prompt labor;
• feedback value;
• evaluator labor;
• dependency on model access;
• hidden moderation or safety labor;
• downstream automation displacement.

AI systems can create economic opacity when user contribution, attention, feedback, memory, or dependency becomes value without clear accounting or recourse.

12.4 Security

Check:

• hidden operational burden;
• unpaid security debt;
• deferred patching;
• incident cost externalization;
• third-party risk transfer;
• compliance burden;
• detection and response labor;
• vendor dependency.

Security economics become illegible when risk is transferred to downstream operators, users, or future incident responders while present metrics appear efficient.

12.5 Justice / Governance / Legitimacy

Check:

• who benefits;
• who pays;
• who carries risk;
• who has authority;
• who has exit;
• who receives repair;
• who is excluded from accounting.

Legitimacy requires that economic burden and benefit are visible enough for responsibility to attach.

12.6 CMS / Meaning / Archetypes

Check:

• symbolic value extraction;
• community labor;
• unpaid care;
• invisible maintenance;
• ritual or identity labor;
• reputation capture;
• meaning-bearing work;
• hidden burden of belonging.

Meaning systems often depend on invisible economic contribution. Legibility is needed when symbolic value or communal coherence hides unrecognized labor or burden.

13. Machine-Readable Metadata

id: "RA-061"
title: "Economic Legibility"
aliases:
  - "Economic Legibility"
family_primary: "Economy / Auditability / Hidden Debt"
families_secondary:
  - "Core"
  - "Economy"
  - "Governance"
  - "Auditability"
  - "Externality"
  - "Boundary"
  - "Coherence"
  - "Dependency"
  - "Contracts"
  - "Scaling"
  - "Justice / Governance / Legitimacy"
  - "Institutional Design"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Economic"
  - "Institutional"
  - "Platform"
  - "Governance"
  - "Civilizational"
  - "AI"
  - "Security"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U3 contract / governance / allocation process"
    - "often U4 accounting / pricing / market narrative"
    - "often U5 dependency / debt / externality memory layer"
  symptom_visible:
    - "U4 price / contract term / profit metric / budget report / platform dashboard / compliance statement / settlement artifact"
  repair_required:
    - "same or lower than the layer where flows, debt, dependency, or externality became hidden"
  validation:
    - "U6"
    - "U7"
operators:
  scaffold: "Au economic flow / debt / burden trace → Π boundary-safe disclosure scope → Σ total-burden legibility invariant → FI affected-field feedback → Θ profit / efficiency / accounting proxy damping → ℛ repair / clearance / slack / recoupling routing → Λ economic-fit test → Τ burden and recurrence proof"
  sequence:
    - "Au"
    - "Π"
    - "Σ"
    - "FI"
    - "Θ"
    - "ℛ"
    - "Λ"
    - "Τ"
state_variables:
  primary:
    - "Au"
    - "Au_eff"
    - "H"
    - "H_hidden"
    - "H_export"
    - "O"
  secondary:
    - "ε"
    - "ι"
    - "BΣ"
    - "K"
    - "R"
    - "FI"
    - "Φ"
diagnostics:
  - "flow_visibility"
  - "debt_visibility"
  - "externality_visibility"
  - "contract_visibility"
  - "dependency_visibility"
  - "burden_traceability"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Hidden Flows"
  - "Debt Opacity"
  - "Externality Invisibility"
  - "Opaque Contracts"
  - "Dependency Concealment"
  - "Hidden Economic H"
  - "Cost Externalization"
  - "Burden Transfer"
  - "Shadow Subsidy"
  - "Accounting Theater"
  - "Platform Extraction Opacity"
  - "Contract Fog"
  - "Legibility Collapse"
  - "Economic Coherence Drift"
linked_restoration_arcs:
  - "RA-004"
  - "RA-014"
  - "RA-019"
  - "RA-020"
  - "RA-025"
  - "RA-040"
  - "RA-043"
  - "RA-046"
  - "RA-049"
  - "RA-054"
  - "RA-056"
  - "RA-062"
  - "RA-063"
  - "RA-064"
  - "RA-065"
  - "RA-066"
anti_patterns:
  - "Dashboard Legibility"
  - "Accounting Theater"
  - "Contract Fog"
  - "Externality Footnote"
  - "Burden Erasure"
  - "Shadow Subsidy"
  - "Dependency-as-Preference"
  - "Audit Without Routing"
  - "Profit-as-Coherence"
completion_tests:
  - "effective auditability increases"
  - "flow visibility increases"
  - "debt visibility increases"
  - "externality visibility increases"
  - "contract visibility increases"
  - "dependency visibility increases"
  - "burden traceability increases"
  - "hidden H decreases through exposure"
  - "exported H becomes visible then decreases through repair routing"
  - "feedback integrity increases"
  - "Φ/O divergence decreases"
summary: "Economic Legibility repairs hidden flows, debt opacity, externality invisibility, opaque contracts, dependency concealment, and hidden economic H by revealing flows, debts, externalities, contracts, dependencies, and burden pathways so repair can route accurately."

Final Calibration Rule

Economic Legibility answers six questions:

What economic flows are hidden or fragmented?
What debts, deferred obligations, or hidden H are concealed?
What externalities are being exported outside the visible accounting boundary?
What contracts, terms, or dependency structures shape real consent and exit?
Who benefits, who pays, who carries risk, and who owes repair?
How does legibility route into repair without dashboard legibility, accounting theater, or profit-as-coherence?