tegwick
680ed8b4b1
Security & Governance splits into `security` (secrets, keys, policy, vulnerability) and `governance` (evidence, lifecycle). Every capability id is unchanged — domains are navigation_only, so this is a table-of-contents change, not a concept change. - capabilities.yaml: 41 capabilities across 9 domains - ITC-CAP §8 catalog table and promotion gate updated - OQ-2 closed; decision record added to ASSIMILATION.md - canon 0.2.0 -> 0.2.1 (patch) + CHANGELOG entry - ITC-WP-0014 T01 done, workplan active make validate: ok. make test: 22 passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
4.2 KiB
| id | type | title | domain | topic_slug | repo | status | priority | created | updated | depends_on_workplans | owner | spec_refs | state_hub_workstream_id | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ITC-WP-0014 | workplan | Capability Model consolidation (post-ITCC assimilation) | infotech | canon | info-tech-canon | active | medium | 2026-08-14 | 2026-08-15 |
|
claude |
|
18cccc77-5aef-48f2-91d6-124bd439285a |
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)
id: ITC-WP-0014-T01
status: done
priority: high
state_hub_task_id: "4074193b-04dc-4168-b7af-f42e94417321"
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.
Done 2026-08-15 (canon 0.2.1): navigation domain split into security (4)
and governance (2); no capability id changed. Decision record in
assimilation/it-capability-canon/ASSIMILATION.md; OQ-2 closed.
T02 — Publish capability.schema.yaml
id: ITC-WP-0014-T02
status: todo
priority: high
depends_on: [T01]
state_hub_task_id: "1ed8d07a-34ee-4ad4-8e4a-03a513c14836"
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
id: ITC-WP-0014-T03
status: todo
priority: medium
depends_on: [T02]
state_hub_task_id: "e0ad8ec8-fdf2-4238-888c-af052fcddd40"
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
id: ITC-WP-0014-T04
status: todo
priority: medium
depends_on: [T02]
state_hub_task_id: "182e0ad5-5fb9-4d50-9576-b9f5fdff91d3"
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
id: ITC-WP-0014-T05
status: todo
priority: medium
depends_on: [T01]
state_hub_task_id: "339d2006-d1c8-4572-b559-e6ceb7b06c45"
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
id: ITC-WP-0014-T06
status: todo
priority: low
depends_on: [T02]
state_hub_task_id: "530f86c2-b61b-4b54-b380-8eec92bdced1"
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
id: ITC-WP-0014-T07
status: todo
priority: medium
depends_on: [T01, T02, T03, T04]
state_hub_task_id: "455690e3-c39a-4926-a13b-a179b134b2a4"
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.