MoreProofFlagship System / MP-001

MotionProof: create and check web animations.

MotionProof checks animation files before they are packaged for a website or app. The browser example below uses four built-in recipes; it does not call an AI model.

Built with

Lottie, Chromium, Model Context Protocol, npm, GitHub.

The reliability gap

Generation made motion faster, but not shippable.

The pipeline started from a blunt observation: an agent can produce convincing source and a nice first preview while still handing engineering an artifact that is inaccessible, environment-dependent, visually empty, or impossible to audit.

I set the product bar, chose the provider-neutral and fail-closed architecture, directed the agent-assisted implementation, and held the result to a public, reproducible release gate. The point was not to hide the agents. It was to prove that agent-built software can still have a legible owner, explicit judgment, and evidence strong enough for someone else to trust.

Animated evidence cards converge into an attributed outcome in desktop and mobile compositions. — The same evidence-flow system rendered as desktop and recomposed mobile Lottie. Visitors who request reduced motion receive the checked-in poster instead of the animated proof.

Static reduced-motion poster showing evidence cards converging into an attributed outcome in desktop and mobile compositions. — The same evidence-flow system rendered as desktop and recomposed mobile Lottie. Visitors who request reduced motion receive the checked-in poster instead of the animated proof.

Try a built-in animation

Describe an effect to select a matching recipe, then preview the animation.

This browser example selects from four checked-in recipes; it does not call an AI model. The sample downloads differ from the compiler's full five-artifact output.

Integrated deterministic studio

No model call · no API key · checked-in recipes

Open release audit ↗

Recipe register

Certified sample previewsignal-flow

Signal Flow

Persistent rails route staggered signals into a credible processing outcome.

Install the public release

npm install https://github.com/HowdyDooToYou/lottie-animation-pipeline/releases/download/v2.0.0/motionproof-2.0.0.tgz

Authority trace

Who gets to decide?

Authority / Verifier

Move authority outside the provider.

Strict structure, vector-only content, quality, Chromium frames, meaningful motion, payload, and reduced-motion checks fail closed.

Receipt

Certification + raster evidence

What gets checked

The claim is backed by the compiler

MotionProof does not care which intelligence proposed the animation. It cares whether the artifact survives the same deterministic production contract.

File structure and size

Checks for strict structure, vector-only content, and payload constraints.

Browser rendering and movement

Verifies real Chromium frames, meaningful motion, and visual quality outside the provider.

Reduced-motion behavior and packaging

Ensures the presence of a poster for fallback and promotes passing candidates into one atomic bundle.

Release proof

Public source and dated release checks

The documented July 26, 2026 release candidate passed the complete release gate: rebuilding deterministic assets, testing the contracts, rendering the production library, packing the npm distribution, installing it in a clean consumer, creating a real bundle, and completing an MCP handshake.

Automated tests across generation, certification, packaging, MCP, and runtime policy

27/27

Production Lotties strict-valid and visibly rendered in Chromium

Hashed artifacts promoted together in every certified bundle

Reproduce the release decision

npm ci
npm run check:release

Evidence summary

MotionProof / Certified Motion Compiler

The role, enforced constraints, product judgment, and reproducible release evidence behind the public build.

Role: Set the product contract and directed an agent-assisted implementation and release across the SDK, CLI, MCP server, Agent Skill, plugin bundles, certifier, and product studio.
Constraints: The core had to stay provider-neutral and zero-key by default, reject executable or external Lottie content, produce a reduced-motion poster, stay within a 500 kB animation budget, and promote complete bundles atomically.
Judgment: Separated proposal from authority: any model, agent, recipe, or human can propose a candidate, but only deterministic structure, quality, browser-render, motion, payload, and accessibility gates can promote it.
Evidence: The release gate passed 52 automated tests, strict validation for 27 of 27 production Lotties, Chromium rendering for 27 of 27, a clean consumer-package install, a certified five-artifact smoke bundle, and a three-tool MCP handshake.

Technical explanation

Interfaces, bundle contents, and licenses

A proposal from an agent, model, or human enters a portable contract, gets proven against Chromium rendering, and is promoted into one atomic bundle.

Drop-in surfaces

Typed SDK

Applications bring any provider through one small interface.

JSON CLI

Humans and coding agents get stable stdout, exit codes, and structured failure.

Local MCP

Three tools expose creation, certification, and recipe discovery.

Agent Skill

One portable workflow teaches compatible hosts the same definition of done.

Bundle contents

animation.json: Editable, certified vector motion
poster.png: Reduced-motion and no-JavaScript fallback
preview.html: Portable offline review surface
certification.json: Checks, quality, and raster evidence
manifest.json: Hashes, provenance, prompt hash, and artifact inventory

Open-core licensing

The SDK, CLI, MCP server, Agent Skill, plugins, deterministic recipes, certifier, and local studio ship under the recipient's choice of MIT or Apache-2.0—including commercial use. Released open-core rights do not move backward.

Back to All Work