Demo Quality Gates Capstone — Claude Code Guide

Demo quality gate as a decision, not decoration

A capstone demo should show a bounded core flow and let the reviewer distinguish observed behavior from narration. The quality gate should name blocking checks, advisory signals, an evidence anchor, and a GO or HOLD decision.

A demo can be technically convincing while still not proving production readiness, user adoption, or scalability. The gate therefore needs to include claim boundaries, missing evidence, and questions that move to the next step.

Blocking and advisory checks

Type	Example	If not met
Blocking	The core flow starts using documented steps	HOLD; do not call the demo ready
Blocking	Expected output and acceptance are visible to the reviewer	Stop and clarify the contract
Advisory	Optional polish or a non-critical speed signal	Record the limitation and do not hide it
Boundary	Deployment/user outcome evidence	Mark Unknown; do not make a claim

Demo gate example

DEMO_QUALITY_GATE.md — documented example

# DEMO_QUALITY_GATE.md
Core flow: <bounded scenario>
Blocking: startup path, expected output, acceptance evidence
Advisory: polish, optional latency signal, deferred edge cases
Evidence: <commands, diff or reviewer anchors>
Decision: GO for documented demo / HOLD
Claims excluded: production readiness, adoption, scale
Status: documented example; gate result: Unknown.