Production readiness means the source file, page template, runtime, assets, and public rendering all agree. Do not use local visual success as the only proof.

Source checks

• The .fmtion file parses as JSON and passes generated schema validation.
• The source includes explicit meta.name and any needed version/runtime metadata.
• Node types, port names, params, dynamic ports, gates, overrides, and assets match source-of-truth metadata.
• The source is committed or published through the correct source-backed flow for the owning page.

Runtime checks

• load(file) succeeds without unexpected normalization, preflight, or mount failures.
• debug.validate() returns no error-severity findings.
• Accepted warnings are recorded with reason and owner.
• play(), pause(), and dispose() behave correctly for route or component lifecycle.

Visual checks

• DOM selectors match at desktop and mobile widths.
• Canvas and 3D surfaces are nonblank at first paint, after resize, and after route transitions.
• Scroll scenes reach start, midpoint, end, and release states.
• Cross-scene texture wires, texture stats, physics readers, and state-machine state are checked where relevant.
• Reduced-motion behavior is acceptable for large movement, repeated text effects, particles, or camera motion.

Verified runnable examples

This guide points to proof-backed sample coverage. The full ledger lives in Generated examples and proof log.

DOM: Scroll fade reveal

• Source: faster-motion/demo/tests/dom/catalog/scroll-animations/fade-reveal/fade-reveal.domgraph.fmtion
• Expected output: Sections fade and translate into place as their trigger elements enter the configured viewport range.
• Validation: Schema validation passed. Runtime proof reports zero structural/runtime issues and 17 loaded nodes.
• Desktop proof: generated-assets/faster-motion-docs/proofs/screenshots/dom-fade-reveal-desktop.png
• Mobile proof: generated-assets/faster-motion-docs/proofs/screenshots/dom-fade-reveal-mobile.png

Canvas: Fill rule diagnostic

• Source: faster-motion/demo/tests/canvas/fillrule-diagnostic/fillrule-diagnostic.fmtion
• Expected output: A contained Canvas scene renders paired path cases so nonzero and evenodd fill handling can be compared visually.
• Validation: Schema validation passed. Runtime proof reports zero blocking runtime issues and 10 rendered objects; the accepted metadata note is preserved in the proof ledger.
• Desktop proof: generated-assets/faster-motion-docs/proofs/screenshots/canvas-fillrule-diagnostic-desktop.png
• Mobile proof: generated-assets/faster-motion-docs/proofs/screenshots/canvas-fillrule-diagnostic-mobile.png

Guide-specific sample target: Production checklist sample attached to one public page with validation output, screenshots, and accepted-warning log.

Faster Motion docs

Use this local map together with the left navigation. The source-backed content tree controls the main article order; this section keeps related pages one click away.

Start

• Faster Motion docs map
• Faster Motion documentation overview
• Get started with Faster Motion
• Faster Motion concepts
• .fmtion file format

DOM animation

• DOM animation guide
• DOM selectors and targets
• Scroll animation
• Pointer, hover, and drag inputs
• Text, SVG, and path animation
• Responsive gates and parameter overrides

Canvas animation

• Canvas animation guide
• Canvas area lifecycle
• Canvas objects, assets, and rendering
• Canvas inputs and state machines

3D and procedural

• Canvas 3D and procedural guide
• 3D scenes, cameras, and lights
• Procedural geometry and fields
• Particles and physics

Reference

• Node reference index
• Node categories reference
• Runtime loading and publishing
• Runtime API reference
• Debugging and preflight
• Debug API reference
• Validation errors and warning codes
• Faster Motion production checklist
• Faster Motion recipes overview