Core loop
Core loop
The Understand→Ship production loop that turns vague creative prompts into brand-bound, validated output.
Pax replaces one-off "make it beautiful" prompts with a repeatable loop every agent adapter implements from the same canonical source. Each stage produces artifacts your team can inspect, diff, and reproduce.
What you will learn
- Eight stages from repository scan to shipped handoff
- Checkpoints you can resume without replaying the full chat
- Visual proof gates before anything ships
- Same loop for Design, Motion, Lottie, and Film pillars
The loop
Understand → Direct → Design → Build → Render → Critique → Repair → Ship| Stage | You prove | Primary commands |
|---|---|---|
| Understand | Brand scan and repository context | paxfx understand scan, paxfx understand brand |
| Direct | Creative thesis, composition, motion rationale | paxfx direct generate, paxfx direct approve |
| Design | Registry selections bound to tokens | paxfx design plan, paxfx design match |
| Build | Implementation with reduced-motion paths | paxfx design add, paxfx ship add |
| Render | Captures at mobile, tablet, desktop | paxfx preview, paxfx film demo |
| Critique | .pax/reports/check.json | paxfx critic, paxfx check --rendered |
| Repair | Targeted fixes mapped to finding ids | paxfx repair (max 3 passes) |
| Ship | Handoff with rationale and reproduction | paxfx ship export |
Concept first
Think of the loop as proof over promises. Agents do not ship copy or motion because it sounds good. They ship because each stage left an artifact that passed validation.
Understand reads what is already true: tokens, typography, routes, and motion habits in your repository. Direct locks a creative thesis before pixels move. Design and Build bind registry assets to semantic roles so blocks and effects inherit brand law. Render and Critique capture what users actually see, including reduced-motion pathways. Repair applies only high-confidence fixes. Ship exports with manifests so anyone can reproduce the output.
Status labels
| Capability | Status |
|---|---|
| Protocol adapters (Cursor, Claude, Codex, OpenCode) | production |
| Brand intelligence ingest | production |
| Rendered frame diff (Playwright) | production |
| Film segment queue with crash recovery | beta |
| html-in-canvas component effects | experimental |
Resume from checkpoints
After any completed stage, resume from .pax/protocol/run.json. Do not replay the full chat. See Protocol reference for schema and adapter parity checks.
Runnable full-loop recipe
Expected result
Each command exits 0 and writes inspectable artifacts under .pax/. The critic report lists deterministic checks with pass/fail and remediation hints.
Related
Was this page helpful?
Answers are not recorded or transmitted. Pax has no telemetry.