tegwick
e1a6314131
import-review takes any partner manifest and returns, per concept, whether the name resolves in the ownership index and to which artifact, and per entry whether the pinned SHA-256 matches the blob at the declared source commit. Both run in one pass so neither can be recorded without the other, which is the failure this workplan exists to prevent. It exits non-zero on a finding, reads JSON or YAML, needs no partner checkout, and carries its own limit: resolution proves a name exists and names one owner, nothing more. Accepted manifests are registered under infospace/interfaces/manifests/ as provenance-preserving copies owned by the partner, with the partner revision and retrieval date recorded. Editing a copy to make a check pass is forbidden in the file itself. Validation re-resolves them and reports drift as federation_import_drift, a warning naming the partner rather than an error, because a stale partner pin is not this repository's file to fix. The review kit gains an extension-boundary-review template requiring hash count, resolution count and conflict count as three separate lines, and an operating rule saying one is never evidence of another. Both boundary files carry the standing-check result. Verified live: security-canon resolves 11 of 11, interface-canon 23 of 25 with the two known Interface and Endpoint pins. make check passes with 58 tests, clean validation and those two warnings. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 3588@bnt-lap001 Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da |
||
|---|---|---|
| .. | ||
| manifests | ||
| federation.yaml | ||
| interface-canon-boundary.md | ||
| README.md | ||
| security-canon-boundary.md | ||
Canon federation interface
The interface card publishes this canon's federation boundary under accepted ADR-006.
- commerce-canon interface
- the-custodian interface
- InterfaceCanon boundary review — scoped acceptance of the draft 0.1.1 extension boundary, with pinned sources and review evidence.
- SecurityCanon interface
- SecurityCanon boundary review — scoped acceptance of the draft 0.2.0 architecture-layer authority vocabulary, with pinned sources.
Each export names its source document and current maturity. Imports identify actual dependencies; reciprocal navigation does not imply reciprocal semantic imports. Custodian supplies ecosystem governance, InfoTechCanon information- processing semantics, and CommerceCanon commercial semantics. Family remains seeded, not authored. The card scope is this federation, not every repo artifact.
Reproduce G7 from the adjacent project checkout:
python3 tools/validate_interfaces.py --workspace ..