Closes the loop after the event
You sealed before commit. When reality lands, Arrival locates that sealed fork against what actually ran.
When reality arrives, the court locates it.
TESTED or UNTESTED. Not held. Not broke.
Arrival is the loop of Axiom Future — not the product name. After you seal competing stresses, when live / post-event data lands you get a clear location: TESTED or UNTESTED. Not a forecast. Not “became fact.”
Concrete benefits
Board: TESTED or UNTESTED
A clear location for diligence — green TESTED or grey-amber UNTESTED. No win/loss theatre.
Receipt-linked diligence
Location ties back to the sealed receipt you can verify — not a slide story.
Fail-closed upload
Phase 1 is manual upload only. If the upload cannot be located against the sealed stresses, the court stays fail-closed — not a soft pass.
FIN-2 / IND-1 first
Public sealed examples stay claim-gated: finance FIN-2 and industrial IND-1 first. No invented metrics. No fake sealed USP.
How the loop works
Phase 1 — manual upload only.
Choose fork → seal → declare event window (before the event) → wait → upload post-event data / submit actual execution CSV → TESTED or UNTESTED. Then claim gate.
- Seal — choose the fork (competing stresses) and seal. Receipt you can verify later.
- Declare window — event window before the event (start must not already be past).
- Wait — the event runs outside the court.
- Upload CSV — Upload post-event data / Submit actual execution CSV (Phase 1 manual). No live
api/v1/arrival. - TESTED or UNTESTED — court locates reality → TESTED (green) or UNTESTED (grey-amber). Not held. Not broke.
- Claim gate — public promotion stays behind the claim gate. Sealed examples first: FIN-2 / IND-1.