tegwick
e159fe7a1b
InfoTechCanon re-verified this boundary against its enlarged ownership index under INFO-WP-0027-T04. The original manifest was verified by file hash, which every entry passed; nothing checked that the named concept exists in the named file. Five of twelve did not. Artifact becomes CanonArtifact, which is what Core defines; bare Artifact now resolves to the DevSecOps build artifact, a different concept. Relationship becomes RelationshipDefinition, since the identity model owns Relationship as its actor-linking taxonomy. Ownership moves to the Organization Model, which the kernel map names as its owner. AccessOperations becomes Operation, the upstream name. PrincipalType stops being an import: the identity model does not define it, and it is SecurityCanon's own classification of the imported Principal. Eleven imports remain, no concept is contested, and no semantic disposition changes. 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 |
||
|---|---|---|
| .. | ||
| concept-placement.md | ||
| federation.yaml | ||
| README.md | ||
Canon federation interface
The interface card publishes this canon's federation boundary under accepted ADR-006.
- info-tech-canon interface — shared-concept upstream
- SecurityCanon boundary review — InfoTechCanon-side acceptance of this extension boundary
- interface-canon interface
- commerce-canon interface
- the-custodian interface
SecurityCanon exports one surface, sec-authority: the architecture-layer
Mode of Authority
vocabulary. It imports shared roots from InfoTechCanon and redefines none of
them; the pinned manifest records
each source path and content hash at the declared commit.
Reciprocal navigation does not imply reciprocal semantic imports. InfoTechCanon retains the shared roots, CARING, the access-control model and the identity model; see SEC-ADR-001.
The G7 validator in prj-canon-federation currently pins card paths for
info-tech-canon, commerce-canon and the-custodian. Adding security-canon to
CARD_PATHS is that project's change to make; this card is written to satisfy
the same contract in the meantime.
Concept placement across the two canons — one owning canon and one import direction per shared concept — is recorded in concept-placement.md (SECURITY-DEC-2026-003).