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

Canon 0.5.0: uses_provisions so P stays purchased platform
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
A provision can name which other provision satisfies a catalog
dependency. Relation vocabulary is depends_on / may_use only.
Quoted sits below the invoiced/measured peer pair for propagation.
This commit is contained in:
tegwick 2026-08-15 19:23:44 +02:00
parent 40accbbf3d
commit 0b28ec570e
12 changed files with 156 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/ITC-WP-0014-capability-model-consolidation.md
View file

@ -70,11 +70,12 @@ state_hub_task_id: "1ed8d07a-34ee-4ad4-8e4a-03a513c14836"
Add the capability contract schema under `infospace/schemas/`, register it in
`infospace/infospace.yaml`, and validate `capabilities.yaml` against it.
Encode ITC-CAP 0.3.0: no `typical_resource_classes` on contracts; resource
Encode ITC-CAP 0.4.0: no `typical_resource_classes` on contracts; resource
classes carry `native_unit`, `supply`, and `capacity_behaviour`; consumption
rows require EvidenceBasis (CAP-R10); requirement and provision record
shapes live in the model prose until a companion requirement/provision
schema is justified. §10.3 is already met by the resource-control join.
rows require EvidenceBasis (CAP-R10); provisions may declare
`uses_provisions` (CAP-R11); requirement and provision record shapes live
in the model prose until a companion requirement/provision schema is
justified. §10.3 is already met by the resource-control join.
### T03 — Formal mapping artifacts for each anchor