# 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](../prj-state-hub-retirement) |
| **Foundation WP** | [RMGR-WP-0001](workplans/RMGR-WP-0001-foundation.md) |

Start with [INTENT.md](INTENT.md), [SCOPE.md](SCOPE.md), and the
[genesis record](history/2026-08-09-genesis.md).

Architecture:

- [Repository representation v0.1](docs/repository-representation_v0.1.md)
- [Observation and command contracts v0.1](docs/observation-command-contracts_v0.1.md)
- [State Hub extraction inventory v0.1](docs/state-hub-extraction-inventory_v0.1.md)
- [ADR-001 Implementation foundation](docs/adr-001-implementation-foundation.md)

```bash
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
```

Vertical-slice proof: [docs/evidence/t05-vertical-slice.md](docs/evidence/t05-vertical-slice.md).

Direction:

- [State Hub repo tooling research](history/2026-08-09-state-hub-repo-tooling-research.md)
- [Architecture blueprint (retirement path)](specs/ArchitectureBlueprint.md)
- Next: [RMGR-WP-0002](workplans/RMGR-WP-0002-retirement-dual-run-strangler.md) dual-run strangler