REMNIC RELAY MISSION CONTROL / BUILD WEEK 2026
Replay CHECKOUT-TOKEN-RECOVERY

04 / 12 · APPEND-ONLY CAUSAL TRACE

The checkout token split

Resolve a conflicting token refresh policy and prove a cold agent acts on it.

Agent conflict detected Two agents. Two incompatible beliefs. One observable contract.
Conflict detected

Space play · ← → step · E evidence

01 / THE DECISION LINEAGE

What the team believes

CONFLICT OPEN

BUILDER · ATLAS

ACTIVE BELIEF
Mint a new checkout token for every request and retry.
DISAGREEMENT DETECTED

SCOUT · NOVA

SOURCE-GROUNDED
Reuse the checkout-session token and refresh it only after expiry.

02 / PROOF, NOT A PROMISE

Mission receipt

RPENDING

The receipt is still accumulating causal proof.

Human approved
Cold start
Contract
Causal events
08
BEFORE · TEST WAITING AFTER · PROOF PENDING

03 / DISTRIBUTED CONTEXT

Three agents. One corrected memory.

Each card is reduced from the current Relay snapshot—not a scripted chat transcript.

04 / APPEND-ONLY CAUSAL TRACE

How the outcome changed

No hidden orchestration. Every visible turn is backed by a versioned mission event and inspectable evidence.

    DETERMINISTIC REPLAY GATE

    Review selected correction

    Mission Control will bind this approval to the exact selected correction.

    RETIRESelected stale decision
    ACTIVATESelected replacement decision
    Evidence loads from the selected correction

    Replay mode advances an integrity-checked fixture; it does not claim a live write.

    LIVE RELAY API

    Connect Mission Control

    The bearer token stays in this tab's session storage. Replay remains the safe default.

    R

    Reconstructing causal trace…