Synthetic scenario · illustrative product experience
Synthetic continuity exercise

03:17 — The Continuity Room

PSP-A stops accepting new authorisation requests. 320 synthetic attempts are waiting. Your job is not to find a magic route; it is to make a bounded decision without hiding the traffic that cannot safely move.

2–4 minutesCOO · Head of Payments · Operations
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 · SIGNAL
03:17:08ZPSP-A · UNAVAILABLE
Flow Route eligible traffic to PSP-B

Continuity improves for the eligible segment; missing context remains a visible hold, not an override.

Fixed incident facts

Fixed incident facts

Primary route
PSP-A is unavailable in this DEMO fixture.
Alternative
PSP-B has narrower corridor, risk and context requirements.
Required context
48 attempts lack a field required by payment-continuity@demo-3.2.
Decision object
DR-DEMO-0317 records the proposal, review and consequences.
02 · GOVERN
Set the mandatory-control boundary

Forty-eight attempts lack context required by the DEMO policy; no operating posture may silently move them into execution.

03 · DECIDE
Choose the operating posture inside that boundary

The boundary stays fixed while each posture makes a different commercial and control trade-off.

04 · CHALLENGE
3 · Record a distinct checker disposition

The checker sees the proposed scope and the unresolved 48 attempts. Self-approval is not permitted in this DEMO workflow.

Your mission

Decide what may continue without concealing what cannot.

The provider signal is captured. No alternate execution is assumed until the boundary and posture are explicit.

Flow

320 synthetic attempts are visible and awaiting a bounded disposition.

Guardrail

PSP-B remains conditional; 48 attempts lack required context.

Ownership

Payments owns the proposed posture; a distinct checker must review it.

Evidence

DR-DEMO-0317 is the synthetic decision object; no live routing event is represented.

Why this matters

Continuity begins with a visible decision boundary, not an invisible override.

OUTCOME

A continuity decision with visible limits

The chosen posture is appended to the synthetic record. Alternatives, holds and the checker reason remain visible.

DEMO · READY TO REVIEW
PostureRoute eligible traffic to PSP-B
BoundaryStep up where supported
CheckerConfirm for a bounded period
Inspect Decision Record DR · DEMO
decision_recordFIXTURE
record_id
DR-DEMO-0317
merchant
MER-DEMO-204 · Lumen Digital
signal
PSP-A UNAVAILABLE · 03:17:08Z
policy
payment-continuity@demo-3.2
maker
payments_owner_demo
checker
compliance_checker_demo
case
CASE-DEMO-0317
correlation_id
corr_demo_0317

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

Your scenario artifact

Continuity Drill Brief

A compact reconstruction of the incident, posture, exclusions and next ownership.

TrustStack ORIONContinuity Drill Brief
DEMO · demo-universe-1

Synthetic continuity exercise — not a production incident report.

Incident scope

  • PSP-A unavailable at 03:17:08Z
  • 320 deterministic DEMO attempts
  • Lumen Digital · MER-DEMO-204

Decision boundary

  • PSP-B only where eligibility and required context are satisfied
  • No missing-context override
  • Temporary posture requires an expiry and distinct review

Next actions

  • Payments owns provider recovery
  • Compliance owns the open exception
  • Engineering preserves the correlation and path trail

Pilot hypothesis

  • Test whether a bounded continuity policy can reduce uncontrolled downtime without concealing held traffic.

What this shows

  • How route state, policy context, human review and evidence can meet in one reconstructable decision.
  • Why rejected and unresolved traffic is part of the outcome, not a footnote.
  • How a temporary action can carry an owner, scope and expiry.

What this does not prove

  • No live provider connection, automatic failover or production routing is demonstrated.
  • The fictional counts are not forecasts or customer results.
  • The scenario does not establish uptime, latency or contractual service levels.
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
    Current chapter
  2. 09:00
    Shared Merchant Decision MemoOne Merchant — Five Realities
    Continue with the same synthetic facts
  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

Now let a skeptical partner challenge DR-DEMO-0317

Continue
90-day pilot · targets agreed up front · scale, revise or stop at day 90 Run this discipline on your traffic See baseline vs TrustStack in numbers →