Skip to content

Core concepts

A project is the complete workspace for one explanation or closely related series. It contains creative decisions, source files, imported media, and output history.

The description states what the project is trying to communicate. It should change less often than scene implementation.

The passport stores foundational choices such as audience, format, production path, and communication identity. Changing these decisions can invalidate later work, so Matemium resolves them early.

The selected route through production:

  • Visual-first — produce a finished mute film for your own sound.
  • Voice synthesis — write narration, regulate timing, generate speech, and assemble the result.
  • Custom voice — begin with an approved external performance and build the visuals against verified audio.

The roadmap records phases, progress, blockers, and the current production decision. It is project state—not a generic checklist shown identically for every workflow.

A Python class extending CanvasScene. A project can contain more than one scene, although the desktop normally selects one scene for a render.

The primary authoring file. Humans and the agent edit the same visible Python source. Matemium does not use generated JSON as the normal authoring format.

CanvasBuilder is the recommended declarative authoring API. It collects content, layout intent, world objects, and timeline operations before compiling them into the internal scene representation.

A tape is a structured plane of content inside Matemium’s 3D world. In tape-scroll mode it behaves like an infinite document: content flows vertically, reveals lazily, and remains addressable after appearing.

Projects can use multiple tapes for comparisons, parallel explanations, notes, or alternative perspectives.

Anything positioned in Matemium’s 3D world, including solids and tape objects. A tape can be observed as a plane in 3D or entered in tape-scroll mode.

A local compilation of a scene through Matemium’s Manim-based engine. Rendering produces visual evidence that should be inspected rather than assumed correct.

The loop of rendering, inspecting, identifying a concrete defect, changing the project, and rendering again.

Generated videos, images, full-sheet exports, and related delivery artifacts. Output remains local unless you explicitly publish or move it.