tegwick
55a0134b94
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
2.5 KiB
Repository layout and conformance
The foundation targets core documentation conformance to
InfoTechCanonRepositoryLayoutStandard
itc-repo-layout:RepositoryLayoutStandard, 0.1.0-RC1 (RC1-seed), reviewed at
InfoTechCanon commit b081d39da1353201f879ee6832d4e3e52b791c73.
That standard governs documentation placement; its section 9 does not prescribe
canon domain-content layout. The kernel/models/standards tree follows the
federation T04 requirement and InfoTechCanon's current canon.yaml layout family.
| Requirement | Current evidence |
|---|---|
| Minimal: repository purpose and boundary | INTENT.md and SCOPE.md |
| Core: raw demand distinct from implementation | demand/README.md and workplans/ |
| Core: current stakeholder documentation | docs/README.md and this assessment |
| Canon registry and ownership boundary | canon.yaml and infospace/kernel/CommerceCanonCore.md |
| Canon extension locations | infospace/{models,standards,assimilation,mappings,concepts,profiles,patterns,validation}/README.md |
Canon artifacts live under infospace/. Root assimilation/, mappings/, profiles/ are navigation entry points to that single tree, satisfying the project goal's root discovery locations without duplicating content. Legacy canon/ and model/ remain migration inputs. The counterparty model is registered as draft; the standards registry remains empty.
Full documentation conformance is not claimed: research/history retain legacy names, and spec/, wiki/, issues/ are not established. Finished IDENTITY-WP files remain unchanged in workplans/ as required by the accepted migration provenance rule, rather than being moved to history/. T07 owns source distribution. This assessment does not claim stable model promotion, provenance transfers, or interface card completion.
Validation
Parse canon.yaml as YAML and check that each registered artifact exists and its frontmatter ID/status matches the registry; check that the core documentation files and all nine infospace directories exist. Verify relative Markdown links in the new scaffold against a sibling federation/InfoTechCanon checkout. Compare legacy source and finished-plan SHA-256 hashes with the pre-scaffold snapshot. Run the federation ownership validator against this repository and git diff --check. The project records the results under docs/evidence/; the native COMMERCE-WP-0001 links that evidence and the live migration tasks.