Interface sequences · Rendered draft
Task-card explanation · r02 guidance · NOT PACKAGED
Study the source, inspect the editable build, then adapt the treatment to your own content.
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
A runnable draft is not a fidelity approval.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- NOT PACKAGED: existing-code numerical guidance, not a new treatment or completion. The r01 source-first critic viewed 24 scaled static triptych frames on four sheets; the retained ledger has 119 contact frames. Neither is moving-source review. All 294 computed model frames are numerical states, not 294 inspected raster states. No fresh source-master hash, moving-source quality vote, clean-install or minimal-subset preparation. No fresh Remotion render/replay, native Resolve project/import/render or production approval. Both historical manifest-wrapper hash discrepancies remain; matching selected bindings are not whole-wrapper identity. Referenced per-recipe ASSET-NOTES.json and FONT-LICENSE.txt remain absent; shared ASSET_RIGHTS and OFL exist. SVG filters/gradients, font metrics, hierarchy, perspective, clipping, shadows, alpha and color matching remain unverified. The r02 independent recheck covers configuration/privacy and unchanged numerical output only; r01 conclusions are unchanged. Playable links reuse the accepted public clips without copying media or creating player clocks. The seven r02 files retain their historical phase notes unchanged; the integration record documents only the later narrow technical recheck.
- The existing package is retained unchanged. Local checks verify its bytes, archive, media, and route; no new fidelity approval is asserted.