coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Accept the SecurityCanon extension boundary
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
SecurityCanon publishes an architecture-layer vocabulary for authority
relationships, the Mode of Authority, and references shared InfoTechCanon
concepts. This records the InfoTechCanon-side acceptance of that boundary and
adds reciprocal navigation from the federation interface README.

The accepted dispositions keep the layers apart. Mode of Authority describes the
relationship in which authority is exercised; CARING analyses how an
access-control implementation is composed. Auth Mode is orthogonal to access
operation and to CARING's Canonical Role and Plane, so the Operator role and the
OPERATE mode stay distinct concepts and neither is renamed. SecurityCanon does
not reuse Actor or Subject, which ITC-ACCESS owns and binds as "Subject is the
access-control view of an actor"; it renamed its on-behalf-of dimension to
AuthorityContext instead, so no change is required here.

Verified at security-canon b1fa25eb: all five pinned manifest hashes match Git
blobs at this commit and the sources are unchanged in the review checkout, and
none of the seven concepts SecurityCanon declares appears in any InfoTechCanon
owned_concepts declaration, so the boundary introduces no ownership conflict.

No concept is transferred and nothing is removed, so the corpus is unchanged.
Generated indexes and the repository tree are refreshed for the added file;
make check passes with 46 tests, clean validation and a passing small-saas
profile. This is an agent review, not human sign-off, and it records no consumer
adoption or conformance claim.

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
This commit is contained in:
tegwick 2026-09-20 21:49:47 +02:00
parent e1f98da015
commit d61ec8adf6
4 changed files with 81 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
infospace/interfaces/README.md
View file

@ -7,6 +7,9 @@ under [accepted ADR-006](../../../the-custodian/canon/architecture/adr-006-canon
- [the-custodian interface](../../../the-custodian/canon/interfaces/federation.yaml)
- [InterfaceCanon boundary review](interface-canon-boundary.md) — scoped acceptance
of the draft 0.1.1 extension boundary, with pinned sources and review evidence.
- [SecurityCanon interface](../../../security-canon/infospace/interfaces/federation.yaml)
- [SecurityCanon boundary review](security-canon-boundary.md) — 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