0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Repair-First Growth repairs systems where growth, expansion, scaling, adoption, market capture, deployment, output, user-base increase, institutional reach, or capability expansion is pursued before repair capacity, circulation, clearance, slack, boundary integrity, and hidden debt reduction are sufficient.

It applies when growth is being treated as recovery, legitimacy, or coherence even though the system’s repair substrate is still damaged.

This arc repairs growth theater by:

• requiring repair before expansion;
• repairing circulation before scaling throughput;
• reducing hidden debt before increasing load;
• restoring slack before increasing demand;
• expanding restoration capacity before expanding impact;
• distinguishing natural gain from extraction-driven growth;
• preventing growth from depending on overwork, hidden H, underpriced burden, coercive dependency, or externality export;
• validating that growth increases O rather than only Φ;
• allowing expansion only when capacity and repair pathways can absorb it.

Repair-First Growth is the canonical arc for ensuring growth is an effect of restored coherence, not a substitute for it.

1.2 Core Restoration Function

This arc restores growth validity by requiring repair, circulation, clearance, slack, and restoration capacity before expansion is treated as coherent.

Repair-First Growth prevents expansion from compounding unresolved damage.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• a system wants to grow before repair is complete;
• growth metrics are improving while hidden debt remains high;
• expansion would increase load on already-stressed nodes;
• circulation, return, clearance, or repair access is still weak;
• user, worker, community, infrastructure, security, governance, or ecological burden is already high;
• a platform, institution, market, or AI system is scaling faster than its repair capacity;
• “growth” depends on extraction, dependency, overwork, deferred maintenance, or externalized burden;
• a repaired subsystem is being asked to expand before temporal proof;
• adoption or revenue is being treated as legitimacy proof;
• natural gain must be distinguished from forced gain.

Examples:

• a platform scales user acquisition while support, appeal, payout, and moderation repair queues are broken;
• an AI system expands deployment before memory, evaluator, boundary, or incident repair is proven;
• a company grows revenue while technical debt, worker burnout, and externalities accumulate;
• a community project expands membership before governance, repair paths, and role clarity are ready;
• an institution launches new services while old claims, maintenance, and accountability remain unresolved;
• an economic actor increases output by drawing down ecological, social, or labor reserves.

2.2 When Not to Apply

Do not apply this arc when:

• active harm requires stabilization first;
• the issue is still hidden and economic legibility is required first;
• backlog, bad debt, waste, or unresolved burden must be cleared before growth can be assessed;
• the system lacks enough slack to support repair;
• growth is not being attempted or used as restoration proof;
• expansion would be safer than stagnation because repair capacity is already sufficient;
• “repair-first” is being used to block healthy, coherence-positive emergence;
• the system refuses to measure hidden debt, repair capacity, circulation, or affected-node burden.

Repair-First Growth must not become anti-growth rigidity.

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 Economic Legibility, Hidden Debt Reduction, Economic Clearance, Economic Slack Regeneration, Circulation Repair, Constraint Recalibration Under Φ Growth, 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:

Growth is not coherent when it increases load faster than repair, clearance, circulation, boundary integrity, and restoration capacity.

4. Restoration Objective

4.1 Canonical Objective

Restore growth validity by ensuring repair, circulation, clearance, slack, and restoration capacity precede expansion.

Formal objective:

repair_capacity ↑
circulation_integrity ↑
clearance_integrity ↑
K ↑
σ ↑
H ↓
H_export ↓
capacity_margin ↑
growth_readiness ↑
natural_gain ↑
extraction_pressure ↓
expansion_pressure constrained until Λ > 0
O ↑
Φ/O divergence ↓

Expanded objective:

Convert growth from extraction-driven expansion into coherence-bearing natural gain that emerges after repair capacity and circulation are restored.

4.2 Non-Goals

This arc does not aim to:

• reject growth itself;
• freeze systems after repair;
• force permanent austerity;
• mistake smallness for coherence;
• block natural gain;
• delay growth to protect incumbents;
• use repair language to avoid legitimate opportunity;
• require perfect repair before any movement;
• treat capacity as only financial capacity;
• certify growth from one improved metric.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Au growth / repair-capacity trace → Π boundary and affected-load protection → Σ repair-before-growth invariant → FI affected-field and capacity feedback → Θ expansion / extraction pressure damping → ℛ repair / circulation / clearance / slack routing → Λ growth-readiness fit test → Τ growth proof over time

Reference sequence from the registry:

repair circulation
→ natural gain
→ growth
→ expansion

Expanded canonical sequence:

repair circulation
→ clear hidden debt
→ restore slack and repair capacity
→ natural gain
→ bounded growth
→ expansion only after proof

Universal grammar alignment:

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

Repair-First Growth may route into Economic Legibility, Economic Clearance, Economic Slack Regeneration, Circulation Repair, Economic Attractor Shift, Constraint Recalibration Under Φ Growth, Governance-Level Restoration, Basin Geometry Mapping, Attractor Weakening, or Parallel Attractor Seeding.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is repair-gated, circulation-gated, clearance-gated, slack-gated, and growth-readiness-gated.

The sequence must distinguish:

repair
capacity
circulation
clearance
natural gain
growth
expansion
extraction

The following steps cannot be skipped:

growth pressure identification
hidden debt check
repair capacity check
circulation repair
clearance check
slack restoration
growth-readiness test
bounded growth validation
temporal proof

If growth is pursued before repair circulation, the arc fails.

If natural gain appears but boundary and capacity are not tested, growth remains provisional.

If expansion depends on extracting slack from depleted nodes, it is not restoration.

6. Restoration Phases

Phase 0 — Identify Growth Pressure

Purpose: Name what is trying to grow and why.

Actions:

• identify proposed growth or expansion;
• identify growth drivers;
• identify adoption, output, revenue, deployment, market, audience, capability, or institutional reach increase;
• identify who benefits;
• identify who carries load;
• identify whether growth is voluntary, natural, forced, incentivized, or demanded.

Validation:

growth object named
growth pressure visible
affected load mappable

Phase 1 — Audit Repair Baseline

Purpose: Determine whether growth is premature.

Actions:

• identify unresolved harm;
• identify hidden debt;
• identify backlog;
• identify clearance deficit;
• identify boundary damage;
• identify circulation failure;
• identify support and appeal capacity;
• identify technical, social, ecological, governance, or labor debt.

Validation:

repair baseline known
H visible
growth readiness not assumed

Phase 2 — Repair Circulation

Purpose: Ensure flow, return, clearance, and repair access can handle more load.

Actions:

• repair delivery;
• repair return;
• repair clearance;
• repair exchange interfaces;
• repair timing;
• repair distributed repair access;
• reduce response latency;
• ensure growth does not amplify one-way flow.

Validation:

circulation_integrity ↑
clearance ↑
τ_resp ↓

Phase 3 — Clear Hidden Debt and Backlog

Purpose: Reduce old burden before adding new load.

Actions:

• process bad debt;
• clear backlog;
• reduce waste;
• internalize externalities;
• repair deferred maintenance;
• compensate or repair affected nodes;
• preserve accountability records;
• prevent old H from being hidden by growth.

Validation:

clearance_integrity ↑
H ↓
H_export ↓

Phase 4 — Restore Slack and Repair Capacity

Purpose: Ensure the system has enough margin to grow without extraction.

Actions:

• increase buffer capacity;
• increase restoration capacity;
• increase support capacity;
• increase review and appeal capacity;
• increase security and maintenance capacity;
• protect worker, user, ecological, and governance slack;
• prevent capacity from being consumed immediately by old obligations.

Validation:

K ↑
σ ↑
R ↑
capacity_margin ↑

Phase 5 — Distinguish Natural Gain From Forced Growth

Purpose: Determine whether growth is arising from coherence or pressure.

Actions:

• identify whether demand follows real value, repair, trust, and improved circulation;
• identify whether growth depends on coercive dependency, lock-in, hype, debt, extraction, or externality export;
• compare natural adoption with forced retention;
• compare contribution gain with burden transfer;
• compare O improvement with Φ growth.

Validation:

natural_gain ↑
extraction_pressure ↓
Φ/O divergence ↓

Phase 6 — Bounded Growth Test

Purpose: Allow small-scale growth only where capacity and repair can absorb it.

Actions:

• define growth boundary;
• define capacity threshold;
• define rollback criteria;
• define support threshold;
• define incident threshold;
• define hidden debt trigger;
• define expansion stop condition;
• monitor affected-node load.

Validation:

growth_readiness ↑
Λ > 0
bounded growth does not increase H

Phase 7 — Expansion After Proof

Purpose: Permit expansion only when temporal proof is sufficient.

Actions:

• compare growth against repair capacity;
• compare growth against circulation and clearance;
• compare growth against boundary integrity;
• compare growth against hidden debt and affected-node burden;
• compare growth against field signal;
• expand only if O rises and H remains controlled;
• pause or reduce growth when repair lags.

Validation:

O ↑
H stable or ↓
capacity_margin stable or ↑
expansion valid or blocked

Phase 8 — Temporal Growth Proof

Purpose: Confirm growth remains coherence-bearing over time.

Actions:

• monitor hidden debt;
• monitor support load;
• monitor repair queues;
• monitor circulation;
• monitor worker and user burden;
• monitor externalities;
• monitor recurrence;
• monitor whether growth starts depending on extraction again.

Validation:

O(t+n) ≥ O(t)
H(t+n) ≤ H(t)
R(t+n) scales with growth
Φ/O divergence ↓
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Repair-First Growth cannot validly proceed in that form.

The system must either:

• repair circulation;
• clear hidden debt;
• regenerate slack;
• expand restoration capacity;
• protect boundaries;
• reduce expansion pressure;
• route to economic clearance, circulation repair, slack regeneration, constraint recalibration, governance-level restoration, or attractor shift;
• withhold growth or expansion claims until readiness proof exists.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

repair_capacity ↑
circulation_integrity ↑
clearance_integrity ↑
K ↑
σ ↑
H ↓
H_export ↓
capacity_margin ↑
growth_readiness ↑
natural_gain ↑
extraction_pressure ↓
expansion_pressure constrained until Λ > 0
O ↑
Φ/O divergence ↓

Repair-First Growth is not complete if:

growth begins before repair circulation
hidden debt remains high
clearance remains weak
slack remains collapsed
restoration capacity is under-scaled
growth depends on extraction or externality export
affected-node burden rises
support and appeal queues grow
capacity margin disappears
growth metrics are used as restoration proof

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• growth is used to finance repair but repair never catches up;
• expansion is justified by demand while support capacity is broken;
• natural gain is claimed while retention depends on lock-in;
• revenue growth hides labor depletion;
• output growth hides maintenance debt;
• adoption growth hides appeal, support, or incident backlog;
• scaling continues while clearance declines;
• repair teams are asked to absorb growth without added capacity;
• growth is called “resilience” while slack collapses;
• the system treats market validation as coherence proof.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Repair-First Growth cannot be certified by one growth cycle. It requires growth to remain coherence-positive over time.

Template:

Completion requires repair_capacity ↑,
circulation_integrity ↑,
clearance_integrity ↑,
K ↑,
σ ↑,
H ↓,
H_export ↓,
capacity_margin ↑,
growth_readiness ↑,
natural_gain ↑,
extraction_pressure ↓,
O ↑,
and Φ/O divergence ↓ across U7.

Minimum temporal proof:

• repair capacity remains ahead of growth load;
• circulation and clearance remain healthy;
• hidden debt does not return under expansion;
• slack remains sufficient;
• affected-node burden does not rise;
• growth emerges from natural gain rather than pressure;
• expansion can pause when repair indicators degrade;
• O rises with Φ rather than diverging from it.

10.3 Completion Statement

Canonical format:

This arc is complete only when circulation, clearance, slack, boundary integrity, and restoration capacity are repaired before expansion, so growth emerges as natural gain, hidden debt decreases, affected-node burden stays protected, and coherence rises over time.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

Au, H, H_export, O, BΣ, K, σ, R, FI, Φ, repair_capacity, circulation_integrity, clearance_integrity, natural_gain, growth_readiness, expansion_pressure, capacity_margin, extraction_pressure, Φ/O divergence

11.4 Related Laws / Invariants

INV — Growth is not restoration.
INV — Expansion requires repair capacity.
INV — Throughput must not grow faster than clearance.
INV — Natural gain follows repaired circulation.
LAW — Scaling before repair compounds hidden debt.
LAW — Growth without slack becomes extraction.
LAW — Capacity overshoot converts success into instability.
LAW — Φ growth is not O restoration.

12. Domain Notes

12.1 Economy

Check:

• hidden debt;
• clearance;
• slack;
• repair capacity;
• support capacity;
• maintenance;
• externalities;
• worker burden;
• natural demand;
• capacity margin.

Economic growth is coherent when it follows restored circulation and adequate capacity, not when it outruns them.

12.2 Platform Governance

Check:

• user growth;
• support queues;
• appeal capacity;
• creator payouts;
• moderation capacity;
• repair access;
• portability;
• governance capacity;
• trust and safety load.

Platforms should not grow faster than their ability to handle appeals, repair, moderation, payouts, reversals, and user harm.

12.3 AI / Cognitive Infrastructure

Check:

• deployment scope;
• model capability growth;
• support capacity;
• incident response;
• evaluator capacity;
• memory repair;
• boundary repair;
• appeal path;
• governance scaling;
• rollback readiness.

AI growth is not valid when model deployment expands faster than evaluator integrity, boundary safety, memory correction, incident response, and affected-party repair.

12.4 Security

Check:

• attack surface growth;
• patch capacity;
• incident response capacity;
• monitoring load;
• alert triage;
• technical debt;
• maintenance windows;
• rollback capacity;
• staffing slack.

Security growth fails when new surface area is added before existing vulnerabilities, alerts, and technical debt are cleared.

12.5 Justice / Governance / Legitimacy

Check:

• public service expansion;
• claims backlog;
• appeal access;
• oversight capacity;
• affected-node repair;
• legitimacy claims;
• accountability obligations;
• review capacity.

Governance growth must not expand authority faster than appeal, oversight, and repair.

12.6 CMS / Meaning / Archetypes

Check:

• community growth;
• role capacity;
• repair culture;
• unresolved obligations;
• care load;
• symbolic authority;
• belonging pressure;
• hidden labor.

Meaning systems need repair-first growth when expansion would otherwise amplify unresolved relational, symbolic, or communal burden.

13. Machine-Readable Metadata

id: "RA-067"
title: "Repair-First Growth"
aliases:
  - "Repair-First Growth"
family_primary: "Economy / Growth / Restoration Capacity"
families_secondary:
  - "Core"
  - "Economy"
  - "Governance"
  - "Coherence"
  - "Scaling"
  - "Circulation"
  - "Clearance"
  - "Slack"
  - "Boundary"
  - "Restoration Capacity"
  - "Institutional Design"
  - "Platform Governance"
  - "AI Governance"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Economic"
  - "Institutional"
  - "Platform"
  - "Governance"
  - "Community"
  - "Civilizational"
  - "AI"
  - "Security"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U3 governance / allocation / growth decision"
    - "often U4 growth narrative / market claim"
    - "often U5 capacity / repair / recurrence layer"
  symptom_visible:
    - "U4 adoption metric / revenue gain / deployment expansion / user growth / output increase / funding round / scaling announcement"
  repair_required:
    - "same or lower than the layer where repair capacity, clearance, slack, or circulation is insufficient for growth"
  validation:
    - "U6"
    - "U7"
operators:
  scaffold: "Au growth / repair-capacity trace → Π boundary and affected-load protection → Σ repair-before-growth invariant → FI affected-field and capacity feedback → Θ expansion / extraction pressure damping → ℛ repair / circulation / clearance / slack routing → Λ growth-readiness fit test → Τ growth proof over time"
  sequence:
    - "Au"
    - "Π"
    - "Σ"
    - "FI"
    - "Θ"
    - "ℛ"
    - "Λ"
    - "Τ"
state_variables:
  primary:
    - "Au"
    - "H"
    - "H_export"
    - "O"
    - "R"
    - "FI"
  secondary:
    - "BΣ"
    - "K"
    - "σ"
    - "Φ"
diagnostics:
  - "repair_capacity"
  - "circulation_integrity"
  - "clearance_integrity"
  - "natural_gain"
  - "growth_readiness"
  - "expansion_pressure"
  - "capacity_margin"
  - "extraction_pressure"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Growth Theater"
  - "Expansion Without Capacity"
  - "Scaling Before Repair"
  - "Extraction-Led Growth"
  - "Hidden Debt Growth"
  - "Capacity Overshoot"
  - "Circulation Under-Repair"
  - "Clearance Deficit"
  - "Restoration Capacity Deficit"
  - "Growth-as-Coherence"
  - "Premature Expansion"
  - "Burnout Scaling"
  - "Platform Overgrowth"
  - "Repair Deferral"
linked_restoration_arcs:
  - "RA-004"
  - "RA-006"
  - "RA-008"
  - "RA-012"
  - "RA-014"
  - "RA-025"
  - "RA-026"
  - "RA-040"
  - "RA-046"
  - "RA-049"
  - "RA-053"
  - "RA-054"
  - "RA-061"
  - "RA-062"
  - "RA-063"
  - "RA-064"
  - "RA-065"
  - "RA-066"
  - "RA-075"
  - "RA-077"
  - "RA-078"
anti_patterns:
  - "Growth Theater"
  - "Repair-Later Scaling"
  - "Growth-to-Fund-Repair Loop"
  - "Demand-as-Readiness"
  - "Lock-In Gain"
  - "Burnout Scaling"
  - "Support Debt Expansion"
  - "Clearance Deferral"
  - "Market Validation Capture"
completion_tests:
  - "repair capacity increases"
  - "circulation integrity increases"
  - "clearance integrity increases"
  - "compatibility / slack increases"
  - "slack increases"
  - "hidden debt decreases"
  - "exported hidden debt decreases"
  - "capacity margin increases"
  - "growth readiness increases"
  - "natural gain increases"
  - "extraction pressure decreases"
  - "expansion pressure is constrained until Lambda is greater than zero"
  - "coherence increases"
  - "Φ/O divergence decreases"
summary: "Repair-First Growth repairs growth theater and expansion without capacity by requiring circulation repair, hidden debt reduction, restoration capacity, and natural gain before growth or expansion is treated as coherent."

Final Calibration Rule

Repair-First Growth answers six questions:

What growth or expansion is being proposed, and what load will it add?
What repair, circulation, clearance, slack, or capacity deficit remains unresolved?
What must be repaired before growth can proceed?
Is growth emerging as natural gain or being forced through extraction, lock-in, debt, or externality export?
Does Λ show growth-readiness under current capacity and boundary conditions?
How is growth proven over time without growth theater, repair-later scaling, demand-as-readiness, or market-validation capture?