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).

canon.yaml

@@ -1,7 +1,7 @@
 repository: info-tech-canon
 title: InfoTechCanon
 status: service-baseline
-version: 0.3.0
+version: 0.4.0
 description: >
   An evolving, markdown-first canon for building interoperable, adaptable,
   and extensible information-processing systems.
@@ -93,7 +93,7 @@ models:
     title: InfoTechCanonCapabilityModel
     path: infospace/models/capability/InfoTechCanonCapabilityModel.md
     status: proposed
-    version: 0.2.0
+    version: 0.3.0
     catalog: infospace/models/capability/capabilities.yaml
     provenance:
       assimilation: assimilation/it-capability-canon
@@ -149,6 +149,7 @@ workplans:
     - ITC-WP-0012
     - ITC-WP-0013
     - ITC-WP-0014
+    - ITC-WP-0015
 
 feedback:
   path: feedback/
@@ -180,5 +181,4 @@ next_actions:
   - implement ITC-WP-0003 validation and generated views
   - implement ITC-WP-0004 small-saas profile proof
   - explore ITC-WP-0006 PURPOSES model extension
-  - publish ITC-WP-0014 T02 capability.schema.yaml encoding ITC-CAP 0.2.0 (next ITC-CAP promotion gate)
-  - accept resource-control restatement of the backup provision against ITC-CAP 0.2.0 (demand criterion 6 / promotion requirement 3)
+  - publish ITC-WP-0014 T02 capability.schema.yaml encoding ITC-CAP 0.3.0 (next ITC-CAP promotion gate; §10.3 met by resource-control join)