52 lines
1.7 KiB
Markdown
52 lines
1.7 KiB
Markdown
|
# Scope
|
||
|
|
|
||
|
|
## Project authority
|
||
|
|
|
||
|
|
This repository owns the cross-repository project goal, target architecture,
|
||
|
|
decisions, sequencing, dependency map, migration ledger, risks, acceptance
|
||
|
|
gates, and consolidated evidence for State Hub retirement.
|
||
|
|
|
||
|
|
It does not own the production implementations being changed.
|
||
|
|
|
||
|
|
## Participating repositories
|
||
|
|
|
||
|
|
Initial participants include:
|
||
|
|
|
||
|
|
- `hub-core`
|
||
|
|
- `core-hub`
|
||
|
|
- `state-hub`
|
||
|
|
- `repo-manager`
|
||
|
|
- `activity-core`
|
||
|
|
- `issue-core`
|
||
|
|
- `the-custodian`
|
||
|
|
- `ops-hub`
|
||
|
|
- `fin-hub`
|
||
|
|
- identity, authorization, audit, and knowledge components as their boundaries
|
||
|
|
are resolved
|
||
|
|
|
||
|
|
## In scope
|
||
|
|
|
||
|
|
- Repository-flavor and temporary-project conventions.
|
||
|
|
- HelixForge information architecture and authority model.
|
||
|
|
- Orthogonal Architecture extension contracts and conformance.
|
||
|
|
- Core-hub-to-hub-core consolidation and cutover.
|
||
|
|
- Repo Manager foundation and State Hub repository-capability extraction.
|
||
|
|
- State Hub capability, data, consumer, and integration inventory.
|
||
|
|
- Cross-repository implementation sequencing and acceptance gates.
|
||
|
|
- Compatibility adapters, migration evidence, rollback, and retirement.
|
||
|
|
|
||
|
|
## Out of scope
|
||
|
|
|
||
|
|
- Hosting production implementation code in this project repository.
|
||
|
|
- Replacing child-repository workplans with duplicate project tasks.
|
||
|
|
- Becoming a permanent portfolio database, message system, or knowledge store.
|
||
|
|
- Rewriting specialized services whose authority remains valid.
|
||
|
|
- Deleting historical repositories or evidence.
|
||
|
|
|
||
|
|
## Work-record rule
|
||
|
|
|
||
|
|
The project records milestones, dependencies, gates, decisions, and cross-repo
|
||
|
|
acceptance. Each participating repository owns its implementation workplan and
|
||
|
|
evidence. Project records link those workplans by stable identifier rather than
|
||
|
|
copying their task lists.
|