The Build Pattern is the operational layer under Bloom Protocol governance: Seed-from-idea, roles, the unit loop, hard gates, post-merge CLOSEOUT, CP-0 policy, and a copyable scaffold — expressed at ground level, without forking the governance SOP it sits on.
One unit of work
A unit is one blueprint or workstream slice, always the same shape: one git
worktree outside the primary checkout, one branch from fresh
origin/main, one independent audit report, one future PR after
preview, and one post-merge CLOSEOUT. The primary checkout itself stays on
main — feature work never parks there in a long-lived branch.
Seed, then the loop
A program starts with Admin's idea, not with code. Only after Admin locks the program does the recurring unit loop begin:
Admin idea → Seed agent drafts MASTER-PLAN + WORKSTREAMS + BP-01 + COMPOSER + AGENTS
→ STOP — awaiting Admin program lock (no CP-0, no worktree, no feature code)
→ Admin locks program (status → admin-locked / active)
→ hand off to the unit loopCP-0 per CP0-POLICY → Orchestrator picks next unit → worktree from fresh origin/main
→ Build agent: Plan → Build → Check (acceptance) → handoff-ready
→ Audit agent (never the builder): PASS / PASS-WITH-NOTES / FAIL
→ Admin sandbox preview — not yet a PR
→ Publisher: PR after preview approval → merge
→ CLOSEOUT → next unit, again per CP0-POLICYHandoff-ready ≠ PR-ready ≠ closeout-done. Handoff-ready means audited. PR-ready means audited and Admin sandbox-preview-approved. Closeout-done means the land is verified, the SoR is updated, dual worklogs and linked history are written, and the primary checkout is synchronized.
Roles
| Role | Owns | Must not |
|---|---|---|
| Admin (human) | Program lock after Seed; PREP/READY go; sandbox preview; waivers; merge authority; CP-0 mode; cross-hive share gates | Leave preview to agents as substitute; skip program lock |
| Seed agent | Draft MASTER-PLAN, WORKSTREAMS, first BP, COMPOSER, AGENTS | Implement feature code; CP-0; open worktrees; grant program lock |
| Executive-ops bee | Executive docs; COMPOSER / INSTANCES hygiene drafts | Program lock; promote; preview; merge |
| Design bee | design-handoff/; UI catalog slots | Feature merge without audit/preview; expand walls alone |
| Orchestrator | Pick unit, CP-0 per policy, spawn build/audit, keep the ledger true | Write feature code; auto-CP-0 unless eligible; expand walls |
| Build agent | Implement the unit in a worktree; self-check; reach handoff-ready | Audit itself; open a PR before preview; write outside assigned paths |
| Audit agent | Independent check: PASS / PASS-WITH-NOTES / FAIL | Commit to the build branch; grant preview approval |
| Publisher | PR after preview; attach audit; merge; hand off to CLOSEOUT | Open a PR without preview approval; skip CLOSEOUT |
Hard gates
A representative slice of the required gates — the full list runs to twelve:
| Gate | Rule |
|---|---|
| Admin program lock | No unit CP-0 until program status is admin-locked or active |
| Independent audit | Never the build agent auditing itself |
| Human sandbox preview before PR | Admin may waive docs-only in writing |
| One unit / one worktree / one PR | No shared worktrees across units |
| Post-merge CLOSEOUT | Full recipe in 04-agent-ops/CLOSEOUT.md |
| Dual worklogs on CLOSEOUT | Overview + tech under the product's workLogsRoot |
| CP-0 policy | Default admin-gated; automation-eligible only when the adapter sets it and every CP0-POLICY check PASSes |
CP-0 policy
CP-0 is the ledger-started + worktree-spawn gate. It has exactly
two modes, and automation never expands hard walls, skips audit, or skips
preview:
| Mode | Who starts units |
|---|---|
admin-gated (default) | Admin unlock phrase before each gated CP-0 |
automation-eligible | Orchestrator may auto-CP-0 when all circumstance checks PASS — in-domain, program locked, blueprint exists, COORDINATION ok, local safe defaults; preview rules still apply |
Red lines
- Do not fork
BLOOM-PROTOCOL.md— cite the suite, don't copy and drift. - Do not CP-0 before Admin program lock.
- Do not auto-CP-0 unless the adapter is
automation-eligibleand every CP0-POLICY circumstance check PASSes. - Do not leave Seed without a filled bee roster in
AGENTS.md. - Do not work outside the assigned local project without a human-Admin-gated cross-hive share.
Canonical source: master-build/MASTER-BUILD-PATTERN.md · adopt steps: master-build/README.md.