Repository navigation
feat(demo): further demo edits, readme video, npm package guard - #8
Merged
Merged
Conversation
- README: a poster (docs/assets/demo-poster.jpg) linking to the demo MP4 on the demo-video GitHub release. - demo/video: npm run publish-video renders, uploads the video to that release (created if missing, never marked latest), and refreshes the poster from a new Poster still. - publish.yml: only v* releases publish to npm, so the video release doesn't trigger a publish run. - CI: fail if the npm package ships anything beyond dist/, src/, LICENSE, package.json or README.md.
ask and GET /examples accept an optional scope (default "lamps"). walkthrough.mjs passes a run-unique one by default, so earlier rehearsals' runs can't outrank this run's michelle in matthew's top 3.
- repo clip: clone a real agent's Artifacts repo with a short-lived read token (created off camera) and read its log: Codemode-Status and Codemode-Examples trailers, then run.js. - scale clip: the real swarm against the deployed example. 1000/1000 agents with a commit, 0 errors, 27.3s, 36.7 commits/s, push p50 4.1s. - public/clips/index.json now maps each recorded scene to its clip length, so scenes stretch to fit the recording instead of cutting it off. - Shared VHS settings in terminal/theme.tape; scripts/artifacts-token.mjs for off-camera read tokens. Runtime 6:00.
…ording - walkthrough scene: DABstep task 2557 (hard), same agent and prompt. Without memory: 10 programs, ran out of steps, wrong. With memory: started from 3 related runs, right in 2 programs, 8k vs 279k tokens. - provenance scene: a recording that clones task 2557's Artifacts repo, reads the Codemode-Examples trailer, then clones task 2556 and shows the cited commit's code. - Replaces the lava lamp michelle → matthew walkthrough. The live runs didn't show learning, because that question is too easy for the model to need memory. Runtime 6:46.
… scene The 1,000-agent recording didn't add to the story. The measured result (1,000 commits in 27s, 0 errors) is now a line of narration and an on-screen stat in the Phase 1 code memory scene. Runtime 6:17.
The voiceover was MP3 at 48 kbps, with audible artifacts. It's now 16-bit 24 kHz WAV, in the arcas voice (picked from a 7-voice comparison). Runtime 5:41.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft, for continuing demo work before the Oct 14 submission.
So far
docs/assets/demo-poster.jpg, rendered from a newPosterstill) linking tocodemode-git-demo.mp4on ademo-videoGitHub release. GitHub plays videos inline only when they're uploaded through its web editor, so a poster that links to the release asset is the CLI-friendly option. It also keeps the 26 MB video out of git history.npm run publish-video(indemo/video): renders the video, uploads it to thedemo-videorelease (creating it if needed, never marked latest), and refreshes the poster.publish.yml: onlyv*releases publish to npm, so the video release doesn't trigger a failing publish run.dist/,src/,LICENSE,package.json(and a README). Today it's 32 files, 25 KB. No demo video, voiceover, benchmark data or examples were ever included (the package'sfileslist already scoped it); this keeps it that way.Before merging
npm run publish-videoonce the final cut is ready. Until then the README poster links to a release asset that doesn't exist yet.