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

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

@@ -70,10 +70,11 @@ 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.2.0: no `typical_resource_classes` on contracts; resource
-classes carry `native_unit`, `supply`, and `capacity_behaviour`; requirement
-and provision record shapes live in the model prose until a companion
-requirement/provision schema is justified.
+Encode ITC-CAP 0.3.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.
 
 ### T03 — Formal mapping artifacts for each anchor
 
@@ -99,8 +100,9 @@ state_hub_task_id: "182e0ad5-5fb9-4d50-9576-b9f5fdff91d3"
 ```
 
 Express a real `CapabilityRequirement` set with provisions and evidence in the
-small-saas profile (coordinate with ITC-WP-0004). This is the practical proof
-required for promotion.
+small-saas profile (coordinate with ITC-WP-0004). Useful in-repo illustration.
+**No longer the promotion gate** — §10.3 now accepts a consumer record that
+validates against the live catalog (T11).
 
 ### T05 — Landscape and kernel-map revision
 
@@ -136,12 +138,13 @@ source §18. Covers OQ-6.
 id: ITC-WP-0014-T07
 status: todo
 priority: medium
-depends_on: [T01, T02, T03, T04]
+depends_on: [T01, T02, T03, T11]
 state_hub_task_id: "455690e3-c39a-4926-a13b-a179b134b2a4"
 ```
 
 Promote the model from `proposed` to `draft` or `release-candidate`, bump the
-canon version, and write the `CHANGELOG.md` entry.
+canon version, and write the `CHANGELOG.md` entry. T04 (small-saas illustration)
+is no longer a promotion dependency.
 
 ### T08 — Finding A: move resource-class declaration off the contract
 
@@ -187,6 +190,22 @@ supply/capacity defaults, record consumption in native units, add
 **Done 2026-08-15 (canon 0.3.0 / ITC-CAP 0.2.0).** Landed here rather than as a
 new workplan: no LAND or commerce owning-model change was required.
 
+### T11 — Joinable consumer proof for §10.3
+
+```task
+id: ITC-WP-0014-T11
+status: done
+priority: high
+```
+
+Revise §10.3 so a consumer record that validates against the live catalog
+and is cited from `feedback/` counts as the promotion proof. Record
+resource-control `data/capability/platform-audit-storage.json` (commit
+`13c2b82`) as that proof.
+
+**Done 2026-08-15 (canon 0.4.0 / ITC-CAP 0.3.0).** Operational facts stay
+in the consumer repo.
+
 ## Out of scope
 
 - New domain models for `commerce.*` / `intelligence.*` (OQ-5) — the 2026-08-15

workplans/ITC-WP-0015-evidence-basis.md

@@ -0,0 +1,81 @@
+---
+id: ITC-WP-0015
+type: workplan
+title: "Evidence Basis catalog (Governance extension)"
+domain: infotech
+topic_slug: canon
+repo: info-tech-canon
+status: finished
+priority: high
+created: "2026-08-15"
+updated: "2026-08-15"
+owner: grok
+depends_on_workplans:
+  - ITC-WP-0014
+spec_refs:
+  - demand/EvidenceBasis.md
+  - infospace/models/governance/InfoTechCanonGovernanceModel.md
+  - infospace/models/governance/evidence-basis.yaml
+  - infospace/models/capability/InfoTechCanonCapabilityModel.md
+---
+
+# ITC-WP-0015 — Evidence Basis
+
+## Goal
+
+Give quantities a closed, ordered scale for *how they were obtained*, owned
+by ITC-GOV and imported by ITC-CAP consumption, so assumed hours and
+measured gigabytes cannot sit in one list as if they were the same kind of
+knowledge.
+
+## Intent
+
+resource-control published the vocabulary and showed it grading their own
+provider comparison `indicative`. They asked whether we wanted it as a
+demand. We do. Ownership is GOV Evidence, not a CAP-only dialect, because
+the same scale is needed on actuals and thresholds.
+
+## Tasks
+
+### T01 — Demand intake
+
+```task
+id: ITC-WP-0015-T01
+status: done
+priority: high
+```
+
+Steward-file `demand/EvidenceBasis.md` from the consumer's published
+`docs/evidence-basis.md` and `tools/basis.py`. Do not copy the
+implementation.
+
+### T02 — Catalog and GOV section
+
+```task
+id: ITC-WP-0015-T02
+status: done
+priority: high
+depends_on: [T01]
+```
+
+Add `infospace/models/governance/evidence-basis.yaml` as the closed
+vocabulary and §11.34a `EvidenceBasis` to the Governance Model.
+
+### T03 — Import on CapabilityConsumption
+
+```task
+id: ITC-WP-0015-T03
+status: done
+priority: high
+depends_on: [T02]
+```
+
+CAP-R10: a consumption row MUST declare `basis`. Unknown carries no
+quantity. ITC-CAP 0.3.0 / canon 0.4.0.
+
+## Out of scope
+
+- Ledger or invoiced-fact origination (fin-hub).
+- Canon-wide state qualifiers (OQ-3).
+- Retrofitting resource-control actuals and thresholds — that is their work
+  against this catalog.

workplans/index.yaml

@@ -217,3 +217,16 @@ workplans:
     produces:
       - feedback/
       - first consumer utility report (resource-control / ITC-CAP)
+
+  - id: ITC-WP-0015
+    title: Evidence Basis catalog (Governance extension)
+    status: finished
+    priority: high
+    path: workplans/ITC-WP-0015-evidence-basis.md
+    depends_on:
+      - ITC-WP-0014
+    produces:
+      - demand/EvidenceBasis.md
+      - models/governance/evidence-basis.yaml
+      - EvidenceBasis section in ITC-GOV
+      - CAP-R10 on CapabilityConsumption