docs: complete guided run beat gates

This commit is contained in:
lda
2026-07-09 09:24:06 +07:00 Verified
parent 447787226c
commit 8de2885cfd
2 changed files with 8 additions and 8 deletions
+8 -8
View File
@@ -125,9 +125,10 @@ Implementation order:
live/replay execution all share `useDemoTimeline`; AI SDK remains a later live/replay execution all share `useDemoTimeline`; AI SDK remains a later
driver for the same seam. Implementation: driver for the same seam. Implementation:
[`presentation chat timeline bridge`](historical/superpowers/plans/2026-07-09-presentation-chat-timeline-bridge.md). [`presentation chat timeline bridge`](historical/superpowers/plans/2026-07-09-presentation-chat-timeline-bridge.md).
17. Active: implement Guided Run Beat Gates so Scene 10 approval buttons and 17. Completed: guided run beat gates connect Scene 10 schema approval, chat
chat approval requests drive the same deterministic demo timeline. Plan: approval, graph focus, and evidence transitions into one deterministic
[`guided run beat gates`](superpowers/plans/2026-07-09-guided-run-beat-gates.md). presenter sequence. Implementation:
[`guided run beat gates`](historical/superpowers/plans/2026-07-09-guided-run-beat-gates.md).
18. Future: presenter companion, Scene 10 product graph, final scene visuals, 18. Future: presenter companion, Scene 10 product graph, final scene visuals,
evidence assets, and rehearsal timing. evidence assets, and rehearsal timing.
19. Add a static slide/appendix shell only after presentation mode is clear. 19. Add a static slide/appendix shell only after presentation mode is clear.
@@ -199,11 +200,10 @@ Presentation wishlist / defense readiness:
The current `{ "type": "object" }` proof is enough for architecture evidence, The current `{ "type": "object" }` proof is enough for architecture evidence,
but the product demo needs a real schema-derived approval form with submitted but the product demo needs a real schema-derived approval form with submitted
and cancelled outcomes. and cancelled outcomes.
- Active: Guided run beat gates make the prepared agent/demo sequence explicitly - Completed: guided run beat gates connect Scene 10 schema approval, chat
wait for approval decisions and evidence reveals instead of relying on loose approval, graph focus, and evidence transitions into one deterministic
timing. This connects the chat run, schema approval form, graph focus, and presenter sequence. Implementation:
evidence inspector into one deterministic presenter sequence. Plan: [`guided run beat gates`](historical/superpowers/plans/2026-07-09-guided-run-beat-gates.md).
[`guided run beat gates`](superpowers/plans/2026-07-09-guided-run-beat-gates.md).
- Evidence assets and rehearsal timing: prepare fallback screenshots/recordings, - Evidence assets and rehearsal timing: prepare fallback screenshots/recordings,
expected run states, and a timed walkthrough checklist for a 15-minute defense. expected run states, and a timed walkthrough checklist for a 15-minute defense.
- Presenter companion feasibility: decide whether phone/laptop control is local - Presenter companion feasibility: decide whether phone/laptop control is local