coulomb/security-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
security-canon/infospace/interfaces
History
tegwick a267c98087 Publish the SecurityCanon federation interface card (T04) 
Declares one export surface, sec-authority, carrying the Mode of Authority
vocabulary and its machine-readable catalogs, with InfoTechCanon,
InterfaceCanon, CommerceCanon and the Custodian as peers under CUST-ADR-006.
The card validates against InfoTechCanon's interface-card schema.

Imports are pinned against InfoTechCanon e1f98da0 in imports.json, recording
path and SHA-256 for each of the five sources; all five were verified to match
Git blobs at that commit with the sources unchanged in the review checkout.

Reciprocal navigation runs both ways: this repository's interfaces README links
the peer cards, and InfoTechCanon carries the SecurityCanon boundary review with
its own README link, following the InterfaceCanon precedent.

The prj-canon-federation G7 validator passes, and InfoTechCanon make check
passes with 46 tests and clean validation. The validator pins card paths for
three repositories only, so this card meets the same contract without yet being
registered there; that is prj-canon-federation's change to make and the card
says so.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AUkN13CAqtXWPXuEiEtmJj

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 36656@bnt-lap001
Assistant-Session: 66d6eece-d245-43ca-85e8-68a1b5970a67
2026-09-20 21:50:07 +02:00
..
federation.yaml Publish the SecurityCanon federation interface card (T04) 2026-09-20 21:50:07 +02:00
README.md Publish the SecurityCanon federation interface card (T04) 2026-09-20 21:50:07 +02:00

README.md

Canon federation interface

The interface card publishes this canon's federation boundary under accepted ADR-006.

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.