0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Interface Bypass & Decoupling repairs the civilization-scale condition where an intermediary, interface channel, platform, governance layer, institution, policy stack, access route, evidence custodian, or public interpretation surface has become captured, coercive, legitimacy-failed, or structurally invalid.

It applies when legitimacy cannot be restored by asking the captured interface to reform itself, and the field must separate valid function from invalid routing.

This arc repairs captured-interface dependency by:

• identifying which interface channel is captured or invalid;
• distinguishing the function that must be preserved from the intermediary that must be bypassed;
• reducing dependency on captured authority, evidence custody, interpretation, access, or service routes;
• creating alternate routes for truth, appeal, coordination, service, governance, and repair;
• preserving evidence continuity during decoupling;
• protecting public agency and affected-field access;
• preventing bypass from becoming uncontrolled collapse;
• preventing captured authority from reentering through new channels;
• routing old interface debt to repair or containment;
• validating over time that hidden debt falls and coherence rises outside the captured route.

Interface Bypass & Decoupling is the canonical arc for moving around a captured interface without abandoning the people, evidence, services, or repair obligations trapped behind it.

1.2 Core Restoration Function

This arc separates legitimate function from captured interface routing by creating auditable alternate pathways, reducing dependency, protecting affected fields, and validating safe decoupling over time.

Bypass is not revenge against the old interface.

Bypass is the restoration of routing integrity.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• an interface channel controls evidence, access, interpretation, legitimacy, or public action illegitimately;
• legitimacy re-anchoring cannot proceed because authority remains captured;
• intermediary control blocks awareness, appeal, correction, or repair;
• public agency depends on a channel that is no longer trustworthy;
• affected fields cannot reach truth or remedy through the official interface;
• the captured interface exports burden while preserving local order;
• the field needs alternate routes for communication, evidence, governance, service, or repair;
• decoupling can reduce hidden debt without causing uncontrolled collapse;
• service continuity, transition safety, and evidence continuity can be preserved;
• the system must prevent captured authority from reentering through replacement channels.

Examples:

• routing AI governance appeals outside a captured evaluator or policy stack;
• creating independent evidence custody when an institution controls the record;
• bypassing a platform moderation or visibility system that suppresses affected-field correction;
• decoupling public communication from an intermediary that steers awareness;
• separating public safety advisories from a compromised disclosure channel;
• creating alternate governance pathways when official authority is legitimacy-failed;
• reducing dependency on a captured interface while preserving service access for affected users.

2.2 When Not to Apply

Do not apply this arc when:

• the interface is still repairable through legitimacy re-anchoring, audit expansion, or governance restoration;
• bypass would create more harm than continued containment;
• alternate routes are not ready enough to preserve affected-field access;
• decoupling would erase evidence or repair obligations;
• the proposal is abandonment disguised as bypass;
• the proposal is power seizure disguised as decoupling;
• captured channels are being bypassed without responsibility assignment;
• public agency would decrease because the alternate route is less accountable;
• transition safety cannot be preserved;
• the old interface is non-restorable and full Supersession is required instead;
• active harm requires Emergency Harm Stabilization first.

Interface bypass is invalid when it replaces one captured channel with another.

2.3 Required Preconditions

Before this arc begins, the following must be true:

If required preconditions fail:

Arc cannot validly proceed.

The system must route to Audit Surface Expansion, Legitimacy Re-Anchoring, Responsibility Gradient Mapping, Parallel Attractor Seeding, Dignity-Preserving Transition, Governance-Level Restoration, or Emergency Harm Stabilization.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Interface bypass is valid only when it preserves legitimate function while reducing dependency on captured routing and protecting affected fields during transition.

4. Restoration Objective

4.1 Canonical Objective

Reduce or remove dependency on a captured interface while preserving function, evidence, public agency, and repair.

Formal objective:

interface_capture_risk ↓
bypass_integrity ↑
decoupling_integrity ↑
dependency_reduction ↑
alternate_route_integrity ↑
public_agency_restoration ↑
intermediary_control_risk ↓
evidence_continuity ↑
authority_continuity ↑
service_continuity ↑
transition_safety ↑
capture_reentry_risk ↓
legitimacy_transfer ↑
coercive_dependency_pressure ↓
H_public ↓
H_interface ↓
Au_eff ↑
BΣ ↑
FI ↑
𝓓 ↑
O_global ↑
recurrence ↓
Φ/O divergence ↓

Expanded objective:

Convert captured interface dependency into auditable alternate routing that preserves truth, service, public agency, repair obligations, and temporal proof.

4.2 Non-Goals

This arc does not aim to:

• destroy the old interface for symbolic reasons;
• abandon affected fields;
• erase evidence;
• bypass accountability;
• replace one captured authority with another;
• treat alternate route existence as proof of safety;
• force decoupling before transition support exists;
• collapse service continuity;
• use bypass to seize control;
• declare supersession before a higher-order attractor is stable;
• treat decoupling as complete without U7 proof.

Bypass is a routing repair. Supersession is a basin replacement. They may link, but they are not the same arc.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Σ function-not-captured-route invariant → Au dependency / evidence / authority trace → BΣ coupling and public-agency boundary repair → Π alternate routing and decoupling plan → FI affected-field route feedback → Θ dependency / retaliation / collapse pressure attenuation → ℛ transition / service / repair routing → Λ bypass-validity gate → Τ decoupling proof

Specialized grammar alignment:

containment-first stabilization → asymmetric awareness injection → legitimacy re-anchoring → interface bypass and decoupling → inversion exhaustion / self-exposure → post-interface restoration

Universal grammar alignment:

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

Interface Bypass & Decoupling may route into Inversion Exhaustion / Self-Exposure, Post-Interface Restoration, Supersession, Controlled Decoupling, Parallel Attractor Seeding, Dignity-Preserving Transition, Governance-Level Restoration, or Future-Agency Restoration.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is dependency-gated, evidence-gated, alternate-route-gated, affected-field-gated, transition-gated, anti-capture-gated, and temporal-proof-gated.

The sequence must distinguish:

function
interface
intermediary
route
dependency
bypass
decoupling
abandonment
replacement
supersession

The following steps cannot be skipped:

captured route identification
function / interface distinction
dependency map
evidence continuity
alternate route design
affected-field feedback
transition safety
capture reentry prevention
temporal proof

If bypass lowers public agency, it is not restoration.

If decoupling breaks evidence custody, it may protect capture.

If alternate route cannot hold, bypass must remain staged or route to Parallel Attractor Seeding.

6. Restoration Phases

Phase 0 — Identify Captured Interface and Preserved Function

Purpose: Separate what must be preserved from what must be bypassed.

Actions:

• identify captured channel;
• identify legitimate function;
• identify invalid authority claims;
• identify evidence custody risk;
• identify service dependencies;
• identify affected fields;
• identify public agency loss;
• identify repair obligations trapped behind the interface.

Validation:

captured interface named
legitimate function separated
bypass question valid

Phase 1 — Map Dependency and Coupling

Purpose: Understand what will be affected by decoupling.

Actions:

• map user dependency;
• map public dependency;
• map institutional dependency;
• map technical dependency;
• map evidence dependency;
• map appeal / correction dependency;
• map service dependency;
• map governance dependency;
• map economic or labor dependency.

Validation:

dependency map complete enough
coercive_dependency_pressure visible
transition risk legible

Phase 2 — Preserve Evidence and Authority Trace

Purpose: Prevent decoupling from destroying accountability.

Actions:

• preserve records;
• preserve decision provenance;
• preserve evidence custody;
• preserve appeal history;
• preserve public claims;
• preserve interface logs;
• preserve repair obligations;
• preserve chain of responsibility.

Validation:

evidence_continuity ↑
authority_traceability ↑
Au_eff ↑

Phase 3 — Design Alternate Route

Purpose: Create a safer pathway before dependency is cut.

Actions:

• define alternate communication route;
• define alternate evidence route;
• define alternate appeal route;
• define alternate correction route;
• define alternate governance route;
• define service continuity route;
• define public agency route;
• define independent oversight or review path.

Validation:

alternate_route_integrity ↑
public_agency_restoration ↑
service_continuity ↑

Phase 4 — Stage Decoupling

Purpose: Reduce dependency without causing collapse.

Actions:

• reduce captured routing;
• shift evidence custody;
• shift authority claims;
• shift user or public access;
• shift service dependencies;
• shift correction and appeal channels;
• protect vulnerable groups;
• maintain rollback where possible;
• document each decoupling step.

Validation:

decoupling_integrity ↑
dependency_reduction ↑
transition_safety ↑

Phase 5 — Attenuate Capture and Retaliation Pressure

Purpose: Prevent the captured interface from forcing re-dependency.

Actions:

• monitor retaliation;
• monitor misinformation;
• monitor access restriction;
• monitor service sabotage;
• monitor legitimacy attacks;
• monitor rebranding of captured authority;
• monitor capture migration to alternate route;
• reduce panic or dependency narratives.

Validation:

capture_reentry_risk ↓
intermediary_control_risk ↓
𝓓 ↑

Phase 6 — Route Repair Obligations

Purpose: Ensure bypass does not abandon old debt.

Actions:

• assign repair obligations;
• route compensation or restitution where needed;
• route governance repair;
• route affected-field support;
• route evidence review;
• route accountability continuity;
• route future-compatible obligations;
• preserve claims against old interface.

Validation:

H_interface ↓
H_public ↓
accountability_continuity ↑
R ↑

Phase 7 — Transfer or Rebuild Legitimacy

Purpose: Prevent the alternate route from becoming another captured authority.

Actions:

• define new authority basis;
• define oversight;
• define appeal;
• define correction;
• define participation;
• define transparency;
• define limits;
• define review cadence;
• keep old captured authority from reentering by default.

Validation:

legitimacy_transfer ↑
authority_continuity ↑
public_agency_restoration ↑

Phase 8 — Decoupling Temporal Proof

Purpose: Validate that bypass restored routing integrity.

Actions:

• monitor dependency reduction;
• monitor service continuity;
• monitor evidence continuity;
• monitor public agency;
• monitor hidden debt;
• monitor capture reentry;
• monitor recurrence;
• monitor global coherence.

Validation:

dependency_reduction ↑
interface_capture_risk ↓
H_interface ↓
O_global ↑
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Interface Bypass & Decoupling cannot validly complete.

The system must either:

• return to Legitimacy Re-Anchoring;
• expand audit surface;
• preserve evidence first;
• seed a parallel route;
• stage decoupling more slowly;
• protect affected fields;
• route to Controlled Decoupling;
• route to Supersession;
• or withhold bypass claims until temporal proof exists.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

interface_capture_risk ↓
bypass_integrity ↑
decoupling_integrity ↑
dependency_reduction ↑
alternate_route_integrity ↑
public_agency_restoration ↑
intermediary_control_risk ↓
evidence_continuity ↑
authority_continuity ↑
service_continuity ↑
transition_safety ↑
capture_reentry_risk ↓
legitimacy_transfer ↑
coercive_dependency_pressure ↓
H_public ↓
H_interface ↓
Au_eff ↑
BΣ ↑
FI ↑
𝓓 ↑
O_global ↑
recurrence ↓
Φ/O divergence ↓

Completion signs:

captured interface is identified
legitimate function is preserved
dependency on captured route declines
alternate route holds
evidence continuity holds
affected-field agency improves
transition safety holds
capture reentry risk declines
hidden debt decreases
temporal proof holds

Interface Bypass & Decoupling is not complete if:

captured route remains necessary
alternate route cannot hold
evidence breaks during transition
public agency decreases
affected fields are abandoned
old authority reenters through new route
service collapses
hidden debt relocates
decoupling is declared but dependency remains
temporal proof is absent

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• bypass is announced but the captured route still controls evidence;
• decoupling shifts users into a less accountable route;
• service continuity is sacrificed without support;
• old authority quietly controls the alternate route;
• evidence is lost during transition;
• bypass is used to avoid repair obligations;
• the captured interface is renamed rather than decoupled;
• affected fields lose appeal, correction, or participation;
• parallel route capacity is exaggerated;
• dependency metrics do not improve.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Interface Bypass & Decoupling cannot be certified by announcing an alternate route, removing a visible intermediary, changing ownership, publishing a new policy, or routing through a different brand. It requires proof that dependency on the captured interface decreases while public agency, evidence continuity, service continuity, and coherence improve.

Template:

Completion requires interface_capture_risk ↓,
bypass_integrity ↑,
decoupling_integrity ↑,
dependency_reduction ↑,
alternate_route_integrity ↑,
public_agency_restoration ↑,
intermediary_control_risk ↓,
evidence_continuity ↑,
authority_continuity ↑,
service_continuity ↑,
transition_safety ↑,
capture_reentry_risk ↓,
legitimacy_transfer ↑,
coercive_dependency_pressure ↓,
H_public ↓,
H_interface ↓,
Au_eff ↑,
BΣ ↑,
FI ↑,
𝓓 ↑,
O_global ↑,
recurrence ↓,
and Φ/O divergence ↓ across U7.

Minimum temporal proof:

• dependency on captured route declines;
• evidence remains intact and reviewable;
• affected fields retain access, appeal, correction, or service;
• alternate route holds under load;
• transition safety holds;
• captured authority does not reenter;
• hidden debt decreases rather than relocating;
• legitimacy transfers to a more accountable route;
• recurrence of captured routing declines.

10.3 Completion Statement

Canonical format:

This arc is complete only when the captured interface no longer controls essential routing, legitimate function is preserved through auditable alternate pathways, evidence and service continuity hold, affected-field agency improves, capture reentry risk declines, hidden debt decreases, and U7 proof shows that bypass restored coherence rather than merely relocating control.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

Au, Au_eff, H, H_public, H_interface, O, O_local, O_global, BΣ, K, σ, R, FI, 𝓓, interface_capture_risk, bypass_integrity, decoupling_integrity, dependency_reduction, alternate_route_integrity, public_agency_restoration, intermediary_control_risk, evidence_continuity, authority_continuity, service_continuity, transition_safety, capture_reentry_risk, legitimacy_transfer, coercive_dependency_pressure, recurrence, Φ/O divergence

11.4 Related Laws / Invariants

INV — Legitimate function is not identical to the captured route.
INV — Bypass must preserve evidence continuity.
INV — Decoupling must not abandon affected fields.
INV — Alternate routing must increase agency, not merely change control.
INV — Captured authority must not reenter through the replacement path.
INV — Service continuity is part of transition safety.
INV — Bypass without repair obligation routing preserves hidden debt.
LAW — Captured channels frame dependency as legitimacy.
LAW — Decoupling without alternate capacity becomes collapse.
LAW — Φ continuity cannot certify routing integrity.
LAW — Bypass proof is measured by dependency reduction and reduced hidden debt.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• evaluator capture;
• policy stack capture;
• memory access route;
• user appeal route;
• model governance route;
• evidence custody;
• alternate oversight;
• user agency.

AI interface bypass succeeds when users and affected fields can reach correction, appeal, evidence, and governance outside the captured AI policy or evaluator route.

12.2 Platform Governance

Check:

• moderation channel;
• visibility routing;
• creator appeal;
• user data access;
• recommendation dependency;
• evidence custody;
• independent review;
• service continuity.

Platform bypass fails when it simply moves users from one opaque route to another.

12.3 Security / Public Risk

Check:

• disclosure channel;
• advisory route;
• evidence custody;
• patch coordination;
• public safety dependency;
• adversarial capture;
• service continuity;
• auditability.

Security bypass is valid when captured disclosure or coordination paths are replaced without breaking evidence or public protection.

12.4 Institutions / Governance

Check:

• authority registry;
• oversight route;
• appeal and correction;
• public reporting;
• independent audit;
• policy pathway;
• legitimacy transfer;
• responsibility preservation.

Institutional bypass succeeds when authority moves toward a more accountable route rather than merely changing office or committee.

12.5 Media / Public Awareness

Check:

• captured narrative channel;
• evidence access;
• correction path;
• public comprehension;
• amplification risk;
• source custody;
• alternate public route;
• narrative capture risk.

Media bypass restores public agency by reducing dependency on captured interpretation channels.

12.6 Civilization-Scale Interface

Check:

• intermediary access control;
• public awareness route;
• evidence custody;
• legitimacy transfer;
• public consent surface;
• capture reentry;
• post-interface restoration;
• supersession readiness.

Civilization-scale bypass must preserve the public’s future ability to know, contest, repair, and participate outside the captured interface.

13. Machine-Readable Metadata

id: "RA-C-004"
legacy_id: "RA-DECOUPLE-C3"
title: "Interface Bypass & Decoupling"
aliases:
  - "Interface Bypass"
  - "Civilization-Scale Decoupling"
  - "Captured Interface Bypass"
  - "Intermediary Decoupling"
family_primary: "Civilization-Scale Interface Grammar"
families_secondary:
  - "Specialized Grammar"
  - "Civilization-Scale Interface"
  - "Decoupling"
  - "Bypass"
  - "Boundary"
  - "Governance"
  - "Legitimacy"
  - "Public Agency"
  - "Interface Capture"
  - "Auditability"
  - "Sovereignty"
  - "Transition Design"
  - "AI Governance"
  - "Platform Governance"
  - "Security"
  - "Civilizational"
treatment: "Specialized Grammar / Interface Decoupling Arc"
status: "Canon-Ready"
grammar_cluster: "Civilization-Scale Interface Grammar"
sequence_position: 3
previous_arc: "RA-C-003"
next_arc: "RA-C-005"
scope:
  - "Civilizational"
  - "Institutional"
  - "Governance"
  - "Platform"
  - "AI"
  - "Security"
  - "Public Interface"
  - "Media"
  - "Cognitive Infrastructure"
  - "Legitimacy Systems"
  - "High-Risk Interface"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U2 coupling / boundary layer"
    - "often U3 governance or platform route layer"
    - "often U4 interface interpretation layer"
    - "often U5 evidence / memory custody layer"
    - "often U6 legitimacy infrastructure"
    - "often U7 trajectory layer"
  symptom_visible:
    - "U4 / U6 blocked appeal, captured public channel, official routing failure, evidence access dispute, interface mistrust, or public dependency"
  repair_required:
    - "at or below the layer where routing, authority, evidence custody, service dependency, or intermediary control persists"
  validation:
    - "U6"
    - "U7"
operators:
  scaffold: "Σ function-not-captured-route invariant → Au dependency / evidence / authority trace → BΣ coupling and public-agency boundary repair → Π alternate routing and decoupling plan → FI affected-field route feedback → Θ dependency / retaliation / collapse pressure attenuation → ℛ transition / service / repair routing → Λ bypass-validity gate → Τ decoupling proof"
  sequence:
    - "Σ"
    - "Au"
    - "BΣ"
    - "Π"
    - "FI"
    - "Θ"
    - "ℛ"
    - "Λ"
    - "Τ"
state_variables:
  primary:
    - "Au"
    - "Au_eff"
    - "H"
    - "H_public"
    - "H_interface"
    - "O"
    - "O_local"
    - "O_global"
    - "BΣ"
    - "K"
    - "σ"
    - "R"
    - "FI"
  secondary:
    - "𝓓"
    - "Φ"
diagnostics:
  - "interface_capture_risk"
  - "bypass_integrity"
  - "decoupling_integrity"
  - "dependency_reduction"
  - "alternate_route_integrity"
  - "public_agency_restoration"
  - "intermediary_control_risk"
  - "evidence_continuity"
  - "authority_continuity"
  - "service_continuity"
  - "transition_safety"
  - "capture_reentry_risk"
  - "legitimacy_transfer"
  - "coercive_dependency_pressure"
  - "recurrence"
  - "Φ/O divergence"
gates_required:
  - "Dependency-Gate"
  - "Evidence-Gate"
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Alternate Route Gate"
  - "Transition Safety Gate"
  - "Anti-Capture Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Interface Capture"
  - "Intermediary Control"
  - "Captured Channel Dependency"
  - "Legitimacy-Failed Interface"
  - "Coercive Interface Coupling"
  - "Bypass Failure"
  - "Decoupling Failure"
  - "Evidence Breakage During Decoupling"
  - "Public Agency Suppression"
  - "Captured Authority Reentry"
  - "Transition Harm"
  - "Service Collapse After Bypass"
  - "Parallel Route Under-Capacity"
  - "Decoupling Theater"
  - "High-Risk Gate Bypass"
linked_restoration_arcs:
  - "RA-A-004"
  - "RA-A-005"
  - "RA-A-009"
  - "RA-A-010"
  - "RA-A-012"
  - "RA-A-014"
  - "RA-A-020"
  - "RA-A-024"
  - "RA-A-025"
  - "RA-A-030"
  - "RA-A-040"
  - "RA-A-043"
  - "RA-A-046"
  - "RA-A-049"
  - "RA-A-050"
  - "RA-A-051"
  - "RA-A-052"
  - "RA-A-056"
  - "RA-A-078"
  - "RA-A-079"
  - "RA-A-080"
  - "RA-C-001"
  - "RA-C-002"
  - "RA-C-003"
  - "RA-C-005"
  - "RA-C-006"
anti_patterns:
  - "Bypass Theater"
  - "Decoupling as Abandonment"
  - "Evidence Break Bypass"
  - "Captured Route Rebrand"
  - "Parallel Route Under-Capacity"
  - "Authority Reentry"
  - "Control Seizure Bypass"
  - "Service Collapse Bypass"
  - "Dependency Denial"
  - "Repair Obligation Evasion"
  - "Less Accountable Alternative"
completion_tests:
  - "interface capture risk decreases"
  - "bypass integrity increases"
  - "decoupling integrity increases"
  - "dependency reduction increases"
  - "alternate route integrity increases"
  - "public agency restoration increases"
  - "intermediary control risk decreases"
  - "evidence continuity increases"
  - "authority continuity increases"
  - "service continuity increases"
  - "transition safety increases"
  - "capture reentry risk decreases"
  - "legitimacy transfer increases"
  - "coercive dependency pressure decreases"
  - "public hidden debt decreases"
  - "interface hidden debt decreases"
  - "effective auditability increases"
  - "boundary integrity increases"
  - "feedback integrity increases"
  - "damping increases"
  - "global coherence increases"
  - "recurrence decreases"
  - "Φ/O divergence decreases"
summary: "Interface Bypass & Decoupling repairs captured, invalid, coercive, or legitimacy-failed interface channels by separating legitimate function from the captured intermediary, preserving evidence and public agency, reducing dependency, creating alternate routing, and validating that decoupling lowers hidden debt without uncontrolled collapse."

Final Calibration Rule

Interface Bypass & Decoupling answers nine questions:

What interface, intermediary, channel, route, or authority layer is captured or invalid?
What legitimate function must be preserved apart from that interface?
Who depends on the captured route, and what would decoupling affect?
What evidence, authority, service, appeal, or repair obligations must remain continuous?
What alternate route can hold the function more coherently?
How will affected fields retain agency, access, correction, and support during transition?
What prevents captured authority from reentering through the new route?
What old hidden debt remains assigned after bypass?
How is decoupling proven over time through dependency_reduction ↑, interface_capture_risk ↓, alternate_route_integrity ↑, H_interface ↓, O_global ↑, recurrence ↓, and U7 proof?