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.

infospace/models/capability/InfoTechCanonCapabilityModel.md

@@ -7,7 +7,7 @@ standard_family: InfoTechCanon
 repository_context: info-tech-canon
 recommended_path: models/capability/InfoTechCanonCapabilityModel.md
 status: proposed
-version: 0.1.0
+version: 0.2.0
 source_version: "0.1"
 source_body: Information Technology Capability Canon (ITCC)
 source_file: infospace/assimilation/it-capability-canon/source/ITCapabilityCanonV0.1.md
@@ -45,16 +45,17 @@ owned_concepts:
   - CapabilityQualityDimension
   - CapabilityEvidenceHook
   - CapabilityResourceClass
+  - CapabilityConsumption
   - CapabilityInclusionRule
 created_at: 2026-08-14
-updated_at: 2026-08-14
+updated_at: 2026-08-15
 ---
 
 # InfoTechCanon Capability Model
 
 **Short Name:** `ITC-CAP`
 **Document Status:** Proposed (assimilated, not yet promoted)
-**Version:** 0.1.0
+**Version:** 0.2.0
 **Document Type:** InfoTechCanon Domain Model
 **Machine-readable catalog:** `models/capability/capabilities.yaml`
 **Provenance:** adapted from ITCC v0.1 — see `assimilation/it-capability-canon`
@@ -88,7 +89,8 @@ Service / provider              ← ITC-LAND
 Technology                      ← ITC-LAND
         │ consumes
         ▼
-Resource classes → cost         ← classification owned here
+Resource classes → native units ← classification owned here
+                                 (currency overlay is not owned here)
 ```
 
 ---
@@ -102,7 +104,9 @@ Resource classes → cost         ← classification owned here
 - capability-to-capability and landscape-to-capability relationships;
 - the provision of a capability by a provider in a context;
 - the maturity scale that applies to a provision;
-- the resource classes used to attribute cost to a provision;
+- intended quality targets and placement constraints on a requirement;
+- the resource classes used to classify consumption of a provision;
+- consumption records in each class's native unit;
 - admission rules governing what may become a canonical capability;
 - the canonical capability baseline held in `capabilities.yaml`.
 
@@ -115,7 +119,11 @@ Resource classes → cost         ← classification owned here
 - delivery pipeline semantics — ITC-DEVSECOPS;
 - domain-specific business capabilities (hospital admission, underwriting,
   warehouse picking) — outside InfoTechCanon;
-- product features, protocols, and named technologies.
+- product features, protocols, and named technologies;
+- booked cost, currency handling, and ledgers — `fin-hub` under its exchange
+  contract;
+- a canonical exchange rate between human effort and intelligence;
+- timesheet methods or labour rates.
 
 ---
 
@@ -175,26 +183,53 @@ unchanged (Core §6.5 *Profiles, Not Forks*).
 ## 4.4 CapabilityContract
 
 The machine-readable definition of a capability: id, name, purpose, anchors,
-profiles, quality dimensions, evidence hooks, relationships, and typical resource
-classes. Contracts live in `capabilities.yaml` and are the single source of
-truth. This document does not restate them.
+profiles, quality dimensions, evidence hooks, and relationships. Contracts live
+in `capabilities.yaml` and are the single source of truth. This document does
+not restate them.
+
+A contract does **not** declare resource classes. Consumption is a property of a
+provision, not of an abstract ability (see §4.11, CAP-R8).
 
 ## 4.5 CapabilityRequirement
 
 A statement that a system, product, or consumer purpose needs a capability at a
-minimum maturity:
+minimum maturity. It may also select a profile, assert intended quality targets
+against the capability's declared dimensions, and state placement constraints:
 
 ```yaml
 requires:
   - capability: identity.authentication
     minimum_maturity: D5
   - capability: data.backup
+    profile: database
     minimum_maturity: D5
+    targets:
+      rpo: {value: 5, unit: minutes}
+      rto: {value: 60, unit: minutes}
+      retention: {value: 30, unit: days}
+    constraints:
+      - dimension: geographical_separation
+        predicate: not_in
+        of:
+          - {kind: host, id: railiance01}
 ```
 
 A CapabilityRequirement is a **typed `DemandSignal`** (ITC-GOV Purpose and Demand
-extension) carrying a minimum maturity. It does not introduce a parallel
-requirement vocabulary.
+extension). It does not introduce a parallel requirement vocabulary.
+
+Rules:
+
+- `profile`, if present, MUST be a profile declared on that capability.
+- Every key of `targets` MUST be a quality dimension declared on that capability.
+- Every `constraints[].dimension` MUST be a quality dimension declared on that
+  capability.
+- `of` entries are consumer landscape references, not canon identifiers.
+- Closed predicates: `not_in`, `in`, `equals`, `lte`, `gte`.
+
+A target is an *intended* value. It does not create an SLO and does not measure
+anything. Measurement and observed values belong to ITC-LAND service level
+objectives and ITC-OBS (see §4.9). This is what lets a consumer write a need
+before any provider exists.
 
 ## 4.6 CapabilityProvider
 
@@ -209,12 +244,33 @@ resource consumption all attach here.
 
 ```yaml
 provision:
-  provider: auth.prod.eu
-  capability: identity.authentication
+  provider: backup.barman.prod
+  capability: data.backup
+  profile: database
   environment: production
-  maturity: D6
+  maturity: D4
+  consumes:
+    - class: S
+      quantity: {value: 50, unit: GB}
+      period: month
+    - class: H
+      quantity: {value: 1.0, unit: hour}
+      period: month
+      supply: internal
+    - class: P
+      quantity: {value: 1, unit: unit}
+      period: month
+      supply: external
+    - class: I
+      quantity: unknown
 ```
 
+Unknown consumption MUST be recorded as `unknown`, never as zero. Zero means
+"measured and none"; unknown means "not yet measured or not applicable."
+
+A provision MAY override a class's default `supply` and `capacity_behaviour`
+(for example contracted operator time recorded as `H` with `supply: external`).
+
 ## 4.8 CapabilityMaturityLevel
 
 | Level | State | Meaning |
@@ -234,8 +290,21 @@ level (Core §18). It describes a provision, not a document and not a consumer.
 ## 4.9 CapabilityQualityDimension
 
 A named quality attribute relevant to a capability (`rpo`, `rto`, `assurance`,
-`decision_latency`, `explainability`). The model names dimensions; *targets and
-measurement* belong to ITC-LAND service level objectives and ITC-OBS.
+`decision_latency`, `explainability`, `intelligence_intensity`). The model names
+dimensions.
+
+- **Intended targets** against those dimensions belong on a CapabilityRequirement
+  (§4.5). They are demand assertions.
+- **Measurement and observed values** belong to ITC-LAND service level objectives
+  and ITC-OBS. They are supply observations.
+
+A requirement written before any provider exists therefore does not depend on a
+service-level objective that cannot yet exist.
+
+`intelligence_intensity` is the consumption of class `I` per unit of capability
+output. It is a quality of a provision that consumes Intelligence, not a cost
+line. It is declared on the `intelligence.*` capabilities and may be used on any
+provision that consumes `I`.
 
 ## 4.10 CapabilityEvidenceHook
 
@@ -245,17 +314,65 @@ telemetry-derived evidence comes from ITC-OBS.
 
 ## 4.11 CapabilityResourceClass
 
-| ID | Class | Meaning |
-|---|---|---|
-| `C` | Compute | Generic execution capacity |
-| `S` | Storage | Persistence capacity |
-| `N` | Networking | Information movement |
-| `I` | Intelligence | Metered or purchased cognitive / semantic processing |
-| `P` | Platform | Enabling operational overhead |
+| ID | Class | Native unit | Default supply | Default capacity |
+|---|---|---|---|---|
+| `C` | Compute | `vCPU-hour` | external | elastic |
+| `S` | Storage | `GB` | external | elastic |
+| `N` | Networking | `GB` | external | elastic |
+| `I` | Intelligence | `token` | external | elastic |
+| `H` | Human Effort | `hour` | internal | constrained |
+| `P` | Platform | `unit` | external | elastic |
 
-Resource consumption attaches to a provision or implementation, never to an
-abstract capability. This is what makes capability-oriented cost questions
-answerable ("what does Authentication cost per tenant?").
+**Supply** is `internal` (drawn from own capacity) or `external` (purchased).
+It is a sourcing attribute of a consumption record, not a separate class.
+Internal versus contracted labour are both `H`.
+
+**Capacity behaviour** is `elastic` (more is purchasable at roughly linear cost
+inside the planning horizon) or `constrained` (a hard ceiling). Human effort
+inside a founder- or team-hour budget is constrained; tokens and object storage
+are elastic.
+
+Class meanings:
+
+- `C` — generic execution capacity.
+- `S` — persistence capacity.
+- `N` — information movement. Native unit is transfer volume.
+- `I` — metered cognitive or semantic processing, treated as the elastic
+  purchased substitute for `H`. Its unit cost is assumed to decline over time;
+  that is a modelling assumption, not a constant the canon asserts a value for.
+- `H` — human attention applied to provide or operate the capability. Native
+  unit is hours. `H` exists so that labour can bind a decision as a ceiling,
+  not only as a price.
+- `P` — purchased platform and enabling services that make other resources
+  usable. `P` does **not** absorb human time.
+
+The letter is `H` (not `L` for labour) so the human / intelligence contrast is
+the one the class set is designed to make observable.
+
+A provision may record a more specific compatible unit (`GPU-hour` under `C`)
+but SHOULD keep the class. Recommended native units for `C` and `P` are weak
+because those classes are heterogeneous; `hour`, `token`, and `GB` are the
+units the class set is required to protect.
+
+Resource consumption attaches to a provision or implementation, **never to an
+abstract capability**. This is what makes capability-oriented questions
+answerable ("what does Authentication consume per tenant, in hours and in
+tokens?").
+
+## 4.12 CapabilityConsumption
+
+One row of a provision's `consumes` list. It records use of a single resource
+class in that class's **native unit**, optionally over a period.
+
+Currency is not a resource class and is not a native unit. A financial overlay
+— converting hours or tokens into money — is performed by the consumer or by
+`fin-hub` under its own exchange contract. Collapsing classes into currency at
+capture time destroys the information needed for constraint and substitution
+reasoning.
+
+The canon does **not** declare a `substitutes_for` relation or an exchange rate
+between classes. If `H` and `I` appear on the same provision in native units,
+substitution is observable from the time series.
 
 ---
 
@@ -291,6 +408,15 @@ expressed as a CapabilityProfile, not a new Capability.
 **CAP-R7** The Markdown document MUST NOT restate capability definitions held in
 `capabilities.yaml`.
 
+**CAP-R8** Resource consumption MUST attach to a CapabilityProvision or
+implementation, never to a Capability. A Capability contract MUST NOT carry a
+normative resource-class declaration. A consumption record MUST use the class's
+native unit. Unknown MUST be recorded as `unknown`, never as zero.
+
+**CAP-R9** A CapabilityRequirement `profile`, target key, or constraint dimension
+MUST be declared on the required capability. A target is an intended value, not
+a measurement.
+
 ---
 
 # 6. Admission Rules
@@ -327,18 +453,19 @@ Landscape and consumer to capability:
 | `requires` | A product, workload, service, or consumer purpose requires a capability |
 | `provides` | A provider supplies a capability (creates a provision) |
 | `implements` | A technology realizes all or part of a provider |
-| `consumes` | A provision consumes resource classes |
+| `consumes` | A provision consumes resource classes in native units |
 
-Traversal from need to cost:
+Traversal from need to consumption:
 
 ```text
 ConsumerPurpose --requires--> Capability <--provides-- Service
-                                                        │ implements
-                                                        ▼
-                                                   Technology
-                                                        │ consumes
-                                                        ▼
-                                                  C / S / N / I / P
+     │                                                 │ implements
+     │ targets, constraints                            ▼
+     ▼                                            Technology
+CapabilityRequirement                                  │ consumes
+                                                       ▼
+                                              C / S / N / I / H / P
+                                              (native units; unknown allowed)
 ```
 
 ---
@@ -371,7 +498,7 @@ model. This is accepted at `proposed` status and tracked as OQ-5.
 
 | Model | Boundary |
 |---|---|
-| ITC-LAND | Owns services, technologies, runtime resources, SLOs. ITC-CAP names abilities; ITC-LAND names the things that provide and implement them. `BusinessCapability` / `ProductCapability` in ITC-LAND §11 should resolve to references here. |
+| ITC-LAND | Owns services, technologies, runtime resources, and *observed* SLOs. ITC-CAP names abilities and *intended* requirement targets; ITC-LAND names the things that provide and implement them. `BusinessCapability` / `ProductCapability` in ITC-LAND §11 should resolve to references here. |
 | ITC-GOV | Owns policy, control, evidence, assurance. ITC-CAP names capability evidence *hooks*, not evidence semantics. Capability requirements are typed demand signals from the Purpose and Demand extension. |
 | ITC-ACCESS | Owns subject, principal, permission, grant, decision. `identity.*` capabilities are abilities over those mechanisms. |
 | CARING | Access-governance analysis. May import `identity.*` ids; ITC-CAP takes no position on access-governance analysis. |
@@ -410,3 +537,10 @@ Changes made on adoption: `Profile` renamed `CapabilityProfile`; `Provision` mad
 explicit; per-capability `anchors` added; requirements bound to Purpose and
 Demand; the proposed CILM landscape model rejected in favour of ITC-LAND;
 capability definitions moved wholly into the machine-readable catalog.
+
+Version 0.2.0 (canon 0.3.0) refines the proposed model from consumer demand
+`demand/CapabilityProvisionEconomics.md`: resource-class declaration moved off
+the contract onto the provision; requirements gained profile, targets, and
+constraints; class `H` added; `P` narrowed; `I` recharacterised; consumption
+records use native units. See the decision record in
+`assimilation/it-capability-canon/ASSIMILATION.md`.

infospace/models/capability/capabilities.yaml

@@ -12,9 +12,9 @@ canon:
   name: InfoTechCanon Capability Model — Capability Catalog
   short_name: ITC-CAP
   artifact_id: model/capability
-  version: 0.1.0
+  version: 0.2.0
   status: proposed
-  canon_version: 0.2.1
+  canon_version: 0.3.0
   purpose: Canonical, implementation-independent catalog of the abilities an information system may require
     or provide.
   normative_document: models/capability/InfoTechCanonCapabilityModel.md
@@ -28,23 +28,45 @@ resource_classes:
 - id: C
   name: Compute
   description: Generic execution capacity.
-  note: Consumed by a capability provision, never by an abstract capability.
+  native_unit: vCPU-hour
+  supply: external
+  capacity_behaviour: elastic
+  note: Consumed by a capability provision, never by an abstract capability. Recommended native unit is weak; a provision may record a more specific compatible unit.
 - id: S
   name: Storage
   description: Persistence capacity.
+  native_unit: GB
+  supply: external
+  capacity_behaviour: elastic
   note: Consumed by a capability provision, never by an abstract capability.
 - id: N
   name: Networking
   description: Information movement.
-  note: Consumed by a capability provision, never by an abstract capability.
+  native_unit: GB
+  supply: external
+  capacity_behaviour: elastic
+  note: Consumed by a capability provision, never by an abstract capability. Native unit is transfer volume.
 - id: I
   name: Intelligence
-  description: Metered or purchased cognitive or semantic processing capability.
-  note: Consumed by a capability provision, never by an abstract capability.
+  description: Metered cognitive or semantic processing; the elastic purchased substitute for human effort.
+  native_unit: token
+  supply: external
+  capacity_behaviour: elastic
+  note: Consumed by a capability provision, never by an abstract capability. Unit cost is assumed to decline over time as a modelling assumption, not as a constant. No canonical exchange rate with H.
+- id: H
+  name: Human Effort
+  description: Human attention applied to provide or operate a capability.
+  native_unit: hour
+  supply: internal
+  capacity_behaviour: constrained
+  note: Consumed by a capability provision, never by an abstract capability. Internal versus contracted labour is a supply attribute, not a separate class.
 - id: P
   name: Platform
-  description: Enabling operational overhead that makes other resources usable.
-  note: Consumed by a capability provision, never by an abstract capability.
+  description: Purchased platform and enabling services that make other resources usable. Does not include human time.
+  native_unit: unit
+  supply: external
+  capacity_behaviour: elastic
+  note: Consumed by a capability provision, never by an abstract capability. Recommended native unit is weak. Human time is class H, not P.
 maturity_levels:
 - id: D0
   name: Absent
@@ -118,11 +140,6 @@ domains:
     - successful_provisioning
     - successful_deprovisioning
     - ownership_record
-    typical_resource_classes: &id001
-    - C
-    - S
-    - N
-    - P
   - id: identity.authentication
     name: Authentication
     purpose: Establish that an actor controls or legitimately represents an identity.
@@ -145,7 +162,6 @@ domains:
     - successful_authentication
     - failure_metrics
     - availability_metrics
-    typical_resource_classes: *id001
   - id: identity.authorization
     name: Authorization
     purpose: Determine whether an actor may perform an action on a resource.
@@ -165,7 +181,6 @@ domains:
     - policy_tests
     - authorization_decisions
     - denial_evidence
-    typical_resource_classes: *id001
   - id: identity.federation
     name: Identity Federation
     purpose: Establish and use trust relationships between identity domains.
@@ -183,7 +198,6 @@ domains:
     evidence_hooks:
     - federation_configuration
     - successful_federated_login
-    typical_resource_classes: *id001
   - id: identity.organization
     name: Organization & Tenancy
     purpose: Associate identities, resources, policies, and operations with organizational or tenant boundaries.
@@ -202,7 +216,6 @@ domains:
     evidence_hooks:
     - tenant_isolation_tests
     - membership_records
-    typical_resource_classes: *id001
 - id: data
   name: Data & State
   navigation_only: true
@@ -225,11 +238,6 @@ domains:
     evidence_hooks:
     - durability_tests
     - availability_metrics
-    typical_resource_classes: &id002
-    - C
-    - S
-    - N
-    - P
   - id: data.object
     name: Object Persistence
     purpose: Persist opaque objects, files, blobs, documents, or similar binary or semi-structured objects.
@@ -247,7 +255,6 @@ domains:
     evidence_hooks:
     - object_integrity_tests
     - availability_metrics
-    typical_resource_classes: *id002
   - id: data.cache
     name: Caching
     purpose: Maintain temporary or derived state for accelerated access.
@@ -266,7 +273,6 @@ domains:
     evidence_hooks:
     - cache_metrics
     - latency_metrics
-    typical_resource_classes: *id002
   - id: data.backup
     name: Backup & Restore
     purpose: Create recoverable copies or recovery points and restore previously valid persisted state
@@ -289,7 +295,6 @@ domains:
     - successful_restore_test
     - measured_rpo
     - measured_rto
-    typical_resource_classes: *id002
     depends_on:
     - data.object
     may_use:
@@ -315,7 +320,6 @@ domains:
     - retention_policy
     - integrity_verification
     - retrieval_test
-    typical_resource_classes: *id002
   - id: data.search
     name: Search & Retrieval
     purpose: Locate persisted information based on indexed or queryable characteristics.
@@ -336,7 +340,6 @@ domains:
     evidence_hooks:
     - search_tests
     - latency_metrics
-    typical_resource_classes: *id002
 - id: integration
   name: Integration & Communication
   navigation_only: true
@@ -360,10 +363,6 @@ domains:
     evidence_hooks:
     - contract_tests
     - availability_metrics
-    typical_resource_classes: &id003
-    - C
-    - N
-    - P
   - id: integration.messaging
     name: Messaging & Eventing
     purpose: Exchange asynchronous messages or events between producers and consumers.
@@ -383,7 +382,6 @@ domains:
     evidence_hooks:
     - delivery_tests
     - lag_metrics
-    typical_resource_classes: *id003
   - id: integration.exchange
     name: Data Exchange
     purpose: Move datasets, files, or structured information between systems.
@@ -403,7 +401,6 @@ domains:
     evidence_hooks:
     - transfer_tests
     - integrity_checks
-    typical_resource_classes: *id003
   - id: integration.notification
     name: Notification
     purpose: Deliver information to human users or external endpoints.
@@ -424,7 +421,6 @@ domains:
     evidence_hooks:
     - delivery_receipts
     - failure_metrics
-    typical_resource_classes: *id003
   - id: integration.traffic
     name: Traffic Management
     purpose: Route, balance, control, filter, or shape communication between endpoints.
@@ -444,7 +440,6 @@ domains:
     evidence_hooks:
     - routing_tests
     - availability_metrics
-    typical_resource_classes: *id003
 - id: runtime
   name: Runtime & Automation
   navigation_only: true
@@ -468,11 +463,6 @@ domains:
     evidence_hooks:
     - execution_tests
     - capacity_metrics
-    typical_resource_classes: &id004
-    - C
-    - S
-    - N
-    - P
   - id: runtime.configuration
     name: Configuration
     purpose: Supply controlled runtime configuration to software and services.
@@ -492,7 +482,6 @@ domains:
     evidence_hooks:
     - configuration_history
     - propagation_tests
-    typical_resource_classes: *id004
   - id: runtime.scheduling
     name: Scheduling
     purpose: Initiate activities according to time, delay, calendar, or recurrence.
@@ -510,7 +499,6 @@ domains:
     - timezone_support
     evidence_hooks:
     - schedule_execution_records
-    typical_resource_classes: *id004
   - id: runtime.workflow
     name: Workflow Orchestration
     purpose: Coordinate multi-step activities, state transitions, dependencies, retries, and completion.
@@ -529,7 +517,6 @@ domains:
     evidence_hooks:
     - workflow_completion_records
     - recovery_tests
-    typical_resource_classes: *id004
     may_use:
     - integration.messaging
     - runtime.scheduling
@@ -553,7 +540,6 @@ domains:
     evidence_hooks:
     - deployment_records
     - rollback_test
-    typical_resource_classes: *id004
 - id: operations
   name: Operations & Assurance
   navigation_only: true
@@ -578,11 +564,6 @@ domains:
     evidence_hooks:
     - telemetry_coverage
     - dashboard_or_query_evidence
-    typical_resource_classes: &id005
-    - C
-    - S
-    - N
-    - P
   - id: operations.alerting
     name: Alerting
     purpose: Detect relevant conditions and surface them to humans or automation.
@@ -601,7 +582,6 @@ domains:
     evidence_hooks:
     - alert_tests
     - incident_linkage
-    typical_resource_classes: *id005
     may_use:
     - operations.observability
     - integration.notification
@@ -623,7 +603,6 @@ domains:
     evidence_hooks:
     - audit_records
     - integrity_verification
-    typical_resource_classes: *id005
   - id: operations.recovery
     name: Service Recovery
     purpose: Restore an operational service after failure or degradation.
@@ -642,7 +621,6 @@ domains:
     evidence_hooks:
     - recovery_tests
     - incident_recovery_records
-    typical_resource_classes: *id005
     may_use:
     - data.backup
     - operations.observability
@@ -663,7 +641,6 @@ domains:
     evidence_hooks:
     - continuity_tests
     - availability_metrics
-    typical_resource_classes: *id005
 - id: security
   name: Security
   navigation_only: true
@@ -686,11 +663,6 @@ domains:
     evidence_hooks:
     - rotation_records
     - access_audit
-    typical_resource_classes: &id006
-    - C
-    - S
-    - N
-    - P
   - id: security.keys
     name: Key & Certificate Management
     purpose: Create, protect, distribute, rotate, validate, and revoke cryptographic keys and certificates.
@@ -709,7 +681,6 @@ domains:
     evidence_hooks:
     - certificate_inventory
     - rotation_records
-    typical_resource_classes: *id006
   - id: security.policy
     name: Policy Management & Enforcement
     purpose: Define, distribute, evaluate, and enforce machine-interpretable policies.
@@ -729,7 +700,6 @@ domains:
     evidence_hooks:
     - policy_tests
     - decision_records
-    typical_resource_classes: *id006
   - id: security.vulnerability
     name: Vulnerability Management
     purpose: Identify, assess, prioritize, remediate, mitigate, and track exploitable weaknesses.
@@ -749,7 +719,6 @@ domains:
     evidence_hooks:
     - scan_results
     - remediation_records
-    typical_resource_classes: *id006
 - id: governance
   name: Governance
   navigation_only: true
@@ -772,10 +741,6 @@ domains:
     evidence_hooks:
     - evidence_records
     - assessment_links
-    typical_resource_classes: &id007
-    - C
-    - S
-    - P
   - id: governance.lifecycle
     name: Information Lifecycle Governance
     purpose: Apply rules governing information retention, handling, deletion, preservation, and lifecycle
@@ -796,7 +761,6 @@ domains:
     - lifecycle_policy
     - deletion_records
     - retention_evidence
-    typical_resource_classes: *id007
 - id: commerce
   name: Commerce
   navigation_only: true
@@ -818,11 +782,6 @@ domains:
     evidence_hooks:
     - meter_records
     - reconciliation
-    typical_resource_classes: &id008
-    - C
-    - S
-    - N
-    - P
     anchor_note: No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
   - id: commerce.billing
     name: Billing
@@ -841,7 +800,6 @@ domains:
     evidence_hooks:
     - invoice_tests
     - billing_reconciliation
-    typical_resource_classes: *id008
     may_use:
     - commerce.metering
     - commerce.entitlement
@@ -865,7 +823,6 @@ domains:
     evidence_hooks:
     - payment_records
     - settlement_reconciliation
-    typical_resource_classes: *id008
     may_use:
     - identity.authentication
     - operations.audit
@@ -889,7 +846,6 @@ domains:
     evidence_hooks:
     - entitlement_tests
     - decision_records
-    typical_resource_classes: *id008
     may_use:
     - identity.authorization
 - id: intelligence
@@ -912,14 +868,10 @@ domains:
     - latency
     - cost
     - safety
+    - intelligence_intensity
     evidence_hooks:
     - evaluation_results
     - latency_metrics
-    typical_resource_classes: &id009
-    - C
-    - N
-    - I
-    - P
     anchor_note: No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
   - id: intelligence.extraction
     name: Extraction & Classification
@@ -936,10 +888,10 @@ domains:
     - recall
     - precision
     - latency
+    - intelligence_intensity
     evidence_hooks:
     - evaluation_results
     - golden_set_tests
-    typical_resource_classes: *id009
     anchor_note: No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
   - id: intelligence.embedding
     name: Semantic Representation
@@ -954,10 +906,10 @@ domains:
     - semantic_quality
     - latency
     - cost
+    - intelligence_intensity
     evidence_hooks:
     - retrieval_benchmarks
     - latency_metrics
-    typical_resource_classes: *id009
     anchor_note: No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
   - id: intelligence.retrieval
     name: Semantic Retrieval & Ranking
@@ -974,9 +926,9 @@ domains:
     - precision
     - ranking_quality
     - latency
+    - intelligence_intensity
     evidence_hooks:
     - retrieval_benchmarks
-    typical_resource_classes: *id009
     may_use:
     - intelligence.embedding
     - data.search
@@ -995,10 +947,10 @@ domains:
     - latency
     - cost
     - explainability
+    - intelligence_intensity
     evidence_hooks:
     - task_evaluations
     - decision_records
-    typical_resource_classes: *id009
     may_use:
     - intelligence.retrieval
     anchor_note: No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.