Repository integration layer to the helic-forge agentic software factory and operations facility.
Find a file
tegwick 3a65b02db6 RMGR-WP-ADHOC-2026-10-27: note the forge adapter admission
The staged-scan record now points at the admitted Forgejo adapter instead of a waiting admission task.

Assistant: grok
Assistant-Model: grok-4.7
Assistant-Session: 01a17f2b-8cc3-76f0-9bce-3b3444b9a5e9
2026-10-27 23:01:48 +01:00
.githooks build: compose opt-in work-record generation with shared guards 2026-10-19 11:34:02 +02:00
config Package corrected publisher registry and complete prefix registrations 2026-10-03 10:33:26 +02:00
decisions Record the hub identifier for RMGR-DEC-2026-004. 2026-10-06 11:18:34 +02:00
docs RMGR-WP-ADHOC-2026-10-27: allow filename content digests in the staged secret scan 2026-10-27 22:28:18 +01:00
history docs: research SH repo tooling, architecture blueprint, RMGR-WP-0002 2026-08-09 23:04:49 +02:00
intakes Close prefix ownership intake after whynot-control correction 2026-10-03 10:37:21 +02:00
interfaces feat(identifiers): verify batch projections 2026-08-22 23:50:34 +02:00
registry docs(reuse): establish reviewed NetKingdom security capabilities 2026-10-14 06:44:25 +02:00
schemas feat(handoffs): publish owner task interfaces 2026-08-22 14:15:48 +02:00
specs docs: research SH repo tooling, architecture blueprint, RMGR-WP-0002 2026-08-09 23:04:49 +02:00
src/repo_manager RMGR-WP-ADHOC-2026-10-27: allow filename content digests in the staged secret scan 2026-10-27 22:28:18 +01:00
tests RMGR-WP-ADHOC-2026-10-27: allow filename content digests in the staged secret scan 2026-10-27 22:28:18 +01:00
workplans RMGR-WP-ADHOC-2026-10-27: note the forge adapter admission 2026-10-27 23:01:48 +01:00
.dockerignore feat: publish classifications from Forgejo 2026-09-01 01:39:39 +02:00
.generated-work-records.json build: compose opt-in work-record generation with shared guards 2026-10-19 11:34:02 +02:00
.generated-work-records.mk build: compose opt-in work-record generation with shared guards 2026-10-19 11:34:02 +02:00
.gitignore build: keep generated orientation brief local and untracked 2026-10-19 13:44:23 +02:00
.repo-classification.yaml Seed Repo Manager foundation 2026-08-09 16:36:09 +02:00
AGENTS.md apply reef identifier batch 0006 2026-08-31 14:10:44 +02:00
Containerfile feat: publish classifications from Forgejo 2026-09-01 01:39:39 +02:00
INTENT.md RMGR-IN-0004: reconcile flex-auth registry entry to access-engine 2026-09-30 18:56:10 +02:00
Makefile build: compose opt-in work-record generation with shared guards 2026-10-19 11:34:02 +02:00
pyproject.toml feat: finish register receiving and authority routing 2026-08-21 23:15:48 +02:00
README.md Adopt reviewed InterfaceCanon projection terminology 2026-09-09 22:42:31 +02:00
SCOPE.md feat: prepare disabled fixed-policy Custodian snapshot endpoint 2026-10-19 17:56:15 +02:00
uv.lock feat: publish classifications from Forgejo 2026-09-01 01:39:39 +02:00
WORK-RECORDS.md RMGR-WP-ADHOC-2026-10-27: allow filename content digests in the staged secret scan 2026-10-27 22:28:18 +01:00

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 workplan create --path . --workplan-id EX-WP-0001 --title "Example" --goal "Deliver X."
rmgr workplan update --path . --workplan-id EX-WP-0001 --status active
rmgr workplan delete --path . --workplan-id EX-WP-0001 --confirm  # archives; never erases
rmgr task add --path . --workplan-id EX-WP-0001 --title "Implement" --description "Deliver it."
rmgr task update --path . --task-id EX-WP-0001-T01 --status progress
rmgr adhoc add --path . --title "Small fix" --description "Complete the bounded fix."
rmgr sync --path . --push  # primary/railiance01 derives the exact pushed commit
rmgr register put --path . --kind technical-debt --entry-id TD-001 \
  --title "Debt item" --data-json '{"severity":"high"}'
rmgr register list --path . --kind technical-debt
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
rmgr scaffold --path . --refresh-hub-access --no-commit  # State Hub access table from config/state-hub-access.yaml

rmgr sync is the normal work-record closeout path. It uses the canonical kind registry, fills only missing deterministic UUIDv5 identifiers, refuses dirty or behind workplan sources, verifies that the API is primary/railiance01, and requests one central forge-derived reconciliation. A local/cache State Hub is never populated. registrar-reconcile remains only for sealed legacy UUID migration and repair.

Vertical-slice proof: docs/evidence/t05-vertical-slice.md.

Direction: