Launch Demo Kit

One-page flow for launch walkthrough

Use this page to run demo scenarios in fixed order and keep runbook/checklist consistency before soft launch.

Recommended order for a stable 7-minute walkthrough.

1. Start with HOLD to establish hard-stop semantics.

2. Move to ABSTAIN to show intended-use boundary enforcement.

3. Finish with CAUTION, then open Drift and Change Proposal for governed response.

4. Close with SMART live path (`/smart/launch` to callback to patient).

Canonical source of sequence: `docs/DEMO_RUNBOOK.md`.

ENC-S-HOLD-001

Stop operational usage when data integrity is broken (unit mismatch).

Control Tower -> Reset demo -> Show HOLD -> Case Detail -> Audit Vault

ENC-D-ABSTAIN-001

Suppress model output when context is outside intended-use policy boundary.

Control Tower -> Reset demo -> Show ABSTAIN -> Policy Boundary -> Audit Vault

ENC-D-CAUTION-001

Continue with caution while drift pressure and burden shift are investigated.

Control Tower -> Reset demo -> Show CAUTION -> Drift -> Change Proposal

Open `/launch` and validate CTA routes (`/launch/pilot-pack`, `/launch/demo-kit`, `/`).
Run `make demo-reset` and confirm scenario shortcuts open deterministic cases.
Verify each scenario reaches matching evidence blocks (gate reason, policy outcome, lineage).
Open `Drift` and `Change Proposal` from CAUTION path and confirm context import is visible.
Confirm `docs/DEMO_RUNBOOK.md` and `docs/LAUNCH_CHECKLIST.md` match current UI labels.

If case did not open: click `Reapply shortcut`.
If still missing: click `Reset demo`, then re-run the same scenario shortcut.
If drift/change pages are empty: open from case drawer deep-link buttons to restore context.
If SMART launch token/scope fails: use `Retry launch` or `Retry exchange` and continue with sandbox path if needed.

docs/DEMO_RUNBOOK.md

docs/LAUNCH_CHECKLIST.md

docs/PILOT_PACKET.md

docs/EPIC_INTEGRATION_OVERVIEW.md

docs/SECURITY_FAQ.md