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>

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

@@ -0,0 +1,133 @@
+---
+id: ITC-WP-0014
+type: workplan
+title: "Capability Model consolidation (post-ITCC assimilation)"
+domain: infotech
+topic_slug: canon
+repo: info-tech-canon
+status: proposed
+priority: medium
+created: "2026-08-14"
+updated: "2026-08-14"
+depends_on_workplans:
+  - ITC-WP-0003
+  - ITC-WP-0006
+owner: claude
+spec_refs:
+  - infospace/assimilation/it-capability-canon/ASSIMILATION.md
+  - infospace/assimilation/it-capability-canon/proposed-changes.md
+  - infospace/assimilation/it-capability-canon/open-questions.md
+  - infospace/models/capability/InfoTechCanonCapabilityModel.md
+---
+
+# ITC-WP-0014 — Capability Model Consolidation
+
+## Goal
+
+Promote `InfoTechCanonCapabilityModel` from `proposed` to a usable canon model by
+closing the items the ITCC v0.1 assimilation deliberately deferred.
+
+## Intent
+
+Canon version 0.2.0 adopted the capability vocabulary under disposition `adapt`.
+The model is registered, validated, and anchored, but it has no schema, no formal
+mapping artifacts, no profile exercising it, and one unresolved identifier
+question that is blocking because capability ids are durable interfaces.
+
+## Tasks
+
+### T01 — Resolve the `governance.*` identifier prefix (OQ-2)
+
+```task
+id: ITC-WP-0014-T01
+status: todo
+priority: high
+```
+
+Decide between keeping the ids, renumbering to `security.*`, or splitting the
+navigation domain into `security` and `governance` (preferred — preserves every
+id). Record as a DecisionRecord. **Blocks promotion beyond `proposed`.**
+
+### T02 — Publish `capability.schema.yaml`
+
+```task
+id: ITC-WP-0014-T02
+status: todo
+priority: high
+depends_on: [T01]
+```
+
+Add the capability contract schema under `infospace/schemas/`, register it in
+`infospace/infospace.yaml`, and validate `capabilities.yaml` against it.
+
+### T03 — Formal mapping artifacts for each anchor
+
+```task
+id: ITC-WP-0014-T03
+status: todo
+priority: medium
+depends_on: [T02]
+```
+
+Turn `assimilation/it-capability-canon/mappings.yaml` into per-pair mapping
+artifacts under `infospace/mappings/` conforming to `mapping.schema.yaml`.
+
+### T04 — Small-SaaS capability requirement set
+
+```task
+id: ITC-WP-0014-T04
+status: todo
+priority: medium
+depends_on: [T02]
+```
+
+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.
+
+### T05 — Landscape and kernel-map revision
+
+```task
+id: ITC-WP-0014-T05
+status: todo
+priority: medium
+depends_on: [T01]
+```
+
+Revise `InfoTechCanonLandscapeModel` §11.4 (the deferred strategy/capability note)
+to reference ITC-CAP, and add the capability model to
+`InfoTechCanonKernelMap`.
+
+### T06 — Requirement/provision validation in the service surface
+
+```task
+id: ITC-WP-0014-T06
+status: todo
+priority: low
+depends_on: [T02]
+```
+
+Extend the CLI/JSON/API surface (ITC-WP-0002) to answer "does this environment
+satisfy this product's capability requirements?" — the validator sketched in
+source §18. Covers OQ-6.
+
+### T07 — Promotion review
+
+```task
+id: ITC-WP-0014-T07
+status: todo
+priority: medium
+depends_on: [T01, T02, T03, T04]
+```
+
+Promote the model from `proposed` to `draft` or `release-candidate`, bump the
+canon version, and write the `CHANGELOG.md` entry.
+
+## Out of scope
+
+- New domain models for `commerce.*` / `intelligence.*` (OQ-5) — needs a real
+  consumer demand first.
+- Canon-wide intended/declared/applied/observed/assessed state qualifiers (OQ-3)
+  — kernel-level pressure, not a capability-model decision.
+- CARING importing `identity.*` ids — touches a release-candidate standard and
+  needs its own review.

workplans/index.yaml

@@ -179,3 +179,31 @@ workplans:
       - repository-layout standard placement and extension candidates
       - registered repository-layout standard
       - consumer adoption brief
+
+  - id: ITC-WP-0013
+    title: Attribute Value Type catalog (Data Model extension)
+    status: proposed
+    priority: high
+    path: workplans/ITC-WP-0013-attribute-value-type-catalog.md
+    depends_on:
+      - ITC-WP-0006
+    produces:
+      - reviewed attribute-value-type demand signal
+      - attribute value type catalog standard section
+      - machine-readable attribute value type catalog
+      - consumer alignment note
+
+  - id: ITC-WP-0014
+    title: Capability Model consolidation (post-ITCC assimilation)
+    status: proposed
+    priority: medium
+    path: workplans/ITC-WP-0014-capability-model-consolidation.md
+    depends_on:
+      - ITC-WP-0003
+      - ITC-WP-0006
+    produces:
+      - resolved capability identifier prefix decision
+      - capability contract schema
+      - formal capability mapping artifacts
+      - small-saas capability requirement set
+      - capability requirement/provision validation surface