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
# InfoTechCanon Capability Catalog
#
# Canonical machine-readable source of truth for the capability baseline.
# The normative prose lives in InfoTechCanonCapabilityModel.md; capability
# definitions are NOT duplicated there.
#
# Adapted from ITCC v0.1 via assimilation/it-capability-canon.
# Capability ids are durable interfaces: renaming or removing one requires
# explicit migration semantics.
canon :
id : itc-cap
name : InfoTechCanon Capability Model — Capability Catalog
short_name : ITC-CAP
artifact_id : model/capability
2026-08-15 18:19:30 +02:00
version : 0.2 .0
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
status : proposed
2026-08-15 18:19:30 +02:00
canon_version : 0.3 .0
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
purpose : Canonical, implementation-independent catalog of the abilities an information system may require
or provide.
normative_document : models/capability/InfoTechCanonCapabilityModel.md
provenance :
assimilation : assimilation/it-capability-canon
source_body : Information Technology Capability Canon (ITCC)
source_version : '0.1'
source_path : infospace/assimilation/it-capability-canon/source/capabilities.yaml
disposition : adapt
resource_classes :
- id : C
name : Compute
description : Generic execution capacity.
2026-08-15 18:19:30 +02:00
native_unit : vCPU-hour
supply : external
capacity_behaviour : elastic
note : Consumed by a capability provision, never by an abstract capability. Recommended native unit is weak; a provision may record a more specific compatible unit.
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 : S
name : Storage
description : Persistence capacity.
2026-08-15 18:19:30 +02:00
native_unit : GB
supply : external
capacity_behaviour : elastic
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
note : Consumed by a capability provision, never by an abstract capability.
- id : N
name : Networking
description : Information movement.
2026-08-15 18:19:30 +02:00
native_unit : GB
supply : external
capacity_behaviour : elastic
note : Consumed by a capability provision, never by an abstract capability. Native unit is transfer volume.
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 : I
name : Intelligence
2026-08-15 18:19:30 +02:00
description : Metered cognitive or semantic processing; the elastic purchased substitute for human effort.
native_unit : token
supply : external
capacity_behaviour : elastic
note : Consumed by a capability provision, never by an abstract capability. Unit cost is assumed to decline over time as a modelling assumption, not as a constant. No canonical exchange rate with H.
- id : H
name : Human Effort
description : Human attention applied to provide or operate a capability.
native_unit : hour
supply : internal
capacity_behaviour : constrained
note : Consumed by a capability provision, never by an abstract capability. Internal versus contracted labour is a supply attribute, not a separate class.
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 : P
name : Platform
2026-08-15 18:19:30 +02:00
description : Purchased platform and enabling services that make other resources usable. Does not include human time.
native_unit : unit
supply : external
capacity_behaviour : elastic
note : Consumed by a capability provision, never by an abstract capability. Recommended native unit is weak. Human time is class H, not P.
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
maturity_levels :
- id : D0
name : Absent
description : Capability is not provided.
applies_to : capability_provision
- id : D1
name : Experimental
description : Proof of concept or exploratory implementation.
applies_to : capability_provision
- id : D2
name : Available
description : A provider exists and can be consumed.
applies_to : capability_provision
- id : D3
name : Usable
description : Documented and practically consumable.
applies_to : capability_provision
- id : D4
name : Production
description : Approved for production dependency.
applies_to : capability_provision
- id : D5
name : Reliable
description : Reliability is measured and actively controlled.
applies_to : capability_provision
- id : D6
name : Scalable
description : Capacity and operational scaling are demonstrated.
applies_to : capability_provision
- id : D7
name : Strategic
description : Governed, reusable, and deliberately evolved as a platform capability.
applies_to : capability_provision
relationship_types :
- id : depends_on
description : Capability normally requires another capability to operate.
- id : may_use
description : Capability may use another capability without conceptual dependency.
- id : composes
description : A higher-level capability or pattern is composed from lower-level capabilities.
- id : requires
description : A landscape entity requires a capability.
- id : provides
description : A provider supplies a capability.
- id : implements
description : A technology or implementation realizes a provider or capability provision.
- id : consumes
description : A provider or implementation consumes economic resources.
domains :
- id : identity
name : Identity & Access
navigation_only : true
capabilities :
- id : identity.lifecycle
name : Identity Lifecycle
purpose : Create, maintain, suspend, recover, and remove identities over time.
anchors :
- model/organization
- model/access-control
profiles :
- human
- machine
- external
- privileged
quality_dimensions :
- provisioning_latency
- deprovisioning_latency
- recovery
- ownership
evidence_hooks :
- successful_provisioning
- successful_deprovisioning
- ownership_record
- id : identity.authentication
name : Authentication
purpose : Establish that an actor controls or legitimately represents an identity.
anchors :
- model/access-control
profiles :
- human
- machine
- password
- passkey
- mfa
- passwordless
- high-assurance
quality_dimensions :
- assurance
- availability
- latency
- factor_support
evidence_hooks :
- successful_authentication
- failure_metrics
- availability_metrics
- id : identity.authorization
name : Authorization
purpose : Determine whether an actor may perform an action on a resource.
anchors :
- model/access-control
- standard/caring
profiles :
- rbac
- abac
- relationship-based
- policy-based
quality_dimensions :
- decision_latency
- policy_coverage
- explainability
evidence_hooks :
- policy_tests
- authorization_decisions
- denial_evidence
- id : identity.federation
name : Identity Federation
purpose : Establish and use trust relationships between identity domains.
anchors :
- model/access-control
profiles :
- workforce
- customer
- partner
- machine
quality_dimensions :
- trust_scope
- protocol_support
- availability
evidence_hooks :
- federation_configuration
- successful_federated_login
- id : identity.organization
name : Organization & Tenancy
purpose : Associate identities, resources, policies, and operations with organizational or tenant boundaries.
anchors :
- model/organization
profiles :
- organization
- team
- tenant
- hierarchy
- delegation
quality_dimensions :
- isolation
- delegation
- hierarchy_depth
evidence_hooks :
- tenant_isolation_tests
- membership_records
- id : data
name : Data & State
navigation_only : true
capabilities :
- id : data.transactional
name : Transactional Persistence
purpose : Persist structured mutable state with defined consistency and transaction semantics.
anchors :
- model/data
profiles :
- relational
- document
- key-value
quality_dimensions :
- consistency
- durability
- availability
- latency
- throughput
evidence_hooks :
- durability_tests
- availability_metrics
- id : data.object
name : Object Persistence
purpose : Persist opaque objects, files, blobs, documents, or similar binary or semi-structured objects.
anchors :
- model/data
profiles :
- blob
- document
- artifact
quality_dimensions :
- durability
- availability
- retention
- size_limits
evidence_hooks :
- object_integrity_tests
- availability_metrics
- id : data.cache
name : Caching
purpose : Maintain temporary or derived state for accelerated access.
anchors :
- model/data
- model/landscape
profiles :
- local
- distributed
- content
quality_dimensions :
- hit_rate
- latency
- eviction_policy
- freshness
evidence_hooks :
- cache_metrics
- latency_metrics
- id : data.backup
name : Backup & Restore
purpose : Create recoverable copies or recovery points and restore previously valid persisted state
after loss, corruption, or erroneous modification.
anchors :
- model/data
profiles :
- database
- object
- volume
quality_dimensions :
- rpo
- rto
- retention
- isolation
- geographical_separation
- restore_validation
evidence_hooks :
- successful_backup
- successful_restore_test
- measured_rpo
- measured_rto
depends_on :
- data.object
may_use :
- runtime.scheduling
- operations.observability
- id : data.archive
name : Archive & Retention
purpose : Preserve information for long-term retention under defined lifecycle, integrity, and retrieval
rules.
anchors :
- model/data
- model/governance
profiles :
- regulatory
- operational
- cold
quality_dimensions :
- retention
- immutability
- retrievability
- integrity
evidence_hooks :
- retention_policy
- integrity_verification
- retrieval_test
- id : data.search
name : Search & Retrieval
purpose : Locate persisted information based on indexed or queryable characteristics.
anchors :
- model/data
- model/information-space
profiles :
- lexical
- structured
- faceted
- semantic
- hybrid
quality_dimensions :
- latency
- recall
- precision
- freshness
evidence_hooks :
- search_tests
- latency_metrics
- id : integration
name : Integration & Communication
navigation_only : true
capabilities :
- id : integration.api
name : API Exposure
purpose : Expose machine-consumable interfaces through which systems can invoke or retrieve functionality.
anchors :
- model/landscape
- model/network
profiles :
- request-response
- streaming
- public
- internal
quality_dimensions :
- availability
- latency
- compatibility
- rate_limits
evidence_hooks :
- contract_tests
- availability_metrics
- id : integration.messaging
name : Messaging & Eventing
purpose : Exchange asynchronous messages or events between producers and consumers.
anchors :
- model/landscape
profiles :
- queue
- pub-sub
- event-stream
- event-bus
quality_dimensions :
- delivery_semantics
- ordering
- durability
- latency
- throughput
evidence_hooks :
- delivery_tests
- lag_metrics
- id : integration.exchange
name : Data Exchange
purpose : Move datasets, files, or structured information between systems.
anchors :
- model/data
- model/landscape
profiles :
- batch
- file
- stream
- managed-transfer
quality_dimensions :
- integrity
- latency
- throughput
- retries
evidence_hooks :
- transfer_tests
- integrity_checks
- id : integration.notification
name : Notification
purpose : Deliver information to human users or external endpoints.
anchors :
- model/landscape
profiles :
- email
- sms
- push
- chat
- webhook
- physical-mail
quality_dimensions :
- delivery_rate
- latency
- channel_support
- tracking
evidence_hooks :
- delivery_receipts
- failure_metrics
- id : integration.traffic
name : Traffic Management
purpose : Route, balance, control, filter, or shape communication between endpoints.
anchors :
- model/network
profiles :
- load-balancing
- ingress
- service-routing
- rate-limiting
- api-gateway
quality_dimensions :
- availability
- latency
- routing_correctness
- capacity
evidence_hooks :
- routing_tests
- availability_metrics
- id : runtime
name : Runtime & Automation
navigation_only : true
capabilities :
- id : runtime.execution
name : Workload Execution
purpose : Execute software workloads with defined runtime resources and isolation.
anchors :
- model/landscape
profiles :
- process
- container
- virtual-machine
- function
- batch
quality_dimensions :
- availability
- isolation
- startup_time
- capacity
evidence_hooks :
- execution_tests
- capacity_metrics
- id : runtime.configuration
name : Configuration
purpose : Supply controlled runtime configuration to software and services.
anchors :
- model/landscape
- model/devsecops
profiles :
- static
- dynamic
- environment
- feature
quality_dimensions :
- versioning
- propagation_latency
- consistency
- auditability
evidence_hooks :
- configuration_history
- propagation_tests
- id : runtime.scheduling
name : Scheduling
purpose : Initiate activities according to time, delay, calendar, or recurrence.
anchors :
- model/landscape
- model/task
profiles :
- cron
- calendar
- delay
- recurring
quality_dimensions :
- timing_accuracy
- delivery_guarantee
- timezone_support
evidence_hooks :
- schedule_execution_records
- id : runtime.workflow
name : Workflow Orchestration
purpose : Coordinate multi-step activities, state transitions, dependencies, retries, and completion.
anchors :
- model/task
profiles :
- durable
- human-in-the-loop
- saga
- agentic
quality_dimensions :
- durability
- retry_semantics
- visibility
- recovery
evidence_hooks :
- workflow_completion_records
- recovery_tests
may_use :
- integration.messaging
- runtime.scheduling
- integration.notification
- id : runtime.deployment
name : Deployment & Release
purpose : Bring defined software versions and configurations into operational environments in a controlled
manner.
anchors :
- model/devsecops
profiles :
- rolling
- blue-green
- canary
- immutable
quality_dimensions :
- rollback
- lead_time
- failure_rate
- traceability
evidence_hooks :
- deployment_records
- rollback_test
- id : operations
name : Operations & Assurance
navigation_only : true
capabilities :
- id : operations.observability
name : Observability
purpose : Establish operational state and behavior from telemetry such as logs, metrics, traces, events,
and derived signals.
anchors :
- model/observability
profiles :
- logs
- metrics
- traces
- events
- profiles
quality_dimensions :
- coverage
- freshness
- retention
- queryability
evidence_hooks :
- telemetry_coverage
- dashboard_or_query_evidence
- id : operations.alerting
name : Alerting
purpose : Detect relevant conditions and surface them to humans or automation.
anchors :
- model/observability
profiles :
- threshold
- anomaly
- event
- slo
quality_dimensions :
- detection_latency
- precision
- delivery
- escalation
evidence_hooks :
- alert_tests
- incident_linkage
may_use :
- operations.observability
- integration.notification
- id : operations.audit
name : Audit
purpose : Produce attributable historical evidence about relevant actions, changes, and decisions.
anchors :
- model/governance
profiles :
- security
- administrative
- business
- decision
quality_dimensions :
- integrity
- attribution
- retention
- queryability
evidence_hooks :
- audit_records
- integrity_verification
- id : operations.recovery
name : Service Recovery
purpose : Restore an operational service after failure or degradation.
anchors :
- model/observability
- model/security
profiles :
- restart
- failover
- rebuild
- disaster-recovery
quality_dimensions :
- rto
- recovery_success_rate
- automation
evidence_hooks :
- recovery_tests
- incident_recovery_records
may_use :
- data.backup
- operations.observability
- id : operations.continuity
name : Continuity
purpose : Maintain acceptable service operation despite disruption.
anchors :
- model/governance
profiles :
- high-availability
- multi-zone
- multi-region
- degraded-mode
quality_dimensions :
- availability
- fault_tolerance
- capacity_reserve
evidence_hooks :
- continuity_tests
- availability_metrics
- id : security
2026-08-15 02:43:55 +02:00
name : Security
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
navigation_only : true
capabilities :
- id : security.secrets
name : Secret Management
purpose : Protect, distribute, rotate, and revoke confidential credentials and secrets.
anchors :
- model/security
profiles :
- static
- dynamic
- application
- human
quality_dimensions :
- rotation
- access_control
- auditability
- availability
evidence_hooks :
- rotation_records
- access_audit
- id : security.keys
name : Key & Certificate Management
purpose : Create, protect, distribute, rotate, validate, and revoke cryptographic keys and certificates.
anchors :
- model/security
profiles :
- tls
- signing
- encryption
- pki
quality_dimensions :
- rotation
- revocation
- expiry_control
- key_protection
evidence_hooks :
- certificate_inventory
- rotation_records
- id : security.policy
name : Policy Management & Enforcement
purpose : Define, distribute, evaluate, and enforce machine-interpretable policies.
anchors :
- model/governance
- model/security
profiles :
- access
- configuration
- admission
- compliance
quality_dimensions :
- coverage
- decision_latency
- versioning
- explainability
evidence_hooks :
- policy_tests
- decision_records
- id : security.vulnerability
name : Vulnerability Management
purpose : Identify, assess, prioritize, remediate, mitigate, and track exploitable weaknesses.
anchors :
- model/security
profiles :
- source
- dependency
- image
- runtime
- infrastructure
quality_dimensions :
- coverage
- time_to_detect
- time_to_remediate
- risk_acceptance
evidence_hooks :
- scan_results
- remediation_records
2026-08-15 02:43:55 +02:00
- id : governance
name : Governance
navigation_only : true
capabilities :
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 : governance.evidence
name : Compliance Evidence
purpose : Produce and maintain evidence supporting governance, assurance, certification, or compliance
assertions.
anchors :
- model/governance
profiles :
- technical
- organizational
- regulatory
quality_dimensions :
- completeness
- traceability
- freshness
- integrity
evidence_hooks :
- evidence_records
- assessment_links
- id : governance.lifecycle
name : Information Lifecycle Governance
purpose : Apply rules governing information retention, handling, deletion, preservation, and lifecycle
transitions.
anchors :
- model/governance
- model/data
profiles :
- retention
- deletion
- legal-hold
- classification
quality_dimensions :
- coverage
- enforcement
- traceability
evidence_hooks :
- lifecycle_policy
- deletion_records
- retention_evidence
- id : commerce
name : Commerce
navigation_only : true
capabilities :
- id : commerce.metering
name : Metering
purpose : Measure usage or activity that is commercially or contractually relevant.
anchors : [ ]
profiles :
- usage
- event
- capacity
- time
quality_dimensions :
- accuracy
- completeness
- latency
- auditability
evidence_hooks :
- meter_records
- reconciliation
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
- id : commerce.billing
name : Billing
purpose : Calculate amounts owed based on contracts, pricing rules, entitlements, metering, or events.
anchors : [ ]
profiles :
- subscription
- usage-based
- one-time
- hybrid
quality_dimensions :
- accuracy
- explainability
- reconciliation
- currency_support
evidence_hooks :
- invoice_tests
- billing_reconciliation
may_use :
- commerce.metering
- commerce.entitlement
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
- id : commerce.payment
name : Payment
purpose : Transfer monetary value between parties.
anchors : [ ]
profiles :
- card
- sepa
- bank-transfer
- wallet
- payout
- recurring
quality_dimensions :
- success_rate
- settlement_time
- currency_support
- refund_support
evidence_hooks :
- payment_records
- settlement_reconciliation
may_use :
- identity.authentication
- operations.audit
- integration.api
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
- id : commerce.entitlement
name : Entitlement
purpose : Determine which products, features, capacities, or service levels a customer or actor is
contractually allowed to use.
anchors :
- model/access-control
profiles :
- feature
- capacity
- plan
- time-bound
quality_dimensions :
- decision_latency
- consistency
- auditability
evidence_hooks :
- entitlement_tests
- decision_records
may_use :
- identity.authorization
- id : intelligence
name : Intelligence
navigation_only : true
capabilities :
- id : intelligence.generation
name : Generation
purpose : Produce novel information representations from context or instructions.
anchors : [ ]
profiles :
- text
- image
- audio
- video
- code
- structured-data
quality_dimensions :
- quality
- latency
- cost
- safety
2026-08-15 18:19:30 +02:00
- intelligence_intensity
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
evidence_hooks :
- evaluation_results
- latency_metrics
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
- id : intelligence.extraction
name : Extraction & Classification
purpose : Derive structured information, labels, attributes, or classifications from input.
anchors : [ ]
profiles :
- ocr
- document-extraction
- entity-extraction
- classification
- speech-recognition
quality_dimensions :
- accuracy
- recall
- precision
- latency
2026-08-15 18:19:30 +02:00
- intelligence_intensity
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
evidence_hooks :
- evaluation_results
- golden_set_tests
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
- id : intelligence.embedding
name : Semantic Representation
purpose : Produce machine-usable semantic representations of information.
anchors : [ ]
profiles :
- text
- image
- multimodal
quality_dimensions :
- dimensionality
- semantic_quality
- latency
- cost
2026-08-15 18:19:30 +02:00
- intelligence_intensity
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
evidence_hooks :
- retrieval_benchmarks
- latency_metrics
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.
- id : intelligence.retrieval
name : Semantic Retrieval & Ranking
purpose : Select or rank information according to semantic relevance.
anchors :
- model/information-space
profiles :
- vector
- reranking
- hybrid
- multimodal
quality_dimensions :
- recall
- precision
- ranking_quality
- latency
2026-08-15 18:19:30 +02:00
- intelligence_intensity
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
evidence_hooks :
- retrieval_benchmarks
may_use :
- intelligence.embedding
- data.search
- id : intelligence.reasoning
name : Reasoning & Decision
purpose : Derive judgments, plans, decisions, hypotheses, or action proposals from context and constraints.
anchors : [ ]
profiles :
- analysis
- planning
- decision
- agentic
quality_dimensions :
- task_success
- reliability
- latency
- cost
- explainability
2026-08-15 18:19:30 +02:00
- intelligence_intensity
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
evidence_hooks :
- task_evaluations
- decision_records
may_use :
- intelligence.retrieval
anchor_note : No anchoring canon model yet — new canon surface. See assimilation open question OQ-5.