Synthetic scenario · illustrative product experience
Synthetic evidence challenge

Proof Lab — Try to Break the Decision

A partner asks why Lumen Digital traffic moved to PSP-B, who approved it, and what they may inspect. Test a sandbox copy of DR-DEMO-0317. The original record never changes.

2–4 minutesMLRO · Audit · CISO · PSP diligence
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 · FIXTURE
Control-test copyDR-DEMO-0317 → TEST-DEMO-0317Original Decision Record unchanged · test fixture TEST-DEMO-0317
The source Decision Record remains unchanged.DR-DEMO-0317
02 · GOVERN

Review purpose

Partner diligence for the synthetic continuity decision

03 · DECIDE
Evidence state vocabulary
PASS

Present and suitable for the stated test purpose.

EXCEPTION

A control or integrity condition requires remediation.

NOT RECORDED

The field is absent; the interface does not infer it.

NOT APPLICABLE

The field is not required for this decision mode.

04 · CHALLENGE
Run evidence challenges

Toggle any challenge. Results distinguish an exception from a missing or inapplicable field.

Evidence Run evidence challenges DR-DEMO-0317 → TEST-DEMO-0317

With no challenge selected, the synthetic fixture passes the six checks for its stated internal review purpose.

Your mission

Test whether the evidence supports the stated purpose without strengthening it by inference.

The baseline sandbox copy is ready for six purpose-bounded control tests.

Flow

The review follows provenance, rationale, duties, integrity and grant scope to the final disposition.

Guardrail

The original DR-DEMO-0317 remains unchanged throughout the challenge.

Ownership

partner_reviewer_demo runs the tests; remediation stays with the relevant control owner.

Evidence

EVP-DEMO-0317 is examined only for the stated synthetic partner-diligence purpose.

Why this matters

Evidence is useful when both its support and its limits can be inspected.

OUTCOME

Confidence stops where the recorded evidence stops

The report changes with the selected challenges and never edits the source fixture.

DEMO · READY TO REVIEW
0
PASS · BASELINE FIXTURE

With no challenge selected, the synthetic fixture passes the six checks for its stated internal review purpose.

Inspect Decision Record DR · DEMO
decision_recordFIXTURE
record_id
DR-DEMO-0317
test_copy
TEST-DEMO-0317
evidence_pack
EVP-DEMO-0317
grant
GRANT-DEMO-PARTNER-48H
policy
payment-continuity@demo-3.2
decision_mode
rules_only
reviewer
partner_reviewer_demo
original
UNCHANGED

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

Your scenario artifact

Evidence Review Report

A purpose-bounded report of provenance, completeness, segregation, integrity and disclosure tests.

TrustStack ORIONEvidence Review Report
DEMO · demo-universe-1

Synthetic control test — not an assurance opinion.

Review scope

  • DR-DEMO-0317 sandbox copy
  • Partner-diligence purpose
  • EVP-DEMO-0317 and scoped 48-hour grant

Control result

  • Selected tests are listed as PASS, EXCEPTION, NOT RECORDED or NOT APPLICABLE
  • No missing rationale or model is fabricated

Reliance boundary

  • Suitable only for the stated synthetic purpose when all required tests pass
  • Exceptions require named remediation before external reliance

Deliberate exclusions

  • No live customer data
  • No broad access grant
  • No claim of universal event or storage coverage

What this shows

  • Missing evidence can be made explicit instead of being filled with plausible-sounding text.
  • Segregation, manifest integrity and grant scope can fail visibly and independently.
  • Rules-only decisions can be represented honestly without inventing a model.

What this does not prove

  • This browser exercise is not an audit, assurance report or certification.
  • It does not establish uniform backend enforcement across every ORION workflow.
  • It does not demonstrate write-once storage or complete event-producer coverage.
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
    Continue with the same synthetic facts
  3. 14:00
    Evidence Review ReportProof Lab — Try to Break the Decision
    Current chapter
  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

Turn the control pattern into a bounded 90-day pilot

Continue
90-day pilot · targets agreed up front · scale, revise or stop at day 90 Run this discipline on your traffic Read how evidence works in the manual →