coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
repo-manager/SCOPE.md
tegwick e3fbdbc148 docs: establish INTENT/SCOPE and activate RMGR-WP-0001 
Strengthen Intent and Scope for State Hub registration and HelixForge
boundaries; mark foundation workplan active. Classification synced via
register-from-classification (do not re-run statehub register bootstrap —
it collides with RMGR-WP-0001).
2026-08-09 21:55:59 +02:00

2.5 KiB
Raw Blame History

Scope

One-liner

Long-lived tooling component: repository representation, file-backed record indexing, consistency reconciliation, and governed repository control for HelixForge.

In scope

  • Repository registration, identity, classification, and lifecycle.
  • Local checkout, host-path, remote, revision, and synchronization awareness.
  • Discovery, parsing, validation, and indexing of repository-owned records.
  • Workplan, task, decision, capability, service, policy, and relationship declarations when their authoritative form is stored in a repository.
  • Consistency reconciliation between files and replaceable projections.
  • Controlled repository mutation through explicit commands and policy checks.
  • Repository event emission, idempotency, audit evidence, and recovery.
  • Repository-specific coach, lead, and director agent assignments.
  • APIs and adapters through which hub-core addresses repositories (port.repo, port.work in the extension architecture).

Out of scope

  • Cross-domain inboxes, conversations, and message routing: hub-core.
  • General work or issues without a repository authority: issue-core.
  • Recurring scheduling and workflow execution: activity-core.
  • Authentication, user directories, and identity proofing: identity authorities.
  • Authorization policy decisions: flex-auth or its successor.
  • Credential custody: OpenBao/platform credential services.
  • Git hosting: Forgejo or another source-code forge.
  • Domain-specific operational, financial, security, or governance truth.
  • A universal knowledge store or search engine.
  • Hosting production domain-hub business data or operator consoles.

Coordination

Item Location
Parent project prj-state-hub-retirement
Stream S1 in architecture/child-workplan-map_v0.1.md
Foundation workplan RMGR-WP-0001
Disposition inventory prj-state-hub-retirement/inventory/ (repo-* capabilities)

Initial extraction source

The first implementation may reuse proven State Hub behavior for repository registration, host paths, workplan parsing, consistency reconciliation, and file-backed status changes. Extraction must preserve behavior with compatibility tests while removing assumptions that Repo Manager owns cross-domain state.

API boundary

External consumers use versioned contracts. They must not depend on Repo Manager's persistence schema. Commands distinguish requested action from confirmed repository state; a successful command is not complete until the resulting repository revision and normalized event are recorded.