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>
2026-08-14 20:54:32 +02:00
|
|
|
---
|
|
|
|
|
id: agent-brief/model-capability
|
|
|
|
|
artifact_id: model/capability
|
|
|
|
|
source_path: models/capability/InfoTechCanonCapabilityModel.md
|
|
|
|
|
source_kind: model
|
|
|
|
|
generated: true
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
|
|
|
|
|
|
|
|
|
|
# Agent Brief: InfoTechCanon Capability Model
|
|
|
|
|
|
|
|
|
|
- Artifact ID: `model/capability`
|
|
|
|
|
- Kind: `model`
|
|
|
|
|
- Canonical path: `models/capability/InfoTechCanonCapabilityModel.md`
|
|
|
|
|
- Full source: `models/capability/InfoTechCanonCapabilityModel.md`
|
|
|
|
|
- Summary: Domain model used by canon profiles and standards: InfoTechCanon Capability Model.
|
|
|
|
|
|
|
|
|
|
## Retrieval Hints
|
|
|
|
|
|
|
|
|
|
Imports and anchors:
|
|
|
|
|
- `kernel/itc-core`
|
|
|
|
|
- `model/governance`
|
|
|
|
|
- `model/landscape`
|
|
|
|
|
- `model/observability`
|
|
|
|
|
- `model/purpose-demand-extension`
|
|
|
|
|
|
|
|
|
|
## Owned Concepts
|
|
|
|
|
|
|
|
|
|
- `Capability`
|
2026-08-15 18:19:30 +02:00
|
|
|
- `CapabilityConsumption`
|
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>
2026-08-14 20:54:32 +02:00
|
|
|
- `CapabilityContract`
|
|
|
|
|
- `CapabilityDomain`
|
|
|
|
|
- `CapabilityEvidenceHook`
|
|
|
|
|
- `CapabilityInclusionRule`
|
|
|
|
|
- `CapabilityMaturityLevel`
|
|
|
|
|
- `CapabilityProfile`
|
|
|
|
|
- `CapabilityProvider`
|
|
|
|
|
- `CapabilityProvision`
|
|
|
|
|
- `CapabilityQualityDimension`
|
|
|
|
|
- `CapabilityRequirement`
|
|
|
|
|
- `CapabilityResourceClass`
|
|
|
|
|
- `InfoTechCanon Capability Model`
|
|
|
|
|
|
|
|
|
|
## Related Distinctions
|
|
|
|
|
|
|
|
|
|
No common distinction is anchored directly on this artifact.
|