Demo Fallback Assets — autonomy demo openclaw

Pre-prepared fallback materials for use when the live demo cannot run. Apply in the order listed. Pivot in ≤ 15 seconds.

Asset	Purpose	When to use
recorded-output.txt	Captured terminal output — show as-is or alongside a screen recording	Live demo fails; recording available
annotated-output.md	Same output with inline annotations explaining each line	No recording; walk prospect through output
pivot-notes.md	Exact presenter script and fallback sequence	Keep open during every live demo meeting

Keeping assets current

Re-capture recorded-output.txt whenever the demo output format changes. Both the pre-flight gate and the capture must run against the same binary — --dev resolves to ./bin/autonomy from the source tree, so the pre-flight has to use that exact path too. Otherwise a green check on the installed autonomy (on PATH) can sit on top of a broken ./bin/autonomy capture.

# Pre-flight on the source-tree binary, then capture with --dev (same binary).
# `&&` ensures the capture is only attempted if the pre-flight passes.
./bin/autonomy demo validate \
  && bash scripts/capture-demo-output.sh --dev --normalize

The capture script also runs autonomy demo validate against its own $BINARY immediately after writing the recording (post-flight) and exits non-zero with a warning if the gate fails — so even if the pre-flight is ever skipped, the script’s post-flight is the authoritative gate. Both flights deliberately point at the same binary; do not split them.

Commit the updated recorded-output.txt only after the chained command above succeeds with no warnings. The --normalize flag replaces volatile values (audit UUIDs and the capture timestamp) with stable placeholders, so re-captures are diff-silent when the demo output itself is unchanged.

The internal Demo Reliability Checklist (docs/internal/demo-reliability-checklist.md, engineering-only — not linked here because the internal tree is excluded from the public build) is the canonical pre-meeting verification. Re-capture is part of keeping the fallback assets current, not a substitute for the checklist.

Labeling rule

All recorded material must be presented as recorded. Never imply it is live. See pivot-notes.md for the exact framing language.