Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Finish ITC-WP-0013 (AttributeValueType under ITC-DATA) and ITC-WP-0014
T02/T03/T05/T06/T07. Capability contract schemas, live-catalog review
CLI, landscape/kernel-map pointers. Sit on this version.
This commit is contained in:
tegwick 2026-08-15 19:42:30 +02:00
parent 7805560a60
commit d453e17952
44 changed files with 1485 additions and 137 deletions

View file

@ -49,6 +49,7 @@ InfoTechCanonDataModel
InfoTechCanonDevSecOpsModel
InfoTechCanonNetworkModel
InfoTechCanonObservabilityModel
InfoTechCanonCapabilityModel
```
Together they form a coherent first-generation semantic substrate for building interoperable information-processing systems.
@ -69,6 +70,7 @@ Data = datasets, schemas, classification, lineage, quality, contrac
DevSecOps = source-to-artifact-to-release-to-deployment delivery flow and evidence.
Network = addressing, topology, routing, policy, reachability, flow, exposure, and state.
Observability = telemetry, signals, logs, metrics, traces, events, alerts, SLOs, and evidence.
Capability = what an information system must be able to do, independently of how.
```
---
@ -444,6 +446,23 @@ Network owns communication and reachability. Observability owns signals and runt
| ObservedIncident | Observability / Task or ITSM reference |
| ObservabilityEvidence | Observability / Governance reference |
## 4.14 Capability Owns Abilities
| Concept Family | Canonical Owner |
|---|---|
| Capability / CapabilityProfile | Capability |
| CapabilityRequirement / CapabilityProvision | Capability |
| CapabilityMaturityLevel | Capability |
| CapabilityResourceClass / CapabilityConsumption | Capability |
| EvidenceBasis on a consumption row | Governance (imported by Capability) |
| Service / Technology that provides a capability | Landscape |
| Intended quality target | Capability (requirement) |
| Observed SLO | Landscape / Observability |
ITC-CAP sits between product need and landscape implementation. Capability
ids are durable interfaces (CAP-R5). Landscape §11.4 defers abstract
ability here.
---
# 5. CARING Fit in InfoTechCanon