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.

feedback/2026-08-15-resource-control-cap-restatement.md

@@ -18,6 +18,7 @@ spawned_demand:
   - demand/EvidenceBasis.md
 spawned_workplan:
   - ITC-WP-0015
+  - ADHOC-2026-08-15
 ---
 
 # Feedback: ITC-CAP 0.2.0 restatement of platform-audit-storage
@@ -116,5 +117,7 @@ None.
   resource-control.
 - Evidence-basis accepted as `demand/EvidenceBasis.md` and published as
   ITC-GOV `EvidenceBasis` / CAP-R10 (ITC-WP-0015, canon 0.4.0).
-- Provision-to-provision dependency remains a note, not a field. Do not
-  invent it until a demand or T02 needs it.
+- Provision-to-provision dependency accepted as
+  `demand/ProvisionRelationships.md` and published as `uses_provisions`
+  / CAP-R11 (ADHOC-2026-08-15 T03, canon 0.5.0). Canon spelling is
+  `may_use`, not `uses`. Maturity is not capped across the dependency.

feedback/index.yaml

@@ -75,3 +75,4 @@ reports:
     related_workplan:
       - ITC-WP-0014
       - ITC-WP-0015
+      - ADHOC-2026-08-15