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,