Packages
AutoMovie is published as these npm packages. A production created by automovie create depends on every one except @automovie/template, which the CLI installs, through the catalogs in its pnpm-workspace.yaml.
| Package | Owns |
|---|---|
automovie | The CLI: creating a production, and the hosts that capture, inspect, render and review it |
@automovie/template | The scaffold every production starts from: instructions, contracts and thin configuration |
@automovie/interface | The common and domain contracts, including the authoring AST, with no runtime dependency |
@automovie/engine | Deterministic validation and computation of what each frame contains, and the universal motion primitives |
@automovie/human | A person’s skeleton and contact profile, generated by code from typed parameters |
@automovie/motions | The human action vocabulary, its composition grammar, layers, refusals and verdicts |
@automovie/archetypes | Coarse seeded models of what people hold, use, sit on, ride and fight with, and their affordances |
@automovie/render | Scene building, the passes, the polygon man, the inspection core, the capture plan and record, frame schedules and encoding plans |
@automovie/viewer | The interactive inspector page as a React component, and an imperative canvas mount |
@automovie/evidence | The evidence configuration of a production: engineering defaults and the narrative, research and development checks |
@automovie/ingest | Deterministic import of glTF, GLB, VRM, WAVE and PPM inputs |
@automovie/recovery | Curves recovered from a reference mesh, and geometry rebuilt from them |
Boundaries
A few rules decide where code belongs:
@automovie/interfaceholds the pure contracts the other packages expose, so importing a type validates nothing; the package that admits a record checks it.@automovie/motionsowns every action law, and@automovie/enginekeeps only universal motion primitives.@automovie/renderand@automovie/viewerare the packages that importthreein their public surface.@automovie/renderlaunches nothing; theautomoviecommand supplies the browser, the files and FFmpeg as hosts.- No product package depends on
@automovie/archetypes; a production imports it to stage its objects.
Finished content stays in productions. Example productions live in automovie-examples .
Last updated on