info-tech-canon/infospace
tegwick d61ec8adf6
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Accept the SecurityCanon extension boundary
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
2026-09-20 21:49:47 +02:00
..
agent Publish reciprocal canon federation interface 2026-09-06 01:00:12 +02:00
artifacts Publish reciprocal canon federation interface 2026-09-06 01:00:12 +02:00
assimilation Distribute frozen federation corpus by concept destination 2026-09-06 00:44:37 +02:00
concepts Register limited Family concept-area seed 2026-09-06 00:26:29 +02:00
evaluations ITC-WP-0012: integrate Repository Layout Standard 2026-06-13 14:25:54 +02:00
examples Add purpose and demand model extension 2026-05-23 04:59:16 +02:00
indexes Accept the SecurityCanon extension boundary 2026-09-20 21:49:47 +02:00
interfaces Accept the SecurityCanon extension boundary 2026-09-20 21:49:47 +02:00
kernel Register limited Family concept-area seed 2026-09-06 00:26:29 +02:00
mappings Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review 2026-08-15 19:42:30 +02:00
models Extend organization model with distinct social collectives 2026-09-05 22:31:15 +02:00
patterns feat(ITC-WP-0017): establish AgenticDrivesFunctional pattern 2026-08-22 18:54:01 +02:00
profiles Implement canon conformance and maintenance optimizations 2026-09-05 00:50:09 +02:00
reports Add small SaaS profile proof 2026-05-23 04:26:28 +02:00
schemas Implement canon conformance and maintenance optimizations 2026-09-05 00:50:09 +02:00
standards Introduce shared evidence model and governance imports 2026-09-05 21:16:29 +02:00
validation Introduce identity model and reconcile upstream imports 2026-09-05 22:11:46 +02:00
views Accept the SecurityCanon extension boundary 2026-09-20 21:49:47 +02:00
infospace.yaml Introduce identity model and reconcile upstream imports 2026-09-05 22:11:46 +02:00
README.md Implement infospace scaffold and service baseline 2026-05-23 03:12:02 +02:00

InfoTechCanon Infospace

This directory is the single concrete infospace implemented by this repository. The repository root remains the service, governance, and workplan shell.

The current placement pass copies the seed documents into canonical kernel/, models/, and standards/ paths while keeping seeds/ as provenance until the scaffold migration is reviewed.