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

Split capability navigation domains; canon 0.2.1 (OQ-2 resolved)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Security & Governance splits into `security` (secrets, keys, policy,
vulnerability) and `governance` (evidence, lifecycle). Every capability id
is unchanged — domains are navigation_only, so this is a table-of-contents
change, not a concept change.

- capabilities.yaml: 41 capabilities across 9 domains
- ITC-CAP §8 catalog table and promotion gate updated
- OQ-2 closed; decision record added to ASSIMILATION.md
- canon 0.2.0 -> 0.2.1 (patch) + CHANGELOG entry
- ITC-WP-0014 T01 done, workplan active

make validate: ok. make test: 22 passed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-15 02:43:55 +02:00
parent b92359845b
commit 680ed8b4b1
8 changed files with 101 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

10
infospace/assimilation/it-capability-canon/open-questions.md
View file

@ -6,19 +6,17 @@ Resolved for now as a **model** (broad domain structure). If capability contract
later grow enforcement rules and conformance levels for consumers, part of it may
split into a standard. **Review trigger:** first consumer conformance request.
## OQ-2 — The `governance.*` prefix inside the Security & Governance domain
## OQ-2 — The `governance.*` prefix inside the Security & Governance domain — **RESOLVED 2026-08-15 (canon 0.2.1)**
Six capabilities sit in navigation domain `security` but two use a `governance.`
Six capabilities sat in navigation domain `security` but two used a `governance.`
ID prefix (`governance.evidence`, `governance.lifecycle`). Options:
1. keep as-is — IDs are durable interfaces and already drafted;
2. renumber to `security.*` — consistent prefixes, but breaks IDs;
3. split the navigation domain into `security` and `governance`.
Capability IDs are durable interfaces, so this must be settled **before**
promotion beyond `proposed`. Preference: option 3 — it preserves every ID and
removes the inconsistency. **Owner:** canon owner. **Blocks:** promotion to
`draft`/`release-candidate`.
**Decision: option 3.** See the OQ-2 decision record in
[`ASSIMILATION.md`](ASSIMILATION.md). No longer blocks promotion.
## OQ-3 — Should the intended/declared/applied/observed/assessed state qualifier be canon-wide?