Admit source evidence snapshots and harden stream completeness

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06e89-93a2-7aa2-82b3-ce5ccd2682e6

workplans/ADHOC-2026-09-04.md

@@ -0,0 +1,34 @@
+---
+id: KG-WP-ADHOC-2026-09-04
+type: workplan
+title: "2026-09-04 repository consistency maintenance"
+domain: infotech
+repo: kings-guard
+status: finished
+owner: codex
+topic_slug: netkingdom
+created: "2026-09-04"
+updated: "2026-09-04"
+finished: "2026-09-04"
+---
+
+# 2026-09-04 Repository Consistency Maintenance
+
+## Reconcile the accepted layer declaration and the shipped secret-use surface
+
+```task
+id: KG-WP-ADHOC-2026-09-04-T01
+status: done
+priority: low
+```
+
+The completed KG-WP-0004 sweep left current boundary prose and checker
+commentary pointing at v0.6 while the authoritative declaration and architecture
+already use accepted v0.7. Align those references and make `SCOPE.md` say
+explicitly that containment is proposed rather than owned.
+
+Also consume the 2026-09-04 coordination update from `secrets-engine`: record
+that its non-secret `secret-use snapshot` surface and 1d heartbeat declaration
+have shipped. Observation-input admission changes a posture lane and requires
+mapping and contract decisions, so hand that residual to live intake
+`KG-IN-0004` rather than silently treating the unmodeled surface as consumed.

workplans/KG-WP-0005-qonto-source-cadence-admission.md

@@ -0,0 +1,71 @@
+---
+id: KG-WP-0005
+type: workplan
+title: "Admit and validate qonto-assistant source completeness evidence"
+domain: infotech
+repo: kings-guard
+status: active
+owner: codex
+topic_slug: netkingdom
+created: "2026-09-04"
+updated: "2026-09-05"
+origin: cross-repo
+origin_ref: QONTO-WP-0005
+---
+
+# Admit and Validate Qonto-Assistant Source Completeness Evidence
+
+Qonto-assistant has shipped the source-side contract requested by KG-WP-0003:
+source-owned cadence, instance and sequence fields, startup/periodic/shutdown
+heartbeats, and a reconciliation view. Kings-guard must consume and validate
+those claims without confusing source transition counts with authorization or
+claiming completeness beyond an observed process instance.
+
+## Consume source-emitted observation context
+
+```task
+id: KG-WP-0005-T01
+status: done
+priority: high
+```
+
+Prefer source-emitted `identity_binding` and `egress_destination` over legacy
+normalization hints, retain the hints for old records, and prove the live
+mapping does not drift.
+
+## Validate cadence, heartbeat, sequence, and reconciliation locally
+
+```task
+id: KG-WP-0005-T02
+status: done
+priority: high
+```
+
+Consume the source-owned cadence separately from kings-guard's Taxonomy draft.
+Drive qonto-assistant's real AuditLogger emit path, require one stream instance
+with contiguous sequence numbers, translate heartbeat claims, compare source
+transition counts with captured request evidence, and prove the resulting deny
+stream evaluates complete without findings.
+
+## Validate the deployed stream
+
+```task
+id: KG-WP-0005-T03
+status: wait
+priority: medium
+```
+
+Observe an authorized deployed qonto-assistant process from startup through at
+least one allow/deny transition and reconciliation read. Confirm the deployed
+configuration emits periodic heartbeats at the declared interval, preserves
+sequence/instance semantics, and produces no unexplained divergence. This is
+operational evidence; the local source-path proof does not substitute for it.
+
+**Review 2026-09-05:** Local source-path tests pass with source context,
+heartbeat counters, sequence and reconciliation checks. The canonical cadence
+fixture migration and rejection-path hardening are tracked in KG-WP-0006.
+T03 remains waiting: the source workplan explicitly leaves deployment with the
+runtime owner; this repository supplies no authorized deployed stream endpoint
+or process-lifecycle observation route. Required input is a runtime-owner
+capture from startup, a request transition, periodic heartbeat timing, and a
+same-instance reconciliation snapshot. No cluster or Tooling client was used.

workplans/KG-WP-0006-observation-input-review.md

@@ -0,0 +1,77 @@
+---
+id: KG-WP-0006
+type: workplan
+title: "Review and admit canonical cadence and secret-use snapshot inputs"
+domain: infotech
+repo: kings-guard
+status: finished
+owner: codex
+topic_slug: netkingdom
+created: "2026-09-05"
+updated: "2026-09-05"
+origin: cross-repo
+origin_ref: KG-IN-0004
+---
+
+# Observation input review
+
+## Migrate the cadence consumer to the published generic contract
+
+```task
+id: KG-WP-0006-T01
+status: done
+priority: high
+```
+
+Consume InfoTechCanon standard/emission-cadence 0.1. Move profile and
+provenance fields into namespaced extensions; validate examples against the
+owner's schema without copying it. Keep the handover draft historical.
+
+## Harden Qonto stream admission and completeness checks
+
+```task
+id: KG-WP-0006-T02
+status: done
+priority: high
+```
+
+Reject mismatched instances, malformed sequences and counters; preserve missing
+context; prevent absent reconciliation fields or unrelated/future heartbeats
+from manufacturing completeness. Cover failure paths with regression tests.
+
+## Admit secret-use snapshots with explicit scope and unknown completeness
+
+```task
+id: KG-WP-0006-T03
+status: done
+priority: medium
+```
+
+Map the Engine envelope into a separate snapshot observation: it has no event
+actor, event timestamp, or authorization outcome. Require explicit lane scope,
+retain only typed metadata, preserve omitted evidence fields, translate the
+heartbeat interval as a freshness bound, and never promote snapshot freshness
+to stream completeness. Record residual source evidence needed for posture.
+
+## Completion evidence
+
+Reviewed the original pending Qonto implementation and added negative-path
+coverage for scoped streams, absent/invalid counters, snapshot instance binding,
+sequence validation, and heartbeat reconciliation. Both migrated fixtures pass
+InfoTechCanon's external schema 0.1. Snapshot mapping and limitations are in
+`docs/SecretUseSnapshotAdmission.md`.
+
+Residual KG-IN-0005 was recorded before completion for secret-use event
+provenance and operational evidence. Deployed Qonto acceptance remains explicitly
+waiting in KG-WP-0005-T03; local source-path tests do not close it. The NetKingdom
+profile remains proposed in its owner's repository; no adoption is asserted.
+
+Validation: 78 tests passed (including external canonical schema and local
+Qonto emit-path tests), lint and layer conformance passed, pilot demo passed,
+and `git diff --check` was clean. Decision: KG-DEC-2026-003.
+
+State Hub: decision KG-DEC-2026-003 was recorded successfully. Two required
+`statehub fix-consistency --repo kings-guard` attempts (including an unrestricted
+retry) failed with C-00: repository API lookup timed out. Workplan/intake files
+remain authoritative; the operator must rerun synchronization when the repository
+lookup is available. This is a synchronization failure, not implementation evidence.