Repository navigation
Videoform: the plan and its tasks (VF1-VF13) - #207
Merged
Merged
Conversation
A videoform is the kind of video a person makes again and again, read once from five to ten of their finished videos (from the drive, or streamed from a URL with nothing downloaded) into embeddings and measures, then followed and checked on every cut without going back to the references. It's a kind of fingerprint, and flows into what raea has: its ranges into its profile (FP6e), its rules into a controller's rule fields (DR4, DR8), its structure into a script template, its references into brief.ts's shape. What ships runs on raea's own models; the domain vocabulary is written by the person's own AI. docs/videoform.md is the plan (what's built on, what a videoform keeps, the resolver, when it doesn't hold together, judging, the build order); docs/videoform.feature its rask tasks, with their plans. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
|
Thanks. The plan is thorough, and making a videoform a kind of fingerprint, rather than a parallel system, fits how the rest is built. It's docs only and
|
Owner
|
Decided: merging this as the plan for videoforms. It's docs only,
The build order is the one the plan sets: VF4 with VF12 first, from the local drive, as the gate. Resolving platform pages (VF1b, yt-dlp) is built only once that gate passes on the person's own sets. Thanks. |
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
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.
A plan for videoforms: the kind of video a person makes again and again (a listing walkthrough, a recipe short, a podcast clip), read once from five to ten of their finished videos, then followed and checked on every cut, fast. Docs only:
docs/videoform.md(the plan) anddocs/videoform.feature(its rask tasks, with their file plans;rask checkpasses).The decisions in it
fingerprint.tsgains an optionalvideoformsection (context, references, vocabulary, template, rules), so it's found, inherited, taught and shared as any fingerprint (FP14).raea check PROJECTalready runs (DR4, DR8);NAME.script.tstemplate;referencesshape.Where the code goes (from the task plans)
New crates
raea-io-resolve,raea-app-videoformandraea-sys-videoform. The fingerprint crates are each within 150 lines of their limit, so they grow only by a field (+20), a profile measure map (+30) and a hook inraea check(+15).Before building
The first proof that matters is VF4 with VF12: on at least five of the person's sets, the numbers alone must tell videoforms apart.
🤖 Generated with Claude Code