Assimilate ITCC v0.1 as Capability Model; canon 0.2.0
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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>
This commit is contained in:
tegwick 2026-08-14 20:54:32 +02:00
parent b8d060b5b5
commit 28d5824362
37 changed files with 5333 additions and 93 deletions

View file

@ -1,5 +1,5 @@
root: infospace
file_count: 161
file_count: 175
files:
- path: README.md
directory: .
@ -85,6 +85,9 @@ files:
- path: agent/briefs/model-access-control.md
directory: agent/briefs
name: model-access-control.md
- path: agent/briefs/model-capability.md
directory: agent/briefs
name: model-capability.md
- path: agent/briefs/model-data.md
directory: agent/briefs
name: model-data.md
@ -199,6 +202,39 @@ files:
- path: assimilation/README.md
directory: assimilation
name: README.md
- path: assimilation/intake-and-assimilation-practice.md
directory: assimilation
name: intake-and-assimilation-practice.md
- path: assimilation/it-capability-canon/ASSIMILATION.md
directory: assimilation/it-capability-canon
name: ASSIMILATION.md
- path: assimilation/it-capability-canon/assimilation.yaml
directory: assimilation/it-capability-canon
name: assimilation.yaml
- path: assimilation/it-capability-canon/comparison-matrix.md
directory: assimilation/it-capability-canon
name: comparison-matrix.md
- path: assimilation/it-capability-canon/extracted-concepts.yaml
directory: assimilation/it-capability-canon
name: extracted-concepts.yaml
- path: assimilation/it-capability-canon/mappings.yaml
directory: assimilation/it-capability-canon
name: mappings.yaml
- path: assimilation/it-capability-canon/open-questions.md
directory: assimilation/it-capability-canon
name: open-questions.md
- path: assimilation/it-capability-canon/proposed-changes.md
directory: assimilation/it-capability-canon
name: proposed-changes.md
- path: assimilation/it-capability-canon/source/ITCapabilityCanonV0.1.md
directory: assimilation/it-capability-canon/source
name: ITCapabilityCanonV0.1.md
- path: assimilation/it-capability-canon/source/capabilities.yaml
directory: assimilation/it-capability-canon/source
name: capabilities.yaml
- path: assimilation/it-capability-canon/source-summary.md
directory: assimilation/it-capability-canon
name: source-summary.md
- path: concepts/purpose-demand.yaml
directory: concepts
name: purpose-demand.yaml
@ -304,6 +340,12 @@ files:
- path: models/access-control/InfoTechCanonAccessControlModel.md
directory: models/access-control
name: InfoTechCanonAccessControlModel.md
- path: models/capability/InfoTechCanonCapabilityModel.md
directory: models/capability
name: InfoTechCanonCapabilityModel.md
- path: models/capability/capabilities.yaml
directory: models/capability
name: capabilities.yaml
- path: models/data/InfoTechCanonDataModel.md
directory: models/data
name: InfoTechCanonDataModel.md