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

11
infospace/models/capability/InfoTechCanonCapabilityModel.md
View file

@ -345,7 +345,7 @@ ConsumerPurpose --requires--> Capability <--provides-- Service
# 8. Catalog
The baseline is **41 capabilities across 8 navigation domains**, held in
The baseline is **41 capabilities across 9 navigation domains**, held in
`models/capability/capabilities.yaml`.
| Domain | Count | Capability ids |
@ -355,7 +355,8 @@ The baseline is **41 capabilities across 8 navigation domains**, held in
| Integration & Communication | 5 | `integration.api`, `integration.messaging`, `integration.exchange`, `integration.notification`, `integration.traffic` |
| Runtime & Automation | 5 | `runtime.execution`, `runtime.configuration`, `runtime.scheduling`, `runtime.workflow`, `runtime.deployment` |
| Operations & Assurance | 5 | `operations.observability`, `operations.alerting`, `operations.audit`, `operations.recovery`, `operations.continuity` |
| Security & Governance | 6 | `security.secrets`, `security.keys`, `security.policy`, `security.vulnerability`, `governance.evidence`, `governance.lifecycle` |
| Security | 4 | `security.secrets`, `security.keys`, `security.policy`, `security.vulnerability` |
| Governance | 2 | `governance.evidence`, `governance.lifecycle` |
| Commerce | 4 | `commerce.metering`, `commerce.billing`, `commerce.payment`, `commerce.entitlement` |
| Intelligence | 5 | `intelligence.generation`, `intelligence.extraction`, `intelligence.embedding`, `intelligence.retrieval`, `intelligence.reasoning` |
@ -386,9 +387,9 @@ model. This is accepted at `proposed` status and tracked as OQ-5.
This model enters the canon at status `proposed`. Promotion requires:
1. resolution of assimilation open question **OQ-2** (the `governance.*` id prefix
inside the Security & Governance domain) — blocking, because ids are durable
interfaces;
1. ~~resolution of assimilation open question **OQ-2**~~ — **resolved in canon
0.2.1**: the Security & Governance navigation domain was split into `security`
and `governance`, aligning every id with its domain and changing no id;
2. publication of `capability.schema.yaml` validating contracts;
3. at least one canon Profile expressing a real capability requirement set with
evidence;