coulomb/security-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
security-canon/infospace/interfaces
History
tegwick 7e2de19dc6 Close the section 32 generalisation as accepted upstream 
InfoTechCanon reviewed the demand signal separately and accepted option B as
INFO-DEC-2026-001: the CARING section 32 role set now applies wherever a
subject's access is exercised through another party, rather than to non-human
subjects only. CARING moves to canon version 0.4.0-RC2-itc2.

The change is additive and no SecurityCanon declaration moves. The blank cell in
the mapping table stands: InfoTechCanon's access-control model still has no
on-behalf-of relation.

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
2026-09-20 23:54:12 +02:00
..
concept-placement.md Close the section 32 generalisation as accepted upstream 2026-09-20 23:54:12 +02:00
federation.yaml Publish the SecurityCanon federation interface card (T04) 2026-09-20 21:50:07 +02:00
README.md Decide concept placement across the canon boundary (T02) 2026-09-20 22:33:46 +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.

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).