Manifest Model

The Master Home is fully data-driven from manifest.json. Canonical contract lives at knowledge/dev/ui/_master/manifest-contract.md; this doc summarizes the model used in v1.

Surface row fields

id, group, surface_name, description, status, approval_status, current_version, preview_url, spec_path, review_log_path, design_brief_path, owner_agent, next_action, dependencies, checklist{...}, updated_at

Status vocab (10)

not_started · idea · cowork_sketch · spec_ready · preview_deployed · needs_review · approved · design_polish · code_ready · implemented

Approval vocab (4)

none · pending_user_review · user_approved · changes_requested

Checklist (9 booleans, render order)

idea · cowork_sketch · spec_in_kb · preview_deployed · gpt_reviewed · user_approved · design_polished · code_ready · shell_implemented

Groups (4)

core-mow-mot · moit-mout · governance-ops · registry-managers

Summary-card derivation (computed client-side)

• total = count of surfaces.
• deployed previews = checklist.preview_deployed == true.
• pending review = approval_status == pending_user_review OR status == needs_review.
• approved = approval_status == user_approved OR status in {approved, implemented}.
• not started = status == not_started.

Evidence rule

A checklist box is only set true with KB/deploy evidence. No invented approvals; user_approved flips only from a human approval recorded in that surface's review-log.