From 9de170ecf9705a611bc410b1d75000381802a925 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 20 Sep 2026 23:59:17 +0200 Subject: [PATCH] Recheck the adoption gate and verify it is ready (INFO-WP-0019-T06) No change in the evidence: feedback/ holds only the two 2026-08-15 resource-control reports, incoming/ only its README, and no inbox message is an emission-cadence declaration. The sole declaration in the repository is still the worked example, which the standard states is not source-owned. What this repository owes the gate was re-tested rather than assumed. emission-review validates an arbitrary source-owned declaration and reports operational_truth_assessed false, so a submission cannot be read as observed behaviour, and export-emission-contract produces a bundle whose manifest carries the gate in words at digest 972c0b6701d1693f, which a source owner can pin to today. The blocker is not readiness but that no external source owner has been asked. The contract came from the King's Guard taxonomy with evidence classes owned by NetKingdom, which makes netkingdom the obvious first source owner and a second one that must be independent of it. Soliciting them is an outward action this workplan does not authorize, so T06 stays waiting on that decision. Co-Authored-By: Claude Opus 5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 3588@bnt-lap001 Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da --- ...NFO-WP-0019-conformance-and-maintenance.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/workplans/INFO-WP-0019-conformance-and-maintenance.md b/workplans/INFO-WP-0019-conformance-and-maintenance.md index 0d7a4d2..4222642 100644 --- a/workplans/INFO-WP-0019-conformance-and-maintenance.md +++ b/workplans/INFO-WP-0019-conformance-and-maintenance.md @@ -110,6 +110,32 @@ capability reports. Neither supplies independent emission-cadence declarations or the required pinned consumer results. T06 remains waiting; boundary review is handled separately in INFO-WP-0026. +2026-09-20 recheck: no change in the evidence, and the gate is verified ready. + +`feedback/` still holds only the two 2026-08-15 resource-control capability +reports. `incoming/` holds only its README. The inbox carries eleven messages, +the most recent a 2026-06-27 concept contribution from ops-warden; none is an +emission-cadence declaration. The only declaration in the repository remains +`standards/emission-cadence/examples/qonto-assistant.yaml`, which the standard +itself states is not the source-owned declaration and makes no claim about live +emission. + +What this repository owes the gate is in place and was re-tested rather than +assumed. `emission-review` validates an arbitrary source-owned declaration +against the named schema and reports `operational_truth_assessed: false`, so a +submission cannot be mistaken for observed behaviour. +`export-emission-contract` produces a content-addressed bundle whose manifest +carries the gate in words — "Two independent source-owned implementations +required; example does not count" — at digest `972c0b6701d1693f`. A source owner +can pin to that digest today. + +The blocker is therefore not readiness. It is that no external source owner has +been asked. The contract came from the King's Guard taxonomy and the evidence +classes remain owned by NetKingdom, which makes `netkingdom` the obvious first +source owner; a second must be independent of it. Asking them is an outward +action this workplan does not authorize, so T06 stays `wait` until the operator +decides whether to solicit declarations, and from whom. + ## Implementation notes T01–T04 implemented in `contracts.py`, `maintenance.py`, `paths.py`, CLI,