Assimilate ITCC v0.1 as Capability Model; canon 0.2.0

Define the intake and assimilation practice (incoming/ drop zone -> frozen
source snapshot -> Minimal Assimilation Profile -> disposition gate -> canon
transformation -> versioned change notes) and run it on the first inputs.

- infospace/assimilation/intake-and-assimilation-practice.md, incoming/README.md
- assimilation/it-capability-canon: frozen source, comparison matrix, 26
  mappings, 8 proposed changes, 7 open questions, decision record (adapt)
- new model ITC-CAP with 41-capability machine-readable catalog, anchored to
  owning canon models; CILM rejected, Profile renamed, Provision made explicit
- registered in canon.yaml / artifacts index / infospace.yaml; regenerated
  briefs, indexes, views; canon version 0.1.0-scaffold -> 0.2.0 + CHANGELOG
- ITC-WP-0014 for promotion work; ITC-WP-0013 added to the workplan registry

make validate: ok (65 artifacts, 0 errors/warnings). make test: 22 passed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

infospace/assimilation/it-capability-canon/mappings.yaml

@@ -0,0 +1,181 @@
+assimilation: assimilation/it-capability-canon
+source: ITCC v0.1
+target_canon_version: "0.2.0"
+note: >
+  Concept-level mappings from the source vocabulary to canonical owners.
+  mapping_type follows the canon mapping vocabulary: equivalent, narrower,
+  broader, related, imports, superseded_by, no_mapping.
+
+mappings:
+  - source_concept: Implementation
+    target_concept: Technology / SoftwareEntity / RuntimeEntity
+    target_owner: model/landscape
+    mapping_type: imports
+    rationale: Landscape is the canonical owner of concrete landscape entities.
+    confidence: high
+
+  - source_concept: Provider
+    target_concept: Service / ServiceProvider / ServiceInstance
+    target_owner: model/landscape
+    mapping_type: related
+    rationale: CapabilityProvider is a role played by a landscape entity, not a new entity type.
+    confidence: high
+
+  - source_concept: Resource
+    target_concept: RuntimeResource
+    target_owner: model/landscape
+    mapping_type: broader
+    rationale: C/S/N/I/P are cost-attribution classes over runtime resources, including non-runtime metered intelligence.
+    confidence: medium
+
+  - source_concept: Evidence
+    target_concept: Evidence
+    target_owner: model/governance
+    mapping_type: imports
+    rationale: Governance owns evidence semantics; capability evidence hooks name expected evidence types.
+    confidence: high
+
+  - source_concept: Evidence (telemetry-derived)
+    target_concept: TelemetrySignal / Metric / SLO
+    target_owner: model/observability
+    mapping_type: related
+    rationale: Measured maturity evidence (availability, latency, RPO/RTO) is produced by observability.
+    confidence: high
+
+  - source_concept: Requirement
+    target_concept: DemandSignal / ConsumerNeed
+    target_owner: model/purpose-demand-extension
+    mapping_type: narrower
+    rationale: A capability requirement is a typed demand signal carrying a minimum maturity.
+    confidence: high
+
+  - source_concept: Quality dimension
+    target_concept: ServiceLevelObjective
+    target_owner: model/landscape
+    mapping_type: related
+    rationale: Dimensions are named; targets and measurement remain with SLOs and observability.
+    confidence: medium
+
+  - source_concept: identity.authentication
+    target_concept: Principal / AuthenticationEvent
+    target_owner: model/access-control
+    mapping_type: related
+    rationale: The capability is the ability; Access Control owns the mechanism semantics.
+    confidence: high
+
+  - source_concept: identity.authorization
+    target_concept: AuthorizationDecision / Permission / Grant
+    target_owner: model/access-control
+    mapping_type: related
+    rationale: Same ability/mechanism split; CARING adds access-governance analysis over it.
+    confidence: high
+
+  - source_concept: identity.organization
+    target_concept: Organization / Team / Tenant
+    target_owner: model/organization
+    mapping_type: related
+    rationale: Tenancy structure stays with Organization; the capability is the ability to scope by it.
+    confidence: high
+
+  - source_concept: security.policy
+    target_concept: Policy / Rule / Control
+    target_owner: model/governance
+    mapping_type: imports
+    rationale: Policy semantics are owned by Governance and must not be redefined per capability.
+    confidence: high
+
+  - source_concept: security.secrets / security.keys / security.vulnerability
+    target_concept: Secret / Key / Vulnerability / Finding
+    target_owner: model/security
+    mapping_type: related
+    confidence: high
+
+  - source_concept: governance.evidence
+    target_concept: Evidence / Assurance / Control
+    target_owner: model/governance
+    mapping_type: related
+    confidence: high
+
+  - source_concept: governance.lifecycle
+    target_concept: Retention / Classification / DataContract
+    target_owner: model/data
+    mapping_type: related
+    confidence: medium
+
+  - source_concept: data.* (transactional, object, cache, backup, archive, search)
+    target_concept: Dataset / DataStore / Schema / Lineage / Retention
+    target_owner: model/data
+    mapping_type: related
+    rationale: Data owns the assets; capabilities are the abilities exercised over them.
+    confidence: high
+
+  - source_concept: integration.traffic
+    target_concept: Routing / Exposure / Reachability / NetworkPolicy
+    target_owner: model/network
+    mapping_type: related
+    confidence: high
+
+  - source_concept: integration.api / integration.messaging / integration.exchange
+    target_concept: Endpoint / Interface / Flow
+    target_owner: model/landscape
+    mapping_type: related
+    confidence: medium
+
+  - source_concept: runtime.deployment
+    target_concept: Release / Deployment / Artifact
+    target_owner: model/devsecops
+    mapping_type: related
+    confidence: high
+
+  - source_concept: runtime.execution / runtime.configuration / runtime.scheduling
+    target_concept: RuntimeEntity / RuntimeResource / Configuration
+    target_owner: model/landscape
+    mapping_type: related
+    confidence: medium
+
+  - source_concept: runtime.workflow
+    target_concept: Task / Action / Dependency
+    target_owner: model/task
+    mapping_type: related
+    rationale: Task owns work-item semantics; workflow orchestration is the ability to run them.
+    confidence: medium
+
+  - source_concept: operations.observability / operations.alerting
+    target_concept: Telemetry / Alert / Health / SLO
+    target_owner: model/observability
+    mapping_type: related
+    confidence: high
+
+  - source_concept: operations.audit
+    target_concept: Evidence / AuditRecord
+    target_owner: model/governance
+    mapping_type: related
+    confidence: high
+
+  - source_concept: operations.recovery / operations.continuity
+    target_concept: Incident / ServiceLevelObjective
+    target_owner: model/security
+    mapping_type: related
+    confidence: low
+    note: Continuity has no strong canon owner today — see open question OQ-4.
+
+  - source_concept: commerce.*
+    target_concept: (none)
+    target_owner: model/capability
+    mapping_type: no_mapping
+    rationale: New canon surface; no existing model covers metering, billing, payment, or entitlement.
+    confidence: high
+
+  - source_concept: intelligence.*
+    target_concept: (none)
+    target_owner: model/capability
+    mapping_type: no_mapping
+    rationale: New canon surface. Information Space covers markdown knowledge packaging and retrieval, not metered cognitive processing.
+    confidence: high
+
+  - source_concept: CILM (Canonical IT Landscape Model)
+    target_concept: InfoTechCanonLandscapeModel
+    target_owner: model/landscape
+    mapping_type: superseded_by
+    rationale: The proposed sibling model is already the canon Landscape Model. Not adopted as a separate artifact.
+    confidence: high