Skip to content

[docs] - Add the 60-second demo and link it from README - #1732

Merged
cgfixit merged 1 commit into
mainfrom
codex/docs-demo-video
Oct 20, 2026
Merged

cgfixit merged 1 commit into
mainfrom
codex/docs-demo-video

Conversation

@cgfixit

@cgfixit cgfixit commented Oct 20, 2026

Copy link
Copy Markdown
Owner

Proposed changes

Make the completed 60-second CyClaw demo available from the repository README. Add the unchanged MP4 under docs/screenshots/demo/ and a descriptive relative link near the top of README.md.

README.md → docs/screenshots/demo/cyclaw-60-second-demo.mp4

The silent demo shows local status, a document question, its grounded answer, supporting sources, and protected operator controls. It uses real local retrieval/inference with synthetic documents and leaves quiet holds for later narration.

Invariant / Governance Impact: Documentation and media only. No application, configuration, workflow, hook, or invariant changes.

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Security (auth, privacy, injection, egress, redaction, or secrets)
  • Invariant / Governance refinement (use this for changes that strengthen or evolve the 6 invariants, I6 isolation, or harness phases)
  • Dependencies (added, removed, or bumped)
  • CI / infrastructure (workflows, hooks, templates, or checkers)
  • Refactor or tests (behavior-preserving, no new capability)
  • Documentation update
  • Other (none of the boxes above fit)

Benefits / why

Visitors can watch the working local-document flow directly from the README. The description identifies the silent format and synthetic data so the footage is not mistaken for a production corpus or a cloud-provider demonstration.

Risks to monitor

Door: two-way. Blast radius: documentation. Removing the link and media reverses the change; the 1,778,140-byte video remains in Git history. The recording can become dated as the UI evolves. Browser handling of a repository MP4 may open a preview or download it.

Checklist

  • I have read docs/THREAT_MODEL.md, INVARIANTS.md and SECURITY.md (and any relevant Phase docs)
  • This change preserves all 6 security invariants and I6 module isolation (explicit evidence or invariant matrix included for core changes)
  • Full sandbox validation has been run (GROK_API_KEY=dummy pytest tests/ -q --tb=short, and bash .claude/skills/CyClaw-Sandbox/verify.sh for core RAG/agentic paths) and passes with no regressions
  • No new external network dependencies or mandatory online LLM assumptions were introduced without explicit justification + offline fallback path
  • For any agentic/fsconnect change: two-phase audit, quota enforcement, governed delete/trash, and write guards have been verified
  • Relevant architecture docs or threat model notes have been updated if core behavior or topology changed
  • Commit messages follow the title prefix convention above
  • For large or complex changes: before/after invariant matrix + sandbox evidence is included in "Further comments" or linked

Unchecked runtime/security-path rows are not applicable to this two-file documentation/media change. Full local suites and Actionlint were not rerun: no executable code or workflows changed.

Further comments

Evidence — before: the completed 60-second export was a local artifact with no README link. After: it is tracked at the requested repository path and the relative README link resolves.

  • Base: b0683515d5791eb5caaa958013d7780ccfb8027e; candidate: 069a8c175165e0693fb4433fad873cc2cd2163ba.
  • Maintained doc-sync checker: 0 drift items; README paths and links pass. git diff --check passes.
  • Copied video is byte-for-byte identical to the verified export: SHA-256 f3424b34d093484d51d3bc33316587116c56e163739769db6fbb4129002dedad.
  • ffprobe: 60.000000 seconds, 1920×1080, H.264, 30 fps, 1,800 frames, no audio stream. Fresh full-file FFmpeg decode passes.
  • The identical export previously completed real browser playback to 60 seconds with ended: true and no playback error. Its contents were visually reviewed; footage is a paced capture edit of synthetic demo documents.
  • No private corpus, credentials, runtime directories, or raw capture frames are included. The earlier screenshot/gallery and existing 15-second advertisement remain intact.

Suggested merge order of open PRs

Trial merges verified with git merge --no-commit --no-ff and abort against main b0683515d5791eb5caaa958013d7780ccfb8027e on 2026-10-20 ET. The combined demo + #1731 trial also merged cleanly; its README retains both changes. There is no ordering dependency.

#1731 · Blocked (draft)
Impact: Documentation refresh; shared README, distinct hunks; combined trial clean.
Action: Complete hosted checks and human review; recheck current heads before merge.

This PR · Blocked (draft)
Impact: Adds the demo and README link only; combined trial clean.
Action: Human review and merge decision; may merge independently of #1731.

ELI5

The demo was saved locally but visitors could not find it in the repository. This adds that exact silent, one-minute video to docs/screenshots/demo/ and links it near the top of the README. No application behavior changes. The file was decoded, its duration and format checked, and the README link passed the repository checker. The same video also completed browser playback. Full application suites were not run for this media-only addition; future UI changes may make the recording look dated.

Last updated: 2026-10-20 10:29 ET

@cgfixit
cgfixit marked this pull request as ready for review October 20, 2026 14:33
@cgfixit
cgfixit enabled auto-merge October 20, 2026 14:33
@cgfixit
cgfixit merged commit c8ad99a into main Oct 20, 2026
59 of 60 checks passed
@cgfixit
cgfixit deleted the codex/docs-demo-video branch October 20, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants