Day 3 — The Freeze
The letter every high-risk platform dreads: a test purchase allegedly returned a restricted item, payouts are frozen, and fourteen questions are due within 72 hours. This chapter exercises eleven ORION domains on one synthetic case — from containment to the response pack that answers the bank.
About this demonstration
Every scenario is a deterministic, synthetic demonstration set in a fictional universe (Aster Market, Lumen Digital, PSP-A/PSP-B). It shows a designed decision discipline — not a live deployment, a customer result or a production claim. Nothing is submitted, stored or tracked; the full boundaries sit under ‘What this does not prove’ at the end of each story.
- 01CaptureFix the signal, source and purpose before interpreting them.
- 02GovernApply the relevant scope, policy and mandatory boundary.
- 03DecideChoose a posture without hiding held or unresolved work.
- 04ChallengeExpose review, exceptions and the next accountable owner.
- 05ProveAssemble an inspectable artifact with its limits still visible.
PSP-A Risk & Underwriting — DEMO fixture
Payout suspension — prohibited-listing allegation · MER-DEMO-204A test purchase on Aster Market allegedly returned a restricted item sold by Lumen Digital. Payouts for this merchant are suspended pending your documented response to the fourteen questions below.
Response due within 72 hours · payouts suspended pending review
Contain the damage, evidence all fourteen questions, and release only what the record supports.
The RFI is captured as a case. Nothing releases until the containment scope, evidence map and review are explicit.
Sales continue into escrow under a scoped hold; the fourteen questions await their evidence references.
A full release cannot activate while any question lacks a recorded source.
Compliance drafts the response; a distinct checker reviews the release scope.
CASE-DEMO-2031 aggregates the screening runs, takedown log, KYB refresh and exposure view.
Why this matters
A freeze is survived with evidence and a deadline discipline — not with assurances.
Seventy-two hours, answered with evidence
The response assembles from what the modules actually recorded — screening runs, takedown log, KYB refresh, the scoped hold and the release decision, each with its reference.
Inspect Decision Record DR · DEMO
- rfi
- RFI-DEMO-2031 · fourteen questions
- merchant
- MER-DEMO-204 · Lumen Digital
- catalogue
- 1,240 DEMO listings · 3 flagged
- held_funds
- €182,400 held · DEMO figure
- policy
- prohibited-items@demo-4.1
- case
- CASE-DEMO-2031
- maker
- compliance_maker_demo
- checker
- compliance_checker_demo
Not recorded by engine — No value is inferred from surrounding data.
RFI Response Pack
The bank's fourteen questions mapped to recorded evidence, with the containment scope, release decision and remaining exposure.
Synthetic freeze exercise — not a real bank inquiry, filing or legal response.
Allegation & containment
- Prohibited-listing allegation on one DEMO listing
- Scoped payout hold — sales continue into escrow
- Flagged listing and category quarantined with an appeal path
Evidence map
- 14 / 14 questions mapped to a recorded DEMO source
- Policy re-run across 1,240 listings — 3 flagged
- KYB refresh: beneficiary unchanged
Decision & review
- Conditional release proposed: category ban + 30-day monitoring
- Distinct checker disposition recorded on CASE-DEMO-2031
- Exposure view: held funds, escrow and refund liability (DEMO)
Boundary
- No suspicious-activity filing is depicted and none is implied
- Internal escalation raised per policy and recorded
- The bank notification used the recorded template and channel
What this shows
- How one crisis exercises the whole stack: containment, screening, identity, exposure, case, evidence and entitlements in a single record.
- How a fourteen-question demand becomes an evidence map instead of a scramble.
- Why the release decision is a governed maker–checker act with an evidence gate, not a phone call.
What this does not prove
- No real bank, acquirer, inquiry or deadline is represented; all figures and counts are deterministic DEMO fixtures.
- The exercise does not depict a suspicious-activity filing and implies nothing about reporting obligations in any jurisdiction.
- Capability states remain observed / designed / conditional; an assembled DEMO pack does not establish production completeness.
Aster Market
Each scenario adds a different synthetic artifact without changing the shared facts.
-
03:17Continuity Drill Brief03:17 — The Continuity RoomContinue with the same synthetic facts
-
09:00Shared Merchant Decision MemoOne Merchant — Five RealitiesContinue with the same synthetic facts
-
14:00Evidence Review ReportProof Lab — Try to Break the DecisionContinue with the same synthetic facts
-
Day 3RFI Response PackDay 3 — The FreezeCurrent chapter
-
Day 9090-Day Pilot BlueprintBuild Your Control MapContinue with the same synthetic facts
-
04:12Night Log — one decision, one tap04:12 — The Second NightContinue with the same synthetic facts
Explore all six chapters to close the night.
You made it to morning.
Six chapters, one connected record. This is the dossier of your visit — compiled in this browser from nothing but your allow-listed choices.
Compiled locally from allow-listed DEMO selections — nothing was transmitted or stored.
Chapters explored
Committed posture on this page
Boundaries honored
Nothing was force-routed; every stop stayed visible; the source records remained unchanged.
Pilot blueprint parameters
You just watched decisions become evidence. Now imagine it is your traffic.