Repository integration layer to the helic-forge agentic software factory and operations facility.
ADR-007 amended 2026-08-21 to derive C2 identifiers for live records only, so T03's uniqueness prerequisite now has a bounded surface: 11 live files across 5 identifiers, not 48. T03 moves wait -> todo with the derivation rules recorded, including that namespace is the fleet branch and not the repository, that derivation is not retroactive, and that un-archiving is a collision hazard needing its own check. T09 gains the remediation assignment, split by root cause: 5 files are stragglers from its own incomplete RAILIANCE-WP retirement, 4 are the never-assigned WHYNOT-WP prefix, and 2 are same-repo reuse in kontextual-engine. Execution stays with workers in each repo per ADR-007 decision 4. Notes that both WHYNOT-WP-0001 files are statehub-bootstrap workplans -- the generic bootstrap defect STATE-WP-0080 contained -- so the same residue is likely wherever that path ran before the guard. Also records OPS-WP and REPO-WP as unassigned shared prefixes with no live collisions yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| config | ||
| docs | ||
| history | ||
| specs | ||
| src/repo_manager | ||
| tests | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| INTENT.md | ||
| Makefile | ||
| pyproject.toml | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
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: