coulomb/prj-canon-federation
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fold ADR-006 resolutions into CFED-WP-0001 and project scope

Browse source 
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>
This commit is contained in:
tegwick 2026-08-17 10:03:26 +02:00
parent 8b559ef999
commit bae6d56dbe
3 changed files with 151 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

16
SCOPE.md
View file

@ -22,9 +22,16 @@ 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 six ownership collisions listed in `ADR-006`.
- 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.
@ -37,9 +44,10 @@ later via demand signal; their adoption is not a gate of this project.
- 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.
- Extending `itc-org` with social collectives (`Community`, `Family Or
Household`) beyond recording the recommendation — that is an InfoTechCanon
workplan if adopted.
- 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.