Build a Product Design Library

Build the approved product library through seven gated phases. Scope enters only through product authority or a decision owner's choice. Competitor features and generic aesthetics are evidence, never authority.

Vocabulary

• authority — a source that binds the work: repository instructions, decision records, approved specifications, code, generated contracts, tests. Project authority outranks every generic design suggestion.
• decision owner — the human who approves scope, identity, fallbacks, and policy changes. Silence keeps a decision open.
• work owner — the one worker or process that may change a component, exported symbol, file, process, worktree, hostname, or route. Every item has exactly one. A work owner never approves a decision.
• claim — a worker report, walkthrough, scanner pass, screenshot set, or implementer full-suite run. A claim proves nothing on its own.
• receipt — an independent reviewer's recorded pass or block on a named artifact. Only a receipt accepts work. When no independent reviewer capability exists, the receipt is unreviewed: the gate stays closed, and the run reports it to the decision owner. Work never self-certifies.
• seam — the documented boundary where implemented data ends and proposed data begins. Live proof stops at the seam.
• cell — one route, mode, viewport, and state combination in the browser matrix. Only a valid capture proves a cell.
• stub — a temporary fallback. It exists only with the decision owner's explicit approval evidence, one work owner, and a deletion plan (rule).

Runtime skill routing

Resolve each capability by name from the current runtime skill registry. Before its first trigger in a phase, load a skill by reading its SKILL.md through the registry; load the agent-browser tool with agent-browser skills get core. Record each capability, its loaded status, and any limit in the contract's capability table.