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

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

View file

@ -15,6 +15,41 @@ semantics.
---
## 0.6.0 — 2026-08-15
### Frozen — ITC-CAP draft; AttributeValueType catalog; joinable review
**Change.** Canon 0.6.0 is the freeze cut.
- **ITC-CAP** promoted from `proposed` to `draft`. Contract schemas
published: `capability.schema.yaml` (catalog) and
`capability-record.schema.yaml` (requirement/provision records).
`make validate` enforces CAP-R8 on the catalog.
- **Capability-review surface:** `info-tech-canon capability-review PATH`
and `GET /capability-review?path=` join a consumer record to the live
catalog (OQ-6 / ITC-WP-0014 T06).
- **Mappings:** `infospace/mappings/capability-anchors.yaml` formalizes
the assimilation mappings (T03).
- **Landscape §11.4** and **Kernel Map §4.14** now point at ITC-CAP (T05).
- **AttributeValueType** catalog under ITC-DATA
(`models/data/attribute-value-types.yaml`) from
`demand/AttributeValueTypes.md` (ITC-WP-0013). citation-evidence
alignment note published.
ITC-WP-0013 and ITC-WP-0014 are finished. T04 (small-saas illustration)
remains optional and does not block the freeze.
**Rationale.** One consumer cycle has refined the capability model; a
second consumer needed a closed capture-type catalog. Further shape
change of ITC-CAP needs a new minor. 0.6.0 is the version to sit on.
**Breaking:** no capability id or AttributeValueType id invented as a
break. New catalogs and schemas only.
**Validation.** `make validate` 0 errors / 0 warnings; `make test` 23 passed.
---
## 0.5.0 — 2026-08-15
### Added — Provision-to-provision relationships (`uses_provisions`)