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/README.md

@@ -1,3 +1,29 @@
 # Assimilation
 
 Assimilation records for external knowledge and consumer demand live here.
+
+The procedure that governs them — from the `incoming/` drop zone through frozen
+source snapshots, comparison, disposition, canon transformation, and the
+resulting canon version — is
+[`intake-and-assimilation-practice.md`](intake-and-assimilation-practice.md).
+
+Each assimilation is one directory:
+
+```text
+<slug>/
+  assimilation.yaml        record (schemas/assimilation.schema.yaml)
+  ASSIMILATION.md          scope, findings, decision record
+  source/                  frozen snapshot of the processed input
+  source-summary.md
+  extracted-concepts.yaml
+  comparison-matrix.md
+  mappings.yaml
+  proposed-changes.md
+  open-questions.md
+```
+
+## Records
+
+| Assimilation | Source | Disposition | Status |
+|---|---|---|---|
+| [`it-capability-canon`](it-capability-canon/) | Information Technology Capability Canon (ITCC) v0.1 | adapt | decided |