tegwick
bae6d56dbe
T01 done: ADR-006 accepted with R1-R7. T02 unblocked and extended with the split disposition and the full owning-model list. New tasks (forward-only numbering per ADR-007): T11 land itc-evid and move Evidence out of itc-gov; T12 extend itc-org with Community and Household; T13 seed the Family concept area without authoring it. SCOPE.md: itc-org extension promoted from residual to scope; Family build-out explicitly out of scope. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
59 lines
2.8 KiB
Markdown
59 lines
2.8 KiB
Markdown
# Scope
|
||
|
||
## Project authority
|
||
|
||
This repository owns the cross-repository goal, concept-ownership boundary,
|
||
sequencing, dependency map, migration ledger, risks, acceptance gates, and
|
||
consolidated evidence for the canon federation effort.
|
||
|
||
It does not own canon content. Concepts live in the canons themselves.
|
||
|
||
## Participating repositories
|
||
|
||
- `the-custodian` — `ADR-006`; durable decisions and standards
|
||
- `info-tech-canon` — receives the identity model (`itc-ident`)
|
||
- `identity-canon` → `commerce-canon` — renamed in place; retains commercial content
|
||
- `state-hub` — repo slug rename, registration, agent-instruction regeneration
|
||
|
||
Downstream consumers (`fin-hub`, `target-revenue`, `adaptive-pricing`,
|
||
`qonto-assistant`) are **not** participants. They may pull from CommerceCanon
|
||
later via demand signal; their adoption is not a gate of this project.
|
||
|
||
## In scope
|
||
|
||
- Concept-ownership boundary across Custodian canon, InfoTechCanon, CommerceCanon.
|
||
- Resolution of the ownership collisions listed in `ADR-006` (R1–R7, accepted
|
||
2026-08-17).
|
||
- The `identity-canon` → `commerce-canon` rename and all fleet references to it.
|
||
- Landing `itc-ident` in InfoTechCanon with imports, not redefinitions.
|
||
- Landing `itc-evid`, the evidence model, per R3/R5/R7 — including moving
|
||
`Evidence` out of `itc-gov`, which becomes an importer.
|
||
- Extending `itc-org` with `Community` and `Household` under `CollectiveActor`
|
||
per R6. (Promoted from residual to scope by the R6 resolution.)
|
||
- Seeding `Family` as its own concept area per R6 — recording the concept,
|
||
its privacy sensitivity, and open modelling questions only.
|
||
- Bringing CommerceCanon to `InfoTechCanonRepositoryLayoutStandard` structure.
|
||
- Distributing the research corpus as provenance.
|
||
- Cross-canon interface cards.
|
||
|
||
## Out of scope
|
||
|
||
- Hosting canon content in this repository.
|
||
- Authoring new commercial concepts beyond what already exists in the glossary.
|
||
CommerceCanon grows by demand signal after the federation is in place.
|
||
- Building CommerceCanon's service surface (CLI/JSON/API). InfoTechCanon has one;
|
||
whether CommerceCanon needs one is a later, evidence-driven decision.
|
||
- Moving the Federated Organization Standard out of Custodian canon.
|
||
- Authoring the `Family` concept area beyond a seed. Family carries kinship,
|
||
guardianship, dependency, care, and legal/biological/social parenthood
|
||
structure that changes over time; building it out speculatively is the
|
||
failure mode R6 exists to avoid. It grows on demand signal.
|
||
- Consumer adoption of either canon.
|
||
- Retiring or deleting any repository.
|
||
|
||
## Work-record rule
|
||
|
||
This project records milestones, dependencies, gates, decisions, and cross-repo
|
||
acceptance. Each participating repository owns its own implementation workplan
|
||
and evidence. Project records link those workplans by stable identifier rather
|
||
than copying their task lists.
|