Canon 0.5.0: uses_provisions so P stays purchased platform

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.

workplans/ADHOC-2026-08-15.md

@@ -1,7 +1,7 @@
 ---
 id: ADHOC-2026-08-15
 type: workplan
-title: "Ad hoc: consumer feedback directory"
+title: "Ad hoc: feedback directory and provision relationships"
 domain: infotech
 topic_slug: canon
 repo: info-tech-canon
@@ -13,6 +13,7 @@ owner: grok
 spec_refs:
   - feedback/README.md
   - demand/CapabilityProvisionEconomics.md
+  - demand/ProvisionRelationships.md
 state_hub_workstream_id: "dd403bf7-b84d-49af-b914-fb5b0bd1b88a"
 ---
 
@@ -22,7 +23,9 @@ state_hub_workstream_id: "dd403bf7-b84d-49af-b914-fb5b0bd1b88a"
 
 Give the canon a durable place to collect consumer reports on whether
 existing concepts hit, friction, gap, or are drop candidates — without
-collapsing that evidence into `demand/` or `incoming/`.
+collapsing that evidence into `demand/` or `incoming/`. Land the
+provision-to-provision relationship the resource-control restatement
+needed, so class `P` does not become a dumping ground again.
 
 ## Tasks
 
@@ -51,3 +54,16 @@ state_hub_task_id: "95599215-b461-4893-8736-d249030bef34"
 Write `feedback/2026-08-15-resource-control-capability-provision.md` from the
 2026-08-15 backup-cycle mapping. Hits stay here; the three defects remain
 `demand/CapabilityProvisionEconomics.md`.
+
+### T03 — Provision-to-provision relationships
+
+```task
+id: ADHOC-2026-08-15-T03
+status: done
+priority: high
+```
+
+Accept `demand/ProvisionRelationships.md`. Add `uses_provisions` on
+`CapabilityProvision` with `depends_on` / `may_use` only (CAP-R11). Add
+`security.secrets` to `data.backup` `may_use`. Do not cap maturity across
+the dependency. Canon 0.5.0 / ITC-CAP 0.4.0.

workplans/ITC-WP-0014-capability-model-consolidation.md

@@ -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
 

workplans/index.yaml

@@ -209,7 +209,7 @@ workplans:
       - capability requirement/provision validation surface
 
   - id: ADHOC-2026-08-15
-    title: "Ad hoc: consumer feedback directory"
+    title: "Ad hoc: feedback directory and provision relationships"
     status: finished
     priority: low
     path: workplans/ADHOC-2026-08-15.md
@@ -217,6 +217,7 @@ workplans:
     produces:
       - feedback/
       - first consumer utility report (resource-control / ITC-CAP)
+      - uses_provisions on CapabilityProvision (CAP-R11)
 
   - id: ITC-WP-0015
     title: Evidence Basis catalog (Governance extension)