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

Record complete corpus provenance distribution and G6 evidence

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
tegwick 2026-09-06 00:44:57 +02:00
parent 3005a28b0a
commit 1d02c83051
6 changed files with 3665 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

52
docs/evidence/2026-09-06-corpus-distribution.md Normal file
View file

@ -0,0 +1,52 @@
# Corpus distribution — 2026-09-06
CFED-WP-0001-T07 is implemented by INFO-WP-0024 and COMMERCE-WP-0003.
The 45-file research/terminology/scenario corpus is pinned at CommerceCanon
commit `8a07292dd78d094151f165d3ac1dfc7512114308`. Original files remain unchanged.
Destination assimilation workspaces contain 69 byte-identical snapshots:
45 in InfoTechCanon (technical concepts and imported technical context from the
commercial research) and 24 in CommerceCanon (commercial research, shared B2B
provisioning context, indexes, terminology and scenarios). Per-model reading
indexes identify the destination interest. Shared terminology rows, conflict
sections and scenarios are partitioned into 153 exact fragments with line ranges
and hashes. Full source context is retained beside the views.
The machine-readable [distribution ledger](../../ledger/corpus-distribution.json)
records every source, digest, model interest, destination path and fragment.
Each native workspace has its scoped manifest, schema-valid assimilation record,
source summary, reused concept extraction/mappings, comparison matrix, proposed
changes (none), open-question status and decision rationale. Disposition is
observe: this distributes completed research under accepted ADR-006 and the
user-authorized T07, without adopting new domain definitions. No source content
was silently revised, re-researched or claimed current.
Historical Family-as-collective, source/assertion conflations, product terminology
and obsolete review queues remain visible but are explicitly superseded by the
accepted ownership and current draft models. Old scenario satisfiability claims
are not current conformance results. T08/T09/T10 retain live interface, fleet and
residual work; no speculative Family model work is created.
Reproduce (Python 3, PyYAML and jsonschema):
```bash
python3 tools/validate_corpus.py --commerce-repo ../commerce-canon --info-tech-repo ../info-tech-canon
python3 tools/validate_ownership.py --source-repo ../commerce-canon
```
G6 check: 45 sources, 69 snapshots, 153 exact fragments, 479 workspace links;
zero unrouted sources or changed originals. InfoTechCanon adds one observed
assimilation retrieval artifact and remains at 14 models; its metadata patch
release includes a change record. Final checks and publication receipts follow.
Final verification: InfoTechCanon **46 tests pass**, generated consistency, canon
and small-saas profile checks pass. Published InfoTechCanon commit `372f671`;
CommerceCanon implementation `8a89a68`, published/reconciled commit
`bc67e1f25b140ecb60d1439de984f8361acabc32` (primary/railiance01, matching
expected/derived commits, no refusals or retirements).
Native workplan UUIDs: INFO-WP-0024 `3bea30f6-8640-5c16-b782-8258babdba35`,
COMMERCE-WP-0003 `3010a646-4e26-56bb-9fd2-327bb59ebea5`. Decision
`5afcdb1c-10a9-4a84-b769-92fa025c91b8` records the observe/routing rationale.
Required synchronization passed, with existing classification/prefix advisories.
Progress logged to both native workplans and the project. Project: 10/13 done.