Canon 0.4.0: joinable consumer proof and EvidenceBasis

§10.3 now accepts a consumer record that validates against the live
catalog; resource-control's backup restatement is that proof. ITC-GOV
gains EvidenceBasis in tiers (invoiced and measured are peers) and
ITC-CAP requires it on every consumption row (CAP-R10).

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

@@ -1,7 +1,7 @@
 ---
 id: feedback/2026-08-15-resource-control-cap-restatement
 type: consumer-feedback
-status: reviewed
+status: acted-on
 date: "2026-08-15"
 consumer: resource-control
 consumer_domain: financials
@@ -10,10 +10,14 @@ artifacts:
   - model/capability
 related_demand:
   - demand/CapabilityProvisionEconomics.md
+  - demand/EvidenceBasis.md
 related_workplan:
   - ITC-WP-0014
-spawned_demand: []
-spawned_workplan: []
+  - ITC-WP-0015
+spawned_demand:
+  - demand/EvidenceBasis.md
+spawned_workplan:
+  - ITC-WP-0015
 ---
 
 # Feedback: ITC-CAP 0.2.0 restatement of platform-audit-storage
@@ -106,16 +110,11 @@ None.
 
 ## Steward notes
 
-- Status `reviewed`. Demand criterion 6 is met *in the consumer repo*.
-  ITC-CAP §10 promotion requirement 3 still asks for a *canon Profile*.
-  This record is stronger evidence than a worked example and should count
-  toward promotion; whether that means revising §10.3 or adding a thin
-  in-repo example that cites the join (not the operational facts) is an
-  open steward decision.
-- Do not copy `platform-audit-storage.json` into this repository. The
-  catalog stays here; the provisioned facts stay there; the join is the id.
-- Evidence-basis: do not adopt from this report alone. Invite the demand
-  with the closed vocabulary and propagation rule, and decide ownership
-  (GOV Evidence vs CAP-only) when it arrives.
-- Provision dependency: note as pressure on ITC-CAP / T02 schema. Do not
-  invent the field until a demand or T02 needs it.
+- Status `acted-on`. Demand criterion 6 is met in the consumer repo.
+  ITC-CAP §10.3 was revised in canon 0.4.0: this record is the joinable
+  promotion proof (ITC-WP-0014 T11). Operational facts stay in
+  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.

feedback/index.yaml

@@ -47,8 +47,9 @@ reports:
     date: "2026-08-15"
     consumer: resource-control
     consumer_domain: financials
-    status: reviewed
+    status: acted-on
     canon_version: "0.3.0"
+    spawned_canon_version: "0.4.0"
     artifacts:
       - model/capability
     hits:
@@ -70,5 +71,7 @@ reports:
     drop_candidates: []
     related_demand:
       - demand/CapabilityProvisionEconomics.md
+      - demand/EvidenceBasis.md
     related_workplan:
       - ITC-WP-0014
+      - ITC-WP-0015