Skip to Content
ReferencePackages

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.

PackageOwns
automovieThe CLI: creating a production, and the hosts that capture, inspect, render and review it
@automovie/templateThe scaffold every production starts from: instructions, contracts and thin configuration
@automovie/interfaceThe common and domain contracts, including the authoring AST, with no runtime dependency
@automovie/engineDeterministic validation and computation of what each frame contains, and the universal motion primitives
@automovie/humanA person’s skeleton and contact profile, generated by code from typed parameters
@automovie/motionsThe human action vocabulary, its composition grammar, layers, refusals and verdicts
@automovie/archetypesCoarse seeded models of what people hold, use, sit on, ride and fight with, and their affordances
@automovie/renderScene building, the passes, the polygon man, the inspection core, the capture plan and record, frame schedules and encoding plans
@automovie/viewerThe interactive inspector page as a React component, and an imperative canvas mount
@automovie/evidenceThe evidence configuration of a production: engineering defaults and the narrative, research and development checks
@automovie/ingestDeterministic import of glTF, GLB, VRM, WAVE and PPM inputs
@automovie/recoveryCurves recovered from a reference mesh, and geometry rebuilt from them

Boundaries

A few rules decide where code belongs:

  • @automovie/interface holds the pure contracts the other packages expose, so importing a type validates nothing; the package that admits a record checks it.
  • @automovie/motions owns every action law, and @automovie/engine keeps only universal motion primitives.
  • @automovie/render and @automovie/viewer are the packages that import three in their public surface.
  • @automovie/render launches nothing; the automovie command 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