Authoring model

Intent first

High-level authoring is where a person, AI agent, MCP tool, template, or future editor can express rich intent:

{
  "kind": "hero-intro",
  "headline": "A calm beginning",
  "motion": "fade-up"
}

This is illustrative high-level input. The fields are not Atomic Protocol V2 fields. Compiler A expands and normalizes this intent before runtime rendering.

Atomic input

An atomic document is explicit and deterministic:

{
  "format": "motion-protocol",
  "formatVersion": 2,
  "composition": { "width": 1920, "height": 1080, "fps": 30 },
  "layers": []
}

What belongs where

Concern	High-level authoring	Atomic Protocol V2
Pattern and preset names	Yes	No
Semantic motion intent	Yes	No
Shape geometry	Described	Explicit
Transform pivot	Requested	`anchor`
World position	Requested	`translate.z`
Timeline window	Requested	`timing`
GPU resources	No	No

Determinism

An authoring surface may be expressive. The atomic result must be explicit enough that two runtimes can evaluate the same frame without guessing.

Static example policy

JSON blocks in this guide teach structure. They are not validated or rendered by the web documentation page.