coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
info-tech-canon/infospace
History
tegwick 209bb5a9c4
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details
Bind the CARING Scope dimension to one definition (R-1) 
The SecurityCanon boundary review recorded a residual: CARING and ITC-ACCESS
hold two definitions of Scope, with ITC-ACCESS named owner. Reading the corpus
corrects both halves. ITC-IDENT section 2.10 owns Scope as the general boundary
within which identifiers, meanings, relationships, accounts, policies or
lifecycle states are valid, and ITC-ACCESS section 11.8 ResourceScope already
declares itself a refinement of that general identity Scope rather than a
competing definition.

The second use the residual was reaching for is CARING section 21, which
presented a dimension named Scope with a ladder from Ecosystem to Field without
saying what the dimension ranges over. It now states that it ranges over
ITC-IDENT Scope instances, that the ladder is the canonical value set rather
than a second definition, and that ResourceScope refines the same concept for
resource boundaries.

No concept is renamed, moved or removed and no ladder value changes, so the
corpus is unchanged in shape; make check passes with 46 tests, clean validation
and a passing small-saas profile. The correction is carried back to the
SecurityCanon placement record and imports.json, where Scope now imports from
the identity model.

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 22:42:28 +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 Bind the CARING Scope dimension to one definition (R-1) 2026-09-20 22:42:28 +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

README.md

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.