Skip to main content
A HyperFrames project is an ordinary folder. An agent, Studio, and the renderer all work with the same files. You do not need every file in every project. A short title card may only have index.html; a larger launch video may include a storyboard, narration, several scenes, and many assets.

​
The files you will see most often

my-video
BRIEF.md
STORYBOARD.md
SCRIPT.md
index.html
hyperframes.json
compositions
intro.html
feature.html
outro.html

​
What Studio edits

Studio reads the project and writes supported changes back to its files. A canvas move, timeline trim, keyframe adjustment, or property edit is not stored in a separate proprietary Studio document. That means:
  • the next agent session can see your Studio edits;
  • validation and rendering use the same project;
  • Git can show what changed;
  • source editing and visual editing must not compete at the same moment.

​
Story files are checkpoints

The brief and storyboard are useful because they preserve intent. When a later edit drifts, compare it with the agreed message instead of judging every scene from scratch. For a tiny project, these files may be unnecessary. Use them when another person or agent needs to understand why the video was built a certain way.

​
Nested compositions

Larger videos split scenes into files under compositions/. The main index.html places those scenes on the timeline. In Studio, open a nested composition when you want to edit the scene itself. Return to the parent when you want to change where the complete scene appears. Read Compositions for the source format and Layers and groups for the visual workflow.