Implement canon conformance and maintenance optimizations
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06e82-3e08-7042-a79d-438ac6eed8db
This commit is contained in:
tegwick 2026-09-05 00:50:09 +02:00
parent a2e7f22d8d
commit b081d39da1
64 changed files with 4491 additions and 373 deletions

View file

@ -15,6 +15,45 @@ semantics.
---
## 0.7.0 — 2026-09-04
### Added — ecosystem-wide EmissionCadenceDeclaration contract
**Change.** Added the draft `ITC-EMISSION-CADENCE` standard and JSON Schema
contract version `0.1`. The contract defines source-authored expected-rate,
heartbeat, and reconciliation cadence semantics, namespaced profile extensions,
strict form validation, and compatibility rules. A schema-valid
`qonto-assistant` worked example demonstrates both forms without claiming to be
the source-owned live declaration.
**Ownership.** InfoTechCanon owns the generic forms, fields, validation, and
evolution under `GH-DEC-2026-004`. NetKingdom owns its importing security
profile, including evidence-class policy and stronger requirements for rare
load-bearing streams. Sources own instances; observers own evaluation and
findings.
**Rationale.** Stream silence cannot be evaluated from event contents alone,
and a Staff-layer consumer must not own the Taxonomy contract it evaluates.
The split preserves one owner per semantic layer without turning NetKingdom
security doctrine into an ecosystem-wide rule.
**Provenance.** King's Guard draft 0.1.0, frozen under
`assimilation/emission-cadence`; disposition `adapt`; `ITC-WP-0018`.
**Breaking:** no. This is a new draft artifact and schema.
**Validation.** The built-in example is checked against JSON Schema Draft 2020-12;
negative tests cover missing/ambiguous windows, missing intermittent mechanisms,
and unnamespaced profile fields. `make validate` reports 0 errors and 0 warnings;
`make test` passes 29 tests.
**Completed illustration.** The Small-SaaS profile now includes the optional
ITC-CAP requirement/provision record left by `ITC-WP-0014-T04`. Its four
requirements are joined to catalog-valid provisions and evidence and meet their
declared maturity floors.
---
## 0.6.0 — 2026-08-15
### Frozen — ITC-CAP draft; AttributeValueType catalog; joinable review