Synthetic scenario · illustrative product experience
Synthetic merchant-change exercise

One Merchant — Five Realities

Lumen Digital requests a new operating corridor and settlement-beneficiary change. Five teams see different consequences, but the underlying facts must never fork into five versions of truth.

2–4 minutesCOO · CRO/MLRO · CTO/CISO · Product
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.

← All scenarios
  1. 01CaptureFix the signal, source and purpose before interpreting them.
  2. 02GovernApply the relevant scope, policy and mandatory boundary.
  3. 03DecideChoose a posture without hiding held or unresolved work.
  4. 04ChallengeExpose review, exceptions and the next accountable owner.
  5. 05ProveAssemble an inspectable artifact with its limits still visible.
Skip to the outcome ↓
01 · FIXED FACTS
The facts do not change with the lens

The facts do not change with the lens

Merchant
Lumen Digital · MER-DEMO-204
Current posture
Existing activity continues inside a bounded synthetic corridor.
Requested change
Add a corridor and change the settlement beneficiary.
Unresolved evidence
Beneficiary evidence is incomplete.
Additional signal
A synthetic rise in refund-pattern alerts requires review.
Route context
Eligibility differs between PSP-A and PSP-B.
02 · FIVE REALITIES

1 · Examine the same merchant through five decision lenses

The lens changes priority and permitted action—not facts.

Lens changed. The facts remain unchanged.MER-DEMO-204FACTSET-DEMO-ASTER-01
Can the business continue or expand without an unmanaged dependency?
  • Current permitted scope
  • Unresolved conditions
  • Decision owner and review date
03 · SCOPE
2 · Set the operating scope
04 · OWNERSHIP

3 · Name the controlling condition and owner

Your mission

Keep one merchant fact set intact while five functions make their responsibilities explicit.

The Lumen Digital dossier is fixed before any team applies its decision lens.

Flow

Existing bounded activity and the requested expansion remain separate paths.

Guardrail

Incomplete beneficiary evidence prevents the requested change from becoming executable.

Ownership

Each lens exposes a different responsibility without changing the source facts.

Evidence

DR-DEMO-MERCHANT-084 anchors the synthetic proposal, condition and review state.

Why this matters

Shared facts reduce contradictory decisions while preserving functional accountability.

OUTCOME

One merchant context, explicit ownership

The proposal distinguishes current permission from requested expansion and records what must happen before scope can change.

DEMO · READY TO REVIEW
2 · Set the operating scopeContinue under a controlled corridor
Controlling conditionBeneficiary verification
Next accountable owner / Review pointRisk & Compliance · Within 7 days
Inspect Decision Record DR · DEMO
decision_recordFIXTURE
record_id
DR-DEMO-MERCHANT-084
merchant
MER-DEMO-204 · Lumen Digital
proposal
corridor + settlement-beneficiary change
identity_owner
GATE · onboarding and identity context
policy_owner
SENTINEL · screening and disposition
case
CASE-DEMO-MERCHANT-084
maker
operations_owner_demo
status
CONDITIONAL · synthetic fixture

Not recorded by engine — No value is inferred from surrounding data.

Your scenario artifact

Shared Merchant Decision Memo

A common merchant record with role-specific questions, conditions and a non-authorisation boundary.

TrustStack ORIONShared Merchant Decision Memo
DEMO · demo-universe-1

Synthetic merchant exercise — not a customer file or approval.

Current position

  • Existing bounded activity may continue
  • Requested expansion is a separate decision
  • Incomplete beneficiary evidence remains visible

Ownership

  • GATE provides identity/onboarding context
  • SENTINEL owns screening/policy disposition
  • The selected role owns the next action and review point

Does not authorise

  • No new beneficiary
  • No uncontrolled new corridor
  • No route outside provider and policy eligibility

Evidence required

  • Beneficiary verification
  • Provider eligibility
  • Policy validation
  • Required data-contract fields

What this shows

  • A fixed merchant fact set can support several role-specific views without changing the truth.
  • Identity/onboarding ownership and screening/policy ownership remain distinct.
  • Current permission, proposed scope, conditions and next ownership can coexist in one record.

What this does not prove

  • The fixture is not a live merchant, underwriting outcome or legal determination.
  • It does not replace a PSP's or regulated firm's accountability.
  • It does not establish that every listed integration or jurisdiction is currently deliverable.
Aster Decision Dossier

Aster Market

Each scenario adds a different synthetic artifact without changing the shared facts.

1 / 4Explored chapters
  1. 03:17
    Continuity Drill Brief03:17 — The Continuity Room
    Continue with the same synthetic facts
  2. 09:00
    Shared Merchant Decision MemoOne Merchant — Five Realities
    Current chapter
  3. 14:00
    Evidence Review ReportProof Lab — Try to Break the Decision
    Continue with the same synthetic facts
  4. Day 90
    90-Day Pilot BlueprintBuild Your Control Map
    Continue with the same synthetic facts

Explore all four chapters to close the night.

Continue the shared story

Follow Lumen Digital into the 03:17 provider incident

Continue
90-day pilot · targets agreed up front · scale, revise or stop at day 90 Run this discipline on your traffic See the platform behind this flow →