Practice

Adopting Hive

Both companion packs adopt the same way: copy a scaffold, rename the templates, get an Admin lock, then register the instance. Neither pack requires reading another product's build-master rules first.

New build-master (unit loop)

cp -R ⟨lk-bloom⟩/hive/master-build/scaffold \
  /path/to/<product>_build-master
# rename *.template → Seed-from-idea, or fill by hand
# Admin program lock → register hive/master-build/INSTANCES.md

New agent-team-pool (org chart)

cp -R ⟨lk-bloom⟩/hive/agent-team-pools/scaffold \
  /path/to/<product>-master-dev-bot-pool
# rename *.template; copy pools/_POOL.template → pools/<id>/
# Master Pool Lead + path map → Admin pool lock
# register hive/agent-team-pools/INSTANCES.md

Before program lock

• Seed fills the bee roster and declares assigned local project paths in AGENTS.md.
• CP-0 mode is proposed (default admin-gated) — Admin sets the final mode at lock.
• Add or update a row in the public hive map template when the instance is a new product.

Upgrading an instance later

1. Read the changelog in the pack doctrine (MBP or pool pattern).
2. Pull new scaffold docs into the instance deliberately — never silently rewrite live rows.
3. Match local CLOSEOUT / COORDINATION / Seed surfaces to the tip you intend to pin.
4. Bump the instance's patternVersion / poolPatternVersion and its INSTANCES.md row.
5. Record the date and notes; leave older smoke pins alone unless Admin upgrades them.

Legacy root paths are frozen pointers — new work edits hive/ only, and product citations re-pin to hive/ only when Admin chooses.