tegwick
a6d4a9b615
RMGR-WP-0004-T03: project repos get GOAL.md and a required prefix. RMGR-WP-0005-T06 implemented in state-hub consistency.
2.2 KiB
2.2 KiB
repo-manager
Repository integration boundary for the HelixForge agentic software development and operations environment.
Repositories remain independently valid and usable. Repo Manager gives each repository a stable representation inside HelixForge, observes its declared state, performs governed repository changes, and hosts its coach/lead/director agent representation.
| Flavor | tooling (not a domain hub) |
| Domain | infotech |
| Parent project | prj-state-hub-retirement |
| Foundation WP | RMGR-WP-0001 |
Start with INTENT.md, SCOPE.md, and the genesis record.
Architecture:
- Repository representation v0.1
- Observation and command contracts v0.1
- State Hub extraction inventory v0.1
- ADR-001 Implementation foundation
- Railiance app deployment guide (
RMGR-WP-0006) - Repository standards v0.1 (
RMGR-WP-0004)
make install # or: uv pip install -e ".[dev]"
make test
rmgr --version
rmgr observe --path .
rmgr reconcile --path .
rmgr update-task-status --path . --task-id <ID> --status progress
rmgr rapp wrap --path ../rapp-some-app --app some-app \
--ownership-repo some-app --from-app ../some-app
rmgr rapp validate --path ../rapp-user-engine --family-root ..
rmgr rapp place --path ../rapp-some-app --reef reef-railiance
rmgr conform --path .
rmgr prefix-uniqueness --root ..
rmgr scaffold --path ../prj-example --flavor project --wp-prefix EX-WP --no-commit
Vertical-slice proof: docs/evidence/t05-vertical-slice.md.
Direction: