coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Repository integration layer to the helic-forge agentic software factory and operations facility.
73 commits 1 branch 0 tags 2.6 MiB
Find a file
tegwick de97132aef docs(RMGR-WP-0005): registrar fix is gated on the railiance01 remote sweep 
The registrar fix is one env var, not host provisioning: the state-hub
deployment has STATEHUB_REGISTRAR unset, and that pod is the real automated
instance -- it mounts /home/tegwick rw and /home/tegwick/.ssh for push.

But setting it now would be harmful. railiance01 has 70 repos still on
gitea-remote (92.205.130.254) against 7 on forgejo-remote (92.205.62.239),
while the workstation is 126/0 on forgejo. The pod would mint identifiers
into checkouts tracking the superseded server and push them there.

Records the required order -- reconcile railiance01's remotes first, then
enable the registrar -- and that the sweep pod is currently operating against
those stale checkouts.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 09:37:49 +02:00
config feat: model repo standards and detect prefix collisions 2026-08-18 13:28:40 +02:00
docs feat: interim identifier registrar (RMGR-WP-0005-T01) 2026-08-18 21:49:08 +02:00
history docs: research SH repo tooling, architecture blueprint, RMGR-WP-0002 2026-08-09 23:04:49 +02:00
specs docs: research SH repo tooling, architecture blueprint, RMGR-WP-0002 2026-08-09 23:04:49 +02:00
src/repo_manager feat: interim identifier registrar (RMGR-WP-0005-T01) 2026-08-18 21:49:08 +02:00
tests feat: interim identifier registrar (RMGR-WP-0005-T01) 2026-08-18 21:49:08 +02:00
workplans docs(RMGR-WP-0005): registrar fix is gated on the railiance01 remote sweep 2026-08-21 09:37:49 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-21 09:12:45 +02:00
.gitignore feat(RMGR-WP-0001): complete T05 end-to-end vertical slice 2026-08-09 22:49:31 +02:00
.repo-classification.yaml Seed Repo Manager foundation 2026-08-09 16:36:09 +02:00
AGENTS.md Seed Repo Manager foundation 2026-08-09 16:36:09 +02:00
INTENT.md docs: establish INTENT/SCOPE and activate RMGR-WP-0001 2026-08-09 21:55:59 +02:00
Makefile docs(RMGR-WP-0001): complete T04 implementation foundation 2026-08-09 22:41:26 +02:00
pyproject.toml docs(RMGR-WP-0001): complete T04 implementation foundation 2026-08-09 22:41:26 +02:00
README.md feat: flavor-correct rmgr scaffold; record C-15/C-23 file-wins 2026-08-18 13:36:26 +02:00
SCOPE.md docs: establish INTENT/SCOPE and activate RMGR-WP-0001 2026-08-09 21:55:59 +02:00
WORK-RECORDS.md chore(consistency): refresh work-record index 2026-08-18 21:53:20 +02:00

README.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:

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: