Repository navigation
docs: M5 demo video recording script, honesty lines pinned - #69
Conversation
Word-for-word timed script for the submission video, built only from runs verified 2026-10-28 on main: the six-beat replay (VERIFIED, 26 receipts), with the mock-rail disclosure spoken in the live-proof segment, the sandbox boundary stated at 2:20, and VERIFIED defined as internal chain integrity, not a PayPal signature, at 2:35. tests/test_submission_docs.py pins the script's existence, its exact on-screen command, and its honesty lines; the no-em-dash copy rule now covers it too. Submission checklist Demo video section points at the script; status stays not submitted (upload is the account holder's step). Suite: 413 passed, 3 skipped.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c12738fbf7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Then open the dashboard URL the replay printed and say: "The same | ||
| receipts, as an audit view. Every allowed, blocked, and revoked | ||
| decision is on the record." |
There was a problem hiding this comment.
After the prescribed command finishes, opening this URL fails with connection refused: demos/demo_six_beat.py calls dash.stop() immediately after printing the final ledger summary and then exits. I reproduced this with the exact command in the script; it prints VERIFIED with 26 receipts, but the dashboard is unavailable afterward. The new recording sequence therefore cannot show the promised audit view. Provide a supported way to keep the populated dashboard running, or revise the recording instructions to use a view that remains accessible.
Useful? React with 👍 / 👎.
PR #69 added one test after the 2026-10-27 evidence line was written, so the README claimed 412 passed / 415 collected while main at 3280b92 runs 413 passed, 3 skipped, 416 collected. Re-verified locally 2026-10-29 on the merged main tree (full suite plus demo.py, demo_admission, demo_estop, demo_sla_escrow and the six-beat replay, all chains VERIFIED).
PR #69 added one test after the 2026-10-27 evidence line was written, so the README claimed 412 passed / 415 collected while main at 3280b92 runs 413 passed, 3 skipped, 416 collected. Re-verified locally 2026-10-29 on the merged main tree (full suite plus demo.py, demo_admission, demo_estop, demo_sla_escrow and the six-beat replay, all chains VERIFIED). Co-authored-by: Marcus Richards <marsoju@gmail.com>
Word-for-word timed recording script for the submission video (M5), built only from runs verified 2026-10-28 on main: six-beat replay VERIFIED (26 receipts), demo.py VERIFIED (16), admission and e-stop demos VERIFIED.
Suite: 413 passed, 3 skipped. Ruff clean.