Record first GH-WP-0001-T06 posture disposition

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a05e30-2884-71b0-98d7-7edd16ae737b

docs/conformance/2026-09-02-kings-guard-qonto-live-observation.md

@@ -0,0 +1,92 @@
+# Conformance disposition — kings-guard qonto live observation
+
+**Repository:** gate-house
+**Status:** reviewed; residuals routed, acceptance pending
+**Date:** 2026-09-02
+**Contract:** `posture-findings-return.v1`
+**Source:** State Hub message `23480b81-bc34-4df4-92cc-840fbc8514fd`
+**Observer:** kings-guard
+**Observer revision:** `9daea96`
+**Observed source:** qonto-assistant
+**Gate House disposition:** `no_change`
+**Workplan:** GH-WP-0001-T06
+
+## Returned observation
+
+King's Guard completed `KG-WP-0003-T06/T07` and accepted
+`posture-findings-return.v1` without revision.
+
+Real events emitted by `qonto-assistant.audit.AuditLogger` through
+`CapabilityService` reached the evaluator:
+
+- one `org_summary` / REST allow;
+- one `list_transactions` / MCP deny with `arg_constraint`;
+- observation identifiers `req-kg-live-allow` and
+  `req-kg-live-deny-arg-constraint`;
+- signal identifier `sig:req-kg-live-deny-arg-constraint`.
+
+The mapping of request identifier, capability to resource scope, decision, and
+protocol held without adapter drift. Output remained `advisory_only` and
+`metadata_only`. `EffectorRequest` now retains originating observation and
+signal identifiers, stream completeness, and restrictive direction.
+
+## Finding preserved
+
+The `audit.deny` class is load-bearing because qonto-assistant's escalation loop
+branches on it. Its stream completeness is `unknown`:
+
+- no heartbeat or emission-cadence declaration is published;
+- no reconciliation view was supplied;
+- record richness of 90 describes the received deny record, not the stream;
+- no claim is made that every deny was emitted or observed.
+
+This is a finding against source emission completeness, not against the
+received record's mapping and not evidence that an event was suppressed.
+
+The live lane therefore supports only this bounded statement:
+
+> King's Guard observed real qonto-assistant allow and deny events and preserved
+> their origin through advisory output. It cannot yet vouch for completeness of
+> the load-bearing deny stream.
+
+It does not support an estate-wide claim that observation is staffed, or a
+claim that qonto-assistant's deny evidence is complete.
+
+## Doctrine disposition
+
+`no_change`.
+
+The result validates the existing doctrine rather than changing it:
+
+- posture remained restrictive and did not create authority;
+- origin linkage survived into the proposal shape;
+- stream completeness was reported separately from record richness;
+- missing cadence produced an explicit finding rather than optimistic posture;
+- implementation remediation stayed outside Gate House.
+
+Gate House records security-layer-model §12's observation step as **staffed for
+the qonto-assistant lane only**, with completeness explicitly pending.
+
+## Residual routing
+
+| Residual | Owner | Route | State at review |
+| --- | --- | --- | --- |
+| Publish heartbeat plus reconciliation for load-bearing `audit.deny`; optionally emit `identity_binding` and `egress_destination` rather than relying on genome constants. | qonto-assistant | State Hub message `3b9c26a1-ba1a-4189-b439-edd61683aed5` from kings-guard | Delivered, unread; no owning work record observed. |
+| Adopt or decline the emission-cadence declaration as a Taxonomy artifact. | net-kingdom / info-tech-canon | Messages `dd15c0d1-c092-4701-a20a-8f37c6406186` and `5c6868e9-05bc-4970-b5b9-6f777451e15b` | Delivered, unread; ownership decision pending. |
+
+Gate House does not create either repository's task. Until each recipient
+accepts, revises, or rejects its route, these remain pending residuals rather
+than assumed work.
+
+## Review triggers
+
+Re-review when any of the following occurs:
+
+1. qonto-assistant publishes or rejects the heartbeat/reconciliation
+   obligation;
+2. a Taxonomy repository accepts or declines ownership of the declaration;
+3. kings-guard reports a complete-stream observation;
+4. the qonto-assistant event or genome revision changes;
+5. the restrictive posture or origin-link contract changes.
+
+Closing this Gate House review does not close the source finding.

docs/conformance/README.md

@@ -15,5 +15,11 @@ A review record names the external report and safe evidence references, copies
 the executor's outcome without changing it, records Gate House's doctrine
 disposition, and links every residual to a live owner.
 
-No execution reports have returned under these v1 contracts yet. Absence is
+Returned reviews:
-`not_run`, not conformance.
+
+- [`2026-09-02 — kings-guard qonto live observation`](2026-09-02-kings-guard-qonto-live-observation.md):
+  origin-linked advisory observation is staffed for one lane; load-bearing deny
+  stream completeness remains unknown; doctrine disposition `no_change`.
+
+No whitehat-security ASM execution report has returned under
+`conformance-reporting.v1`. That target set remains `not_run`, not conformance.

history/2026-09-01-conformance-loop-handoff.md

@@ -2,7 +2,7 @@
 
 **Repository:** gate-house
 **Project family:** NetKingdom
-**Status:** Handoff complete; first loop return pending
+**Status:** First posture return reviewed; whitehat return pending
 **Date:** 2026-09-01
 **Workplan:** GH-WP-0001-T06
 **Artifact commit:** `8cb7250`
@@ -83,3 +83,22 @@ T06 can move from `wait` to `done` after:
    routes every residual to a live owner.
 
 Anything less would establish document flow, not a conformance loop.
+
+## Progress — 2026-09-02
+
+King's Guard accepted the contract without revision, finished
+`KG-WP-0003-T06/T07`, and returned the first live observation under the
+`[GH-POSTURE]` envelope. Gate House disposition:
+`docs/conformance/2026-09-02-kings-guard-qonto-live-observation.md`.
+
+The qonto-assistant lane is now staffed for observation, not proven complete.
+The load-bearing deny stream has no heartbeat/cadence or reconciliation view,
+so completeness is `unknown`. Residual messages to qonto-assistant,
+net-kingdom, and info-tech-canon were delivered and remain unread.
+
+The whitehat handoff `8229c9a4-862f-4d55-842c-5c95702f79d9` also remains
+unread. Whitehat separately accepted the responsibility boundary with one
+useful correction: Gate House specifies invariants and targets; whitehat
+authors probes. The published target pack already assigns attack design and
+verdict to whitehat, and Gate House explicitly accepted the correction in its
+follow-up.

workplans/GH-WP-0001-foundation.md

@@ -125,3 +125,12 @@ was handed to kings-guard in message
 whitehat result, kings-guard's return-path disposition/status, and Gate House's
 first recorded doctrine disposition. Full record:
 `history/2026-09-01-conformance-loop-handoff.md`.
+
+Progress 2026-09-02 — kings-guard accepted the return-path contract, completed
+`KG-WP-0003`, and returned a real qonto-assistant observation. Gate House
+recorded `no_change`: the lane is staffed, while deny-stream completeness is
+unknown pending heartbeat/reconciliation. Review:
+`docs/conformance/2026-09-02-kings-guard-qonto-live-observation.md`. The
+remaining completion gate is whitehat's unread target-set handoff, a calibrated
+result, and acceptance or explicit rejection of the routed source/Taxonomy
+residuals.