USER-SUPPLIED BLUEPRINT · INTENDED ARCHITECTURE

A gate is a decision, not a conveyor belt.

The CP0–CP9 governance map has branches, returns, custody and a public boundary.

This is a reading of the supplied design, not evidence that the pipeline has run. All route exploration below is illustrative and uses no real documents or telemetry.

Open the simulated 3D exhibit →

Follow a branch

Choose an outcome at CP2. The route changes; checkpoint numbers do not imply that every object visits every checkpoint. CP labels are checkpoint identities, not L0–L10 grades; this exhibit computes no grade.

Promotion

CP2 → Promotion → CP4 → ArkChain → Registry → CP5 → Library / Archive custody → CP6 → Final REDTEAM → CP7 → SymēonMesh airlock → CP8 → K² → CP9 → KO² → TheRellWorld → Public.

CP3 belongs to reclamation, not the promotion route. Parking/hold has no outgoing release route specified in the supplied image.

The supplied map

AiR governance flowchart. An accessible text transcription follows.

Open the original image at full size

Accessible route transcription

Entry and classification

GALAXIA and approved sources → eKO² → KO² → CP0 Source Boundary → AiR Entry / Raw Source Canon → CP1 Classification → ArkLex → CP2 REDTEAM⊕GODMODE and weighted gate.

Promotion

CP2 → Promotion → CP4 Promotion Authority → ArkChain → Registry → CP5 Library Custody → Library / Archive Custody.

Remediation and hold

Remediation returns to CP2. Parking / Hold remains a hold in this diagram; no automatic promotion or release is inferred.

Reclamation

CP2 → Reclamation → CP3 Reclamation Doctrine → DUST_BUNNI → ClawLab. The diagram shows a cold archive destination and a return toward CP1 from the salvage path. It does not say every archived item is automatically returned.

Trust and public egress

Library custody → CP6 Object-Class Doctrine → Final REDTEAM⊕GODMODE → CP7 Mesh Airlock → SymēonMesh.io last cleaning → CP8 K² Admission → K² Ark-internal trusted access → CP9 Public Egress → KO² → TheRellWorld → Public. A return from the cleaning stage toward CP6 is shown.

Cross-cutting records and authority

Living Report Card, ArkLedger and the Doctrine Enforcement Plane connect across the flow. Their dotted connectors are preserved in the source image; exact timing and execution semantics are not specified here.

Worlds are not checkpoints

The separate Ark Nodes resource describes behavioral worlds, such as Sonic’s Judicial Metropolis, the TeckBrowser Field and Library retrieval as travel. Those are illustrative environments, not one-to-one mappings to these ten checkpoints, inhabitants or hardware nodes.

Proof boundary

OBSERVED

The user-supplied image defines this branching design.

ARCHITECTURE

Promotion, remediation, hold and reclamation have distinct paths.

UNVERIFIED

Actual execution, grading accuracy, receipts, integration and publication safety require runtime tests.

NEXT CHECK

Run a permitted synthetic input through each implemented outcome and compare resulting receipts with this design.