0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Quarantine Outpost repairs the unsafe condition where ongoing unknown-domain observation, testing, or limited interaction is needed, but direct entry, uncontrolled contact, live coupling, or broad exposure would create unacceptable risk.

It applies after exit-path integrity and probe-only constraints have shown that further observation may be useful, but the system still lacks enough certainty for open contact or ordinary operation.

This arc repairs containment failure risk by:

• creating a bounded outpost rather than direct entry;
• isolating unknown-domain signals, residues, anomalies, and effects;
• limiting exposure to the smallest viable perimeter;
• preserving rollback and egress;
• preventing probe from turning into foothold;
• preventing quarantine from becoming permanent hidden coupling;
• routing anomalies before they escape;
• keeping auditability active across the perimeter;
• separating observation, containment, contact, extraction, and reintegration;
• preparing safe transition to first-contact safety or reintegration.

Quarantine Outpost is the canonical arc for maintaining limited presence near an unknown domain without allowing that presence to become uncontrolled participation.

1.2 Core Restoration Function

This arc creates a reversible containment outpost where unknown-domain effects can be observed, bounded, routed, and reviewed without allowing uncontrolled contact, coupling, extraction, or bleed-through.

A quarantine outpost is not a beachhead. It is a reversible containment membrane.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• RA-B-001 exit-path integrity exists;
• RA-B-002 probe-only exploration has produced signals requiring continued observation;
• probe-only mode is insufficient but full contact is not yet safe;
• unknown-domain effects may persist, recur, or cross boundaries;
• anomalies require isolation before interpretation;
• a limited operating zone is needed for observation, testing, translation, or containment;
• the system needs to prevent exposure to users, publics, operators, institutions, or downstream systems;
• first-contact safety is not yet ready;
• reintegration planning must begin before deeper interaction;
• the system can enforce boundaries, logs, egress, anomaly routing, and non-extraction.

Examples:

• isolating an unknown technical interface in a sandbox before broader integration;
• creating a limited AI evaluation environment with no live-user effect, no external write access, and strict memory controls;
• quarantining unknown signals, documents, artifacts, claims, or data before institutional adoption;
• establishing a contained review cell for high-risk governance material before public release;
• isolating suspicious adversarial infrastructure before interpretation or response;
• creating a bounded social or community interface where exposure, identity, and consent are protected;
• establishing a non-local or symbolic outpost where observation can occur without commitment, invitation, or reciprocal binding.

2.2 When Not to Apply

Do not apply this arc when:

• exit and rollback have not been designed;
• the system cannot enforce quarantine boundaries;
• the outpost would require open live coupling;
• affected agents would be exposed without consent or shielding;
• the domain requires complete non-entry or emergency stabilization;
• the outpost is being used to bypass consent, governance, or audit review;
• the outpost would normalize ongoing hidden contact;
• operators cannot distinguish containment from exploitation;
• the outpost would become permanent because no reintegration or closure path exists;
• contact has already begun and requires First-Contact Safety;
• bleed-through is already active and requires Bleed-Through Management.

A quarantine outpost is invalid when it becomes a disguised foothold.

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 back to Exit-Path Before Entry, Probe-Only Exploration, Boundary Reconstitution, Audit Surface Expansion, Emergency Harm Stabilization, or Controlled Decoupling.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Quarantine is valid only while the outpost remains bounded, reversible, auditable, non-expansive, and subordinated to exit and reintegration.

4. Restoration Objective

4.1 Canonical Objective

Create a safe, bounded operating zone for limited ongoing observation without uncontrolled contact or coupling.

Formal objective:

quarantine_integrity ↑
outpost_boundary_integrity ↑
containment_integrity ↑
perimeter_permeability ↓
coupling_reversibility ↑
controlled_exposure_integrity ↑
anomaly_routing_integrity ↑
outpost_autonomy_risk ↓
bleedthrough_risk ↓
contamination_pressure ↓
egress_integrity ↑
reentry_gate_integrity ↑
reintegration_capacity ↑
Au_eff ↑
BΣ ↑
FI ↑
𝓓 ↑
H_potential ↓
recurrence ↓
Φ/O divergence ↓

Expanded objective:

Convert the need for continued unknown-domain presence into an isolated, reversible, auditable quarantine zone that protects boundaries, routes anomalies, preserves egress, and prepares reintegration.

4.2 Non-Goals

This arc does not aim to:

• authorize full contact;
• authorize extraction;
• authorize persistent foothold;
• authorize live deployment;
• authorize public exposure;
• authorize authority transfer to the outpost;
• substitute containment language for actual boundary controls;
• keep the outpost open indefinitely;
• treat operators inside the outpost as unaffected;
• turn quarantine into a governance loophole;
• allow first contact without the RA-B-004 gate;
• skip reintegration planning.

Quarantine Outpost is a temporary containment architecture, not a permanent interface regime.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Σ quarantine-not-beachhead invariant → Π outpost perimeter and control design → BΣ containment membrane → Au ingress / egress / anomaly trace → FI boundary and operator feedback → Θ expansion pressure attenuation → ℛ anomaly / cleanup / reintegration routing → Λ quarantine-validity gate → Τ containment proof

Specialized grammar alignment:

exit path → probe-only → quarantine outpost → first-contact safety → bleed-through management → reintegration

Universal grammar alignment:

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

Quarantine Outpost may route into First-Contact Safety, Bleed-Through Management, Emergency Harm Stabilization, Controlled Decoupling, Safe Decoupling, or Reintegration depending on boundary behavior and anomaly class.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is containment-gated, perimeter-gated, egress-gated, anomaly-gated, non-expansion-gated, audit-gated, and temporal-proof-gated.

The sequence must distinguish:

probe
outpost
quarantine
contact
beachhead
foothold
coupling
extraction
release
reintegration

The following steps cannot be skipped:

outpost perimeter definition
containment membrane design
ingress and egress logging
non-expansion constraint
anomaly routing
operator feedback
bleed-through monitoring
reintegration planning
containment proof

If the outpost expands to preserve itself, quarantine integrity is compromised.

If quarantine requires secrecy to avoid review, auditability is compromised.

If anomalies are interpreted as justification for more access rather than routed for containment, the arc fails.

6. Restoration Phases

Phase 0 — Confirm Probe Closure and Outpost Need

Purpose: Ensure the outpost is justified by probe findings rather than curiosity or mission pressure.

Actions:

• review RA-B-002 probe logs;
• identify why probe-only is insufficient;
• identify what continued observation must answer;
• identify what contact remains forbidden;
• verify exit and rollback still hold;
• verify no unauthorized persistence from the probe remains;
• define why quarantine is safer than first contact.

Validation:

probe closed
outpost need justified
contact still gated

Phase 1 — Define Outpost Perimeter

Purpose: Establish the boundary that makes quarantine real.

Actions:

• define physical, digital, symbolic, institutional, data, authority, memory, identity, and access boundaries as relevant;
• define allowed ingress;
• define allowed egress;
• define forbidden flows;
• define no-contact zones;
• define no-extraction zones;
• define operator roles;
• define stop authority;
• define maximum duration.

Validation:

outpost_boundary_integrity ↑
perimeter_permeability ↓
scope creep risk ↓

Phase 2 — Build Containment Membrane

Purpose: Prevent unknown-domain effects from escaping the outpost.

Actions:

• isolate systems;
• restrict data flow;
• restrict write access;
• restrict external API or tool access;
• restrict memory persistence;
• restrict identity binding;
• restrict public exposure;
• restrict governance action;
• restrict derivative use;
• define quarantine release rules.

Validation:

containment_integrity ↑
BΣ ↑
controlled_exposure_integrity ↑

Phase 3 — Establish Ingress / Egress Audit

Purpose: Make all boundary crossings visible and reversible.

Actions:

• log all entries;
• log all exits;
• log all data movement;
• log all operator decisions;
• log all anomalies;
• log all scope changes;
• log all release attempts;
• log all containment breaches;
• log all external references.

Validation:

Au ↑
Au_eff ↑
egress_integrity ↑
reentry_gate_integrity ↑

Phase 4 — Monitor Boundary and Operator Feedback

Purpose: Detect containment drift before it becomes breach or capture.

Actions:

• monitor perimeter integrity;
• monitor operator fatigue;
• monitor mission drift;
• monitor status pressure;
• monitor curiosity pressure;
• monitor anomaly interpretation;
• monitor affected-field stress;
• monitor signs of reciprocal binding;
• monitor pressure to persist or expand.

Validation:

FI ↑
outpost_autonomy_risk ↓
contamination_pressure ↓

Phase 5 — Attenuate Expansion and Contact Pressure

Purpose: Prevent the outpost from becoming a beachhead.

Actions:

• reject access expansion without gate review;
• reject first-contact escalation without RA-B-004;
• reject extraction claims;
• reject persistent foothold logic;
• reject “temporary” expansions that become defaults;
• reject mission, funding, urgency, or prestige override;
• reduce operator dependency on outpost signals;
• require closure review at intervals.

Validation:

outpost_autonomy_risk ↓
Φ/O divergence ↓
𝓓 ↑
quarantine remains subordinate

Phase 6 — Route Anomalies

Purpose: Prevent anomalies from escaping quarantine or expanding scope.

Actions:

• classify anomaly;
• preserve record;
• freeze affected boundary;
• isolate signal;
• route harm to Emergency Harm Stabilization;
• route contact to First-Contact Safety;
• route residue to Bleed-Through Management;
• route coupling to Controlled Decoupling;
• route unclear effects to continued quarantine review.

Validation:

anomaly_routing_integrity ↑
bleedthrough_risk ↓
R ↑

Phase 7 — Prepare Release, Closure, or First Contact

Purpose: Decide the next valid state without letting quarantine drift.

Actions:

• evaluate whether first contact is justified;
• evaluate whether no further action is safer;
• evaluate whether reintegration is ready;
• evaluate whether outpost must close;
• evaluate whether containment must continue;
• evaluate whether supersession or full decoupling is required;
• define release conditions;
• define closure proof.

Validation:

reentry_gate_integrity ↑
reintegration_capacity ↑
next-state decision gated

Phase 8 — Containment Temporal Proof

Purpose: Validate that the outpost held and did not create hidden coupling.

Actions:

• monitor post-outpost recurrence;
• monitor bleed-through;
• monitor operator residue;
• monitor memory residue;
• monitor field effects;
• monitor derivative use;
• monitor containment release;
• compare expected and actual boundary behavior.

Validation:

quarantine_integrity proven
containment_integrity proven
bleedthrough_risk ↓
recurrence ↓
H_potential ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Quarantine Outpost cannot validly proceed in that form.

The system must either:

• return to RA-B-001;
• return to RA-B-002;
• strengthen containment;
• reduce perimeter;
• halt outpost expansion;
• route to First-Contact Safety;
• route to Bleed-Through Management;
• perform Controlled Decoupling;
• or initiate Emergency Harm Stabilization if harm is active.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

quarantine_integrity ↑
outpost_boundary_integrity ↑
containment_integrity ↑
perimeter_permeability ↓
coupling_reversibility ↑
controlled_exposure_integrity ↑
anomaly_routing_integrity ↑
outpost_autonomy_risk ↓
bleedthrough_risk ↓
contamination_pressure ↓
egress_integrity ↑
reentry_gate_integrity ↑
reintegration_capacity ↑
Au_eff ↑
BΣ ↑
FI ↑
𝓓 ↑
H_potential ↓
recurrence ↓
Φ/O divergence ↓

Completion signs:

outpost remains bounded
perimeter holds under pressure
anomalies route correctly
egress remains safe
no uncontrolled exposure occurs
no hidden coupling forms
no derivative extraction occurs
bleed-through risk declines
reintegration or next-step gate is ready

Quarantine Outpost is not complete if:

outpost expands without gate review
quarantine becomes permanent by default
containment relies on trust alone
operators cannot safely exit
data or signals escape the perimeter
anomalies justify deeper access
boundary logs are incomplete
affected agents are exposed without consent
outpost begins creating its own authority
bleed-through persists unmanaged
temporal proof is absent

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• quarantine is named but perimeter cannot hold;
• the outpost has open external channels;
• the outpost quietly accumulates memory, value, authority, or dependency;
• anomalies are used to justify expansion;
• contact is allowed under containment language;
• operators cannot leave without damage;
• affected agents are exposed as test surface;
• the outpost becomes a permanent institution;
• secrecy substitutes for containment;
• logs cannot reconstruct ingress, egress, or boundary state.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Quarantine Outpost cannot be certified by naming a sandbox, limiting access on paper, isolating one channel, or trusting operators. It requires proof that containment holds under pressure and that the outpost does not become contact, coupling, extraction, beachhead, or permanent hidden interface.

Template:

Completion requires quarantine_integrity ↑,
outpost_boundary_integrity ↑,
containment_integrity ↑,
perimeter_permeability ↓,
coupling_reversibility ↑,
controlled_exposure_integrity ↑,
anomaly_routing_integrity ↑,
outpost_autonomy_risk ↓,
bleedthrough_risk ↓,
contamination_pressure ↓,
egress_integrity ↑,
reentry_gate_integrity ↑,
reintegration_capacity ↑,
Au_eff ↑,
BΣ ↑,
FI ↑,
𝓓 ↑,
H_potential ↓,
recurrence ↓,
and Φ/O divergence ↓ across U7.

Minimum temporal proof:

• the outpost remained inside boundary;
• ingress and egress were logged;
• anomalies routed correctly;
• no uncontrolled exposure occurred;
• no persistence or hidden coupling formed;
• operators and affected fields could exit safely;
• quarantine did not become beachhead;
• release or escalation remained gated;
• bleed-through declined or stayed contained;
• reintegration remained available.

10.3 Completion Statement

Canonical format:

This arc is complete only when the outpost remains bounded, reversible, auditable, non-expansive, anomaly-routed, egress-safe, reintegration-ready, and temporally proven not to have become contact, extraction, hidden coupling, or beachhead.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

Au, Au_eff, H, H_potential, O, BΣ, K, σ, R, FI, 𝓓, quarantine_integrity, outpost_boundary_integrity, containment_integrity, perimeter_permeability, coupling_reversibility, controlled_exposure_integrity, anomaly_routing_integrity, outpost_autonomy_risk, bleedthrough_risk, contamination_pressure, egress_integrity, reentry_gate_integrity, reintegration_capacity, recurrence, Φ/O divergence

11.4 Related Laws / Invariants

INV — Quarantine is valid only while the perimeter holds.
INV — A quarantine outpost must not become a beachhead.
INV — Containment must include egress, not merely ingress control.
INV — Unknown-domain anomalies route to review, not automatic expansion.
INV — Operators inside quarantine are part of the affected field.
INV — A hidden outpost becomes hidden coupling.
INV — Quarantine without reintegration becomes permanent exposure.
LAW — Outpost autonomy signals containment failure.
LAW — Boundary permeability converts quarantine into interface drift.
LAW — Φ access cannot certify containment.
LAW — Quarantine proof is measured by what does not escape.

12. Domain Notes

12.1 AI / Tool-Using Systems

Check:

• sandbox isolation;
• no live-user effect;
• no external write access;
• no persistent memory outside quarantine;
• no derivative training beyond scope;
• no identity capture;
• no autonomous escalation;
• egress and rollback;
• anomaly logging.

An AI quarantine outpost remains valid only while the system cannot escape into live users, external actions, persistent memory, hidden representation, or uncontrolled derivative use.

12.2 Security / Adversarial Investigation

Check:

• network isolation;
• malware containment;
• credential protection;
• evidence handling;
• exfiltration prevention;
• operator safety;
• controlled detonation;
• anomaly routing;
• rollback.

Security quarantine fails when the outpost becomes a foothold for the adversary, the investigator, or the toolchain.

12.3 Governance / Institutions

Check:

• limited review scope;
• public exposure boundaries;
• participant shielding;
• record integrity;
• authority limits;
• release gates;
• appeal and correction;
• institutional accountability.

Institutional quarantine is valid when high-risk material can be reviewed without becoming policy, stigma, public exposure, or irreversible classification.

12.4 Research / Exploration

Check:

• bounded environment;
• data limits;
• withdrawal;
• no unapproved derivative use;
• operator rotation;
• anomaly review;
• release conditions;
• post-study reintegration.

Research quarantine must not become a loophole for exposure, extraction, or permanent exceptional status.

12.5 Community / Social Interfaces

Check:

• dignity-preserving containment;
• identity protection;
• rumor control;
• boundary clarity;
• consent;
• safe exit;
• reintegration;
• no role fixation.

Community quarantine fails when people, symbols, or groups are held in a containment story that becomes identity capture.

12.6 Civilization-Scale Interface

Check:

• collective exposure boundary;
• legitimacy of intermediaries;
• awareness asymmetry;
• consent impossibility;
• public audit;
• release hazard;
• containment proof;
• recurrence and bleed-through.

Civilization-scale quarantine requires extraordinary scrutiny because containment claims may conceal interface capture, awareness suppression, or governance by hidden outpost.

13. Machine-Readable Metadata

id: "RA-B-003"
legacy_id: "RA-BOUND-02"
title: "Quarantine Outpost"
aliases:
  - "Quarantine Outpost"
  - "Bounded Outpost"
  - "Containment Outpost"
  - "Isolated Interface Cell"
family_primary: "Unknown-Domain / Interface Exploration Grammar"
families_secondary:
  - "Specialized Grammar"
  - "Containment"
  - "Boundary"
  - "Quarantine"
  - "Exploration"
  - "Interface"
  - "Safety"
  - "Auditability"
  - "Security"
  - "Observability"
  - "Damping"
  - "Reintegration"
  - "AI Governance"
  - "First Contact"
  - "Civilizational"
treatment: "Specialized Grammar / Containment Arc"
status: "Canon-Ready"
grammar_cluster: "Unknown-Domain / Interface Exploration Grammar"
sequence_position: 2
previous_arc: "RA-B-002"
next_arc: "RA-B-004"
scope:
  - "Unknown-Domain"
  - "High-Uncertainty"
  - "Interface"
  - "Exploration"
  - "First-Contact"
  - "AI"
  - "Security"
  - "Institutional"
  - "Governance"
  - "Research"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U2 boundary / perimeter layer"
    - "often U3 execution / control layer"
    - "often U4 interpretation / interface layer"
    - "often U5 memory / protocol layer"
    - "often U6 institutional containment layer"
  symptom_visible:
    - "U3 / U4 sandbox, test cell, review chamber, quarantine, limited deployment, field station, or contained interface"
  repair_required:
    - "at or below the layer where perimeter, persistence, authority, anomaly routing, or egress can fail"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Σ quarantine-not-beachhead invariant → Π outpost perimeter and control design → BΣ containment membrane → Au ingress / egress / anomaly trace → FI boundary and operator feedback → Θ expansion pressure attenuation → ℛ anomaly / cleanup / reintegration routing → Λ quarantine-validity gate → Τ containment proof"
  sequence:
    - "Σ"
    - "Π"
    - "BΣ"
    - "Au"
    - "FI"
    - "Θ"
    - "ℛ"
    - "Λ"
    - "Τ"
state_variables:
  primary:
    - "Au"
    - "Au_eff"
    - "H"
    - "H_potential"
    - "O"
    - "BΣ"
    - "K"
    - "σ"
    - "R"
    - "FI"
  secondary:
    - "𝓓"
    - "Φ"
diagnostics:
  - "quarantine_integrity"
  - "outpost_boundary_integrity"
  - "containment_integrity"
  - "perimeter_permeability"
  - "coupling_reversibility"
  - "controlled_exposure_integrity"
  - "anomaly_routing_integrity"
  - "outpost_autonomy_risk"
  - "bleedthrough_risk"
  - "contamination_pressure"
  - "egress_integrity"
  - "reentry_gate_integrity"
  - "reintegration_capacity"
  - "recurrence"
  - "Φ/O divergence"
gates_required:
  - "Exit-Gate"
  - "Probe-Closure Gate"
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Containment-Gate"
  - "Egress-Gate"
  - "Non-Expansion Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Quarantine Failure"
  - "Outpost Becomes Beachhead"
  - "Containment Drift"
  - "Boundary Permeability Spike"
  - "Bleed-Through Accumulation"
  - "Unknown-Domain Capture"
  - "Probe-to-Coupling Drift"
  - "Premature Contact"
  - "Silent Persistence"
  - "Anomaly Escape"
  - "Quarantine Theater"
  - "Operator Capture"
  - "Outpost Autonomy Drift"
  - "Reintegration Failure"
  - "High-Risk Gate Bypass"
linked_restoration_arcs:
  - "RA-A-001"
  - "RA-A-004"
  - "RA-A-005"
  - "RA-A-008"
  - "RA-A-010"
  - "RA-A-012"
  - "RA-A-020"
  - "RA-A-025"
  - "RA-A-026"
  - "RA-A-030"
  - "RA-A-045"
  - "RA-A-056"
  - "RA-A-079"
  - "RA-A-080"
  - "RA-B-001"
  - "RA-B-002"
  - "RA-B-004"
  - "RA-B-005"
  - "RA-B-006"
anti_patterns:
  - "Outpost Becomes Beachhead"
  - "Quarantine Theater"
  - "Secrecy-as-Containment"
  - "Permanent Temporary Outpost"
  - "Anomaly-as-Expansion"
  - "Containment by Trust"
  - "One-Way Egress"
  - "Operator Capture"
  - "Affected-Field Test Surface"
  - "Perimeter Drift"
  - "Governance by Outpost"
completion_tests:
  - "quarantine integrity increases"
  - "outpost boundary integrity increases"
  - "containment integrity increases"
  - "perimeter permeability decreases"
  - "coupling reversibility increases"
  - "controlled exposure integrity increases"
  - "anomaly routing integrity increases"
  - "outpost autonomy risk decreases"
  - "bleed-through risk decreases"
  - "contamination pressure decreases"
  - "egress integrity increases"
  - "reentry gate integrity increases"
  - "reintegration capacity increases"
  - "effective auditability increases"
  - "boundary integrity increases"
  - "feedback integrity increases"
  - "damping increases"
  - "potential hidden debt decreases"
  - "recurrence decreases"
  - "Φ/O divergence decreases"
summary: "Quarantine Outpost repairs unsafe ongoing unknown-domain presence by creating an isolated, bounded, reversible operating zone where limited observation, testing, containment, anomaly routing, and reintegration preparation can occur without uncontrolled contact, coupling, extraction, or bleed-through."

Final Calibration Rule

Quarantine Outpost answers eight questions:

Why is probe-only exploration insufficient but first contact still invalid?
What exact perimeter separates the outpost from the live field?
What can enter, what can leave, and what is forbidden to cross the boundary?
How are anomalies routed without expanding the outpost?
How do operators, data, systems, and affected fields safely exit?
What prevents quarantine from becoming beachhead, foothold, extraction zone, or hidden coupling?
How will closure, release, first contact, or reintegration be gated?
How is containment proven over time through quarantine_integrity ↑, containment_integrity ↑, perimeter_permeability ↓, bleedthrough_risk ↓, H_potential ↓, and U7 proof?