Demo And Deployment Readiness — Claude Code Guide

Demo readiness is not deployment

Demo readiness means that a reviewer has a reproducible startup path, required inputs, a fallback, and known limitations for a bounded demonstration. This is local or educational scenario readiness, not permission to publish, release, or deploy to production.

Separate environment assumptions, data fixtures, operational permissions, and the deployment decision. If any prerequisite is unconfirmed, record Unknown or HOLD instead of replacing the fact with an optimistic status.

Readiness checklist

1. Record the startup command or manual entry point without credentials.
2. Describe fixtures, inputs, and the expected observable output.
3. Check the fallback for an unavailable or unstable integration.
4. Mark which checks were actually run and which remain Unknown.
5. Pass the deployment decision separately to the authorized owner; do not include deployment in the demo script.

Readiness record

# DEMO_READINESS.md
Scenario: <bounded capstone flow>
Start: <command or manual entry point>
Inputs: <safe fixtures; no secrets>
Expected signal: <observable output>
Fallback: <manual or static path if dependency is unavailable>
Blocking unknowns: <environment, data or permission gaps>
Deployment boundary: no publish/deploy claim; decision owner: <role>
Status: documented example; readiness result: Unknown.