Molloy-Home/minions-template
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: refine downstream onboarding workflow

Browse Source
This commit is contained in:
deamonkai
2026-04-12 13:56:28 -05:00
parent e650ec65d1
commit 7dd35f3975
11 changed files with 93 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/collaboration-playbook.md
View File

@@ -39,7 +39,7 @@ Onboarding should explicitly set:
Onboarding should use `docs/downstream-onboarding-playbook.md`, not a blind
repo copy.
- vendor the template snapshot into `.minions-template/`
- vendor an export-ready template snapshot into `.minions-template/` with `.git/` and `do-not-export` files excluded
- export the live operating files using `docs/export-manifest.md`
- manually merge `INIT.md`, `MEMORY.md`, `docs/operator-onboarding-checklist.md`, and `minion-version.md`
- commit the vendored snapshot and exported live state together as the initial baseline
@@ -49,8 +49,8 @@ repo copy.
Use `PM` as the default owner for downstream template upgrades.
- onboarding should establish `.minions-template/` first; upgrades depend on that baseline
- keep the approved template snapshot in `.minions-template/`
- stage the incoming template in a temporary path such as `.minions-template.next/`
- keep the approved export-ready template snapshot in `.minions-template/`
- stage the incoming export-ready template in a temporary path such as `.minions-template.next/`
- compare old template, new template, and live downstream files before changing production minion docs
- use `docs/export-manifest.md` to decide whether each file is replaced, manually merged, or left downstream-owned
- update the downstream base template version only after the live files and vendored snapshot both match the approved upgrade