Acceptance and rollout

Prototype and site checks

• All four Lunchbreakers tabs are directly addressable; Summary default and refresh/back behavior are correct.
• All 57 policy IDs/titles/source lines survive; search, group jump, disclosures and source download work.
• All 18 treasury months are contiguous; both ledgers reconcile; totals, charts, monthly reports and exports agree; USD and KI never combine.
• Profile membership toggles; purpose precedes official details; chat uses correct Scout; no duplicate Visit link.
• Scoped index has one supplied Initiative, no personal-draft block; Activities and Actions retain DUNA scope on refresh/back; global collections remain global.
• Contextual forms inherit the correct parent; Action choice cannot select another DUNA; local draft/publish and Remix preserve lineage.
• Header tagline stays on one line at phone width; right-aligned Create/Remix have accessible names; flag and Back this Initiative copy are consistent.
• Connection overview hides counts and shows Connect Tools or green Connected from settings; disconnect updates the state.
• Every original K001–K101 remains; exactly 52 reported K-items move out of active requirements; both K095 report lines remain; all 71 completed entries plus the map rollout are accounted for.
• Current route registry, original 539-route inventory, historical drafts, Architecture and kit downloads resolve; homepage panels remain readable on desktop and narrow screens.

Production acceptance still required

Test routing accuracy and clarification; private/secret context isolation; Mask identity protection; purpose mismatch rerouting; stale draft rejection; checkpoint retries; atomic publication; simultaneous claim/complete cases; duplicate evidence detection; returned revision gates; reviewer conflict/escalation; revoked Tool grants; idempotent sends; event ordering; background-trigger ownership; truthful progress; inaccessible sources; and failed network/OAuth return paths.

For governance and money: execute the Governance kit's service acceptance cases; configure an actually adopted ruleset; freeze electorate and ballot revision; independently reproduce decisions; validate mandates, custody, signers and restrictions; test failed/partial execution and reconciliation; never infer adopted policy from a sample page.

Suggested rollout order

1. Reconcile current code/build IDs with Aashik’s completion report; verify the development maps deployment.
2. Confirm role/parent/version identities and migrate existing records without deleting history.
3. Implement shared authorization, commands, receipts and events.
4. Connect permissioned context and one router; validate clarification and rerouting before broad tool execution.
5. Bind DUNA Skills and source-backed wisdom; integrate the research/draft/publish pipeline and instance reuse.
6. Add review escalation and policy-controlled proposal/distribution preparation.
7. Enable live execution only after adopted rules and scoped authority pass acceptance. Release interface changes alongside real status, not placeholder “connected” claims.