Canon 0.3.0: capability provision economics (ITC-CAP 0.2.0)

Accept resource-control demand: move resource classes onto provisions,
let requirements carry targets and constraints, add human-effort class H
with native-unit consumption. Model stays proposed.

CHANGELOG.md

@@ -15,6 +15,52 @@ semantics.
 
 ---
 
+## 0.3.0 — 2026-08-15
+
+### Changed — Capability provision economics (requirement targets, native-unit consumption, class `H`)
+
+**Change.** The still-proposed Capability Model (`ITC-CAP`) moves from `0.1.0` to
+`0.2.0` in response to consumer demand `demand/CapabilityProvisionEconomics.md`
+(resource-control, a completed procurement-to-control cycle).
+
+- **Contracts** no longer declare `typical_resource_classes`. Resource
+  consumption attaches to a provision only (new CAP-R8), matching the rule §4.11
+  already stated.
+- **CapabilityRequirement** may select a profile, assert intended quality
+  targets against the capability's declared dimensions, and state placement
+  constraints with a closed predicate set (`not_in`, `in`, `equals`, `lte`,
+  `gte`). Measurement remains with ITC-LAND / ITC-OBS (new CAP-R9).
+- **Resource classes** gain `H` (Human Effort, native unit `hour`, default
+  supply `internal`, default capacity `constrained`). `P` is narrowed to
+  purchased platform and enabling services and no longer absorbs human time.
+  `I` is recharacterised as the elastic purchased substitute for `H`, native
+  unit `token`. Every class declares `native_unit`, `supply`, and
+  `capacity_behaviour`; a consumption record may override the last two.
+- **CapabilityConsumption** is a new owned concept: one native-unit row on a
+  provision. Unknown is recorded as `unknown`, never as zero. Currency is not a
+  class. No `substitutes_for` relation and no H↔I exchange rate.
+- Quality dimension `intelligence_intensity` is declared on all five
+  `intelligence.*` capabilities.
+
+**Rationale.** The catalog, evidence hooks, and D-scale independently matched
+the consumer's backup evidence. The three defects were cheapest to fix before
+`capability.schema.yaml` freezes the contract and before the consumer restates
+the real provision. Splitting ITC-CAP into demand-side and supply-side canons
+was considered and rejected: both sides agree about what exists.
+
+**Breaking:** no capability id, anchor, profile (except the new dimension on
+`intelligence.*`), evidence hook, or relationship type changed.
+`typical_resource_classes` is removed from the catalog; it was never a durable
+interface.
+
+**Records.** Decision record in
+`assimilation/it-capability-canon/ASSIMILATION.md`; OQ-5 notes a partial fire;
+`ITC-WP-0014` T08–T10 done.
+
+**Validation.** `make validate` 0 errors / 0 warnings; `make test` 22 passed.
+
+---
+
 ## 0.2.1 — 2026-08-15
 
 ### Changed — Capability navigation domains split (OQ-2 resolved)