tegwick
8a1f1b9fb2
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
80 lines
4.1 KiB
Markdown
80 lines
4.1 KiB
Markdown
# Concept-ownership migration ledger
|
|
|
|
`concept-ownership.json` assigns every heading in the project-start donor
|
|
glossary to its intended destination under CUST-ADR-006 accepted-1. This is
|
|
migration metadata, not a new home for canonical definitions.
|
|
|
|
`source-inventory.json` pins the donor commit, path, SHA-256, exact headings,
|
|
and source line numbers. The baseline is the last repository commit before
|
|
2026-08-17 UTC; the glossary itself last changed on 2026-06-21. No definitions
|
|
are copied into this repository. Git history remains the provenance source
|
|
after the rename.
|
|
|
|
## Reading the assignments
|
|
|
|
- `own`: a source concept moves to and is owned by the named destination.
|
|
- `import`: an upstream owner supplies the concept; migration consumers refer
|
|
to it rather than copying its definition. Community requires the T12 extension.
|
|
- `split`: one source entry becomes separately owned destinations. Family Or
|
|
Household becomes Household in itc-org and a separate Family seed.
|
|
- `retire`: no destination, with an explicit rationale. None are currently retired.
|
|
|
|
The four convenience terms retain that status. Their owners steward resolution
|
|
guidance; the ledger does not promote them to canonical roots.
|
|
|
|
The registry's `counterparty` and `family-area` values are migration locators,
|
|
not newly approved model identifiers. Destination repositories choose their
|
|
permanent identifiers through their own review processes. The general evidence
|
|
strength label is similarly provisional. `additional_required_concepts` records
|
|
the Evidence and strength requirements from ADR-006 that are not source headings.
|
|
|
|
## Validation
|
|
|
|
Run from this repository:
|
|
|
|
```bash
|
|
python3 tools/validate_ownership.py
|
|
python3 tools/validate_ownership.py --source-repo ../commerce-canon
|
|
python3 -m unittest discover -s tools -p 'test_*.py'
|
|
```
|
|
|
|
After rename, pass `../commerce-canon` instead. The second command checks the
|
|
inventory against the pinned Git blob, independent of current working-tree edits.
|
|
The first can check assignments offline without the donor checkout.
|
|
|
|
Validation requires complete source coverage, one mapping per source heading,
|
|
valid disposition cardinality, registered owners, and no destination concept
|
|
assigned to different owners. It preserves convenience-term status and validates
|
|
the Family/Household split structurally. It does not establish semantic
|
|
equivalence from different names or inspect published canon definitions.
|
|
|
|
## Publication prerequisites
|
|
|
|
T05 must reconcile `Delegation Relationship` with existing itc-org section 10.18
|
|
`Delegation`. ADR-006 assigns actor-linking delegation to identity, but the
|
|
existing organization model already defines bounded delegation of authority.
|
|
Changing the label alone does not resolve the overlap. Preserve the accepted
|
|
assignment until the canon review resolves the boundary; if ownership must
|
|
change, amend the governing decision before publication.
|
|
|
|
T06 must rewrite the old Evidence Source subtype language in Reputation Signal,
|
|
Performance Evidence, and Beneficial Ownership Exemption against the new
|
|
assertion/source distinction. Commerce imports Adjudication Outcome from
|
|
itc-evid. T11 must remove Evidence ownership from itc-gov.
|
|
|
|
These are implementation requirements in the existing live workplan, not
|
|
untracked residuals. The ledger check supplies G2 validation evidence; accepted
|
|
project completion and proof of zero duplicate published definitions remain
|
|
separate review gates.
|
|
|
|
The [corpus distribution ledger](corpus-distribution.json) records T07's frozen
|
|
research destinations and exact shared fragments. Reproduce G6 with
|
|
`python3 tools/validate_corpus.py --commerce-repo ../commerce-canon --info-tech-repo ../info-tech-canon`
|
|
from the project root. Historical source assertions are not current definitions.
|
|
|
|
[Reciprocal interface evidence](../docs/evidence/2026-09-06-interface-cards.md)
|
|
records the three published canon cards and explicit upstream import review (G7).
|
|
|
|
[Fleet reference review](reference-sweep.json) records exact historical-reference
|
|
exceptions; [G8 evidence](../docs/evidence/2026-09-06-reference-sweep.md) records
|
|
current source coordinates and service validation.
|