Run a design review
The proof-of-loop for the whole platform: a design deliverable that only ships after a physical approve.
How it works
The design coworker builds an artifact — a token set, a Hardware Buddy character pack — and lints it (WCAG contrast, the 8-token system) before asking to publish. Publishing is two-phase: artifact_request_publish asks, the operator approves or denies on the buddy device, and only then does artifact_finalize_publish run. Nothing about the artifact itself is gated; only the act of making it live is.
Why this is the reference example
The artifact, the role, and the approval surface are one coherent story end to end: a design decision becomes a real object the buddy can render, and the same object is what the operator is approving. Every other gated role (Legal, Finance) reuses this exact emit → decide → finalize sequence — only the MCP tools and the gates.toml policy differ.
Related
70fa00c6ad4466e6 · verify