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

docs: add architect role and template workflows

Browse Source
This commit is contained in:
deamonkai
2026-04-12 12:25:07 -05:00
parent 64de2660d2
commit e650ec65d1
18 changed files with 626 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
minion-version.md
View File

@@ -1,7 +1,25 @@
# Minion Template Version
Current version: 1.2.5-1.0.0
Current version: 1.3.0-1.0.0
Version format for downstream repos: `<base-template-version>-<downstream-version>`
Example downstream version: `1.2.5-1.0.0`
Example downstream version: `1.3.0-1.0.0`
## Downstream Onboarding Method
- Keep the initial template snapshot in `.minions-template/`.
- Use [docs/downstream-onboarding-playbook.md](docs/downstream-onboarding-playbook.md) and [docs/export-manifest.md](docs/export-manifest.md) to perform the first controlled export into the live downstream repo.
- Treat `INIT.md`, `MEMORY.md`, `docs/operator-onboarding-checklist.md`, and `minion-version.md` as onboarding merge files, not blind copies.
- Commit the vendored snapshot and exported live files together so later upgrades have a stable comparison base.
## Downstream Upgrade Method
- Keep the currently approved template snapshot in `.minions-template/`.
- During upgrade, stage the incoming template in a temporary path such as `.minions-template.next/`.
- `PM` owns the downstream merge/migration unless the Operator assigns another owner.
- Use [docs/downstream-upgrade-playbook.md](docs/downstream-upgrade-playbook.md) and [docs/export-manifest.md](docs/export-manifest.md) to compare:
- old vendored template
- new vendored template
- live downstream files
- Only update the base-template portion of `minion-version.md` after the live files and vendored snapshot both reflect the approved upgrade.