coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Finish ITC-WP-0013 (AttributeValueType under ITC-DATA) and ITC-WP-0014
T02/T03/T05/T06/T07. Capability contract schemas, live-catalog review
CLI, landscape/kernel-map pointers. Sit on this version.
This commit is contained in:
tegwick 2026-08-15 19:42:30 +02:00
parent 7805560a60
commit d453e17952
44 changed files with 1485 additions and 137 deletions
Download patch file Download diff file Expand all files Collapse all files

30
workplans/ITC-WP-0014-capability-model-consolidation.md
View file

@ -5,7 +5,7 @@ title: "Capability Model consolidation (post-ITCC assimilation)"
domain: infotech
topic_slug: canon
repo: info-tech-canon
status: active
status: finished
priority: medium
created: "2026-08-14"
updated: "2026-08-15"
@ -62,7 +62,7 @@ and `governance` (2); no capability id changed. Decision record in
```task
id: ITC-WP-0014-T02
status: todo
status: done
priority: high
depends_on: [T01]
state_hub_task_id: "1ed8d07a-34ee-4ad4-8e4a-03a513c14836"
@ -77,11 +77,16 @@ rows require EvidenceBasis (CAP-R10); provisions may declare
in the model prose until a companion requirement/provision schema is
justified. §10.3 is already met by the resource-control join.
**Done 2026-08-15 (canon 0.6.0):** `capability.schema.yaml` validates the
catalog; `capability-record.schema.yaml` is the companion record shape.
`make validate` checks the catalog contract (no typical_resource_classes;
classes carry native_unit / supply / capacity_behaviour).
### T03 — Formal mapping artifacts for each anchor
```task
id: ITC-WP-0014-T03
status: todo
status: done
priority: medium
depends_on: [T02]
state_hub_task_id: "e0ad8ec8-fdf2-4238-888c-af052fcddd40"
@ -90,6 +95,9 @@ 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`.
**Done 2026-08-15:** `infospace/mappings/capability-anchors.yaml` holds one
entry per source/target pair, registered as `mapping/capability-anchors`.
### T04 — Small-SaaS capability requirement set
```task
@ -109,7 +117,7 @@ validates against the live catalog (T11).
```task
id: ITC-WP-0014-T05
status: todo
status: done
priority: medium
depends_on: [T01]
state_hub_task_id: "339d2006-d1c8-4572-b559-e6ceb7b06c45"
@ -119,11 +127,14 @@ Revise `InfoTechCanonLandscapeModel` §11.4 (the deferred strategy/capability no
to reference ITC-CAP, and add the capability model to
`InfoTechCanonKernelMap`.
**Done 2026-08-15:** §11.4 now points at ITC-CAP; Kernel Map §4.14 owns
abilities.
### T06 — Requirement/provision validation in the service surface
```task
id: ITC-WP-0014-T06
status: todo
status: done
priority: low
depends_on: [T02]
state_hub_task_id: "530f86c2-b61b-4b54-b380-8eec92bdced1"
@ -133,11 +144,15 @@ 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.
**Done 2026-08-15:** `info-tech-canon capability-review PATH` and
`GET /capability-review?path=` join a consumer record to the live catalog
(CAP-R8–R11).
### T07 — Promotion review
```task
id: ITC-WP-0014-T07
status: todo
status: done
priority: medium
depends_on: [T01, T02, T03, T11]
state_hub_task_id: "455690e3-c39a-4926-a13b-a179b134b2a4"
@ -147,6 +162,9 @@ Promote the model from `proposed` to `draft` or `release-candidate`, bump the
canon version, and write the `CHANGELOG.md` entry. T04 (small-saas illustration)
is no longer a promotion dependency.
**Done 2026-08-15:** ITC-CAP promoted to `draft` in canon 0.6.0. This is
the freeze version. T04 remains an optional illustration.
### T08 — Finding A: move resource-class declaration off the contract
```task