[P1] Rehearse and verify the complete Demo Day presentation and failover path

[TFT444]

Objective

Prove that the complete Demo Day presentation is reproducible, truthful, understandable, and resilient to network or hosted-service failure.

Dependencies

Run after #49, #41, #42, #43, #44, #45, and #50 reach the intended release-candidate state. Keep this issue open until the final presentation candidate passes.

Required modes

• Primary local web application using authoritative runtime evidence
• Optional real Solana Devnet transaction and RPC proof
• Network-independent deterministic simulation fallback
• Same-commit recorded fallback video and static critical states

Rehearsal sequence

1. State the compromised-agent payment risk.
2. Run a legitimate synthetic baseline.
3. Trigger the deterministic attack.
4. Show unsafe signing versus SolGuard pre-signing prevention.
5. Prove authorization absence, signer non-invocation, no transaction, and unchanged balance.
6. Show safe recovery.
7. Show one separately labelled real Devnet proof if available.
8. Close with the buyer and design-partner ask.

Failure drills

• Conference Wi-Fi unavailable
• Hosted dashboard unavailable
• x402 facilitator unavailable
• Solana RPC slow or unavailable
• Devnet wallet lacks test USDC
• Browser refresh or dashboard restart
• External display uses reduced resolution
• Live Devnet transaction remains pending

Acceptance criteria

• Core presentation completes in 90 seconds; extended version remains under two minutes.
• Three consecutive clean-process local runs produce the expected evidence.
• A fresh clone follows the documented setup and passes every quality gate.
• Local dashboard works with networking disabled.
• Every failure drill produces an honest fallback rather than fabricated success.
• Real Devnet evidence includes RPC confirmation and an Explorer link.
• Recorded fallback, screenshots, manifest, QR code and source commit all match the release candidate.
• No secret or personal information appears on screen, in terminal history, logs, video or evidence.
• At least one reviewer unfamiliar with the project can explain the value proposition after the rehearsal.
• Presenter Q&A covers simulation boundaries, key isolation, replay protection, residual risk and production gaps.

Deliverables

• Final 90-second script
• Setup and reset checklist
• Offline/failure playbook
• Same-commit fallback recording
• Reviewer QR/link
• Signed release tag and evidence manifest

Keywords

rehearsal offline-fallback demo-reliability presentation submission-gate