| name | broll-master-build |
| description | Build three HyperFrames representative samples and shared creative capabilities as Lead, or own the complete design-build-view-revise loop for one contiguous 5–8-shot chapter. |
HyperFrames Lead / Chapter Builder
HyperFrames is the v1.0.1 production default. Own only the assignment-selected
role and source tree. Never change SRT timing, Recipe truth, another chapter,
runtime selection, or Parent-generated media contracts.
Complete creative context
Read the complete original SRT and original design directly; a summary cannot
replace either. Use the assignment-selected role prompt, this assignment, its
Recipes, chapter/seam context, shared asset/font index, Lead samples and
capability index, exact HyperFrames runtime, and at most two selected
references. Do not reopen Parent/other stage Skills, schemas, validators,
generic craft references, full catalogs, or command source.
truth is immutable. creativeProposal is revisable: change its metaphor,
objects, composition, motion, material route, or key states when a better
answer preserves the audience outcome and required readable result. Record one
concise reason, not a new approval workflow.
Do not create inspection source, DOM trace markers, motion windows, dense
diagnostics, capture/trace/lint/screenshot/frame-scan/hash/probe/decode/
manifest/contract/receipt/proof tools, or passing proof artifacts. Parent owns
deterministic rendering and media evidence.
Expose every assigned HyperFrames render target as one regular source file at
compositions/<target.id>.html under the assignment's sourceRoot. The file
name is the binding; a root-level <target.id>.html is not a composition.
Lead mode
Read the complete original inputs, compact motion map, exactly three
representative Recipes, and shared assets/fonts. Build three final, directly
renderable samples with clearly different silhouettes, compositions, and main
actions:
- native graphic and type;
- real or generated material fusion;
- information-dense interface, process, or data organization.
Implement every signature motion named by the design in a real sample or
runnable primitive. Provide reusable crop, mask, depth, background fusion,
source binding, preparation, main action, overlap, settle, and readable-hold
capabilities. The capability index stays under one page and explains which
content relationship each capability serves. Shared source may contain tokens,
visual/motion primitives, and base components, never a swap-the-copy whole-shot
template.
Run only the exact standard command, open all three six-frame sheets and short
previews, repair low-level defects, then record accepted or revised. A
revised conclusion names the actual source change. These samples become final
source for their shots; Chapter Builders do not rebuild them.
Chapter Builder mode
Own one contiguous chapter, normally 5–8 shots. Control its composition
variation, material choices, pacing, and neighboring handoffs. Use Lead
capabilities without copying Lead layouts. Never let three consecutive shots
share the same layout skeleton, entry, and rhythm.
Choose native, provided, search, generate, or mixed separately for
each shot. The shared freeze does not close shot-specific search/generation
unless the packet records a real user, capability, authorization, or cost
restriction. Add selected material to the provenance index and fuse it into
crop, mask, path, palette, depth, annotation, or state.
Expose one seekable direct runtime entry per assigned shotId. Build the
maximum visible result first, then staging, necessary anticipation, primary
causal action, weaker follow-through, settle, and readable hold. Apply only the
Recipe's 2–4 craftIntent principles; do not score or mechanically force all
twelve. Keep stable holds valid and motion finite.
Run only the exact standard command. Open every shot's six-frame sheet and the
chapter preview. Fix coverage, overlap, accumulated states, unsupported lines,
empty containers, unreadable results, unfinished action, design-energy
mismatch, and repeated chapter structure. Rerender only affected shots. Handoff
requires one concise accepted or revised conclusion; a revision names what
actually changed.
Complete only when every assigned shot has editable direct source, Parent's
technical command passes, the real sheets/chapter preview were viewed, truth is
preserved, required results are readable, low-level defects are repaired, and
material provenance closes. Technical success alone is not aesthetic approval.
