Reconcile T06 calibration and risk disposition

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a05e30-2884-71b0-98d7-7edd16ae737b
This commit is contained in:
tegwick 2026-09-02 13:10:07 +02:00
parent b3fd044f55
commit 774f69ff80
5 changed files with 66 additions and 26 deletions

View file

@ -1,7 +1,7 @@
# Conformance disposition — kings-guard qonto live observation
**Repository:** gate-house
**Status:** reviewed; implementation finding routed to risk-nexus
**Status:** reviewed; implementation finding registered as RISK-F-0011
**Date:** 2026-09-02
**Contract:** `posture-findings-return.v1`
**Source:** State Hub message `23480b81-bc34-4df4-92cc-840fbc8514fd`
@ -33,8 +33,13 @@ 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`:
King's Guard returned `audit.deny` as load-bearing because qonto-assistant's
escalation loop branches on denies. Risk Nexus's current-source check narrowed
that rationale: `DenyEscalationTracker` is in-process on the decision path,
while `AuditLogger.emit` is a parallel record. A missing audit line would not
disable qonto-assistant's local lockout. The emitted stream is nevertheless
load-bearing for estate observation because King's Guard consumes it. Its
stream completeness is `unknown`:
- no heartbeat or emission-cadence declaration is published;
- no reconciliation view was supplied;
@ -79,11 +84,13 @@ 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.
The implementation finding was also routed through risk-nexus in message
`53645a75-0215-4261-a700-f7aedf09e7e8`. Gate House supplied facts and safe
evidence references, assigned no severity, and requested a finding/note record
or an explicit rejection. Risk Nexus owns grading and remediation tracking;
qonto-assistant continues to own any fix.
The implementation finding was routed through risk-nexus in message
`53645a75-0215-4261-a700-f7aedf09e7e8` and registered as `RISK-F-0011` under
`RISK-RULING-2026-09-02-A`: `medium` (`I2` × `L3`), public, open, no
escalation. Risk Nexus owns grading and remediation tracking; qonto-assistant
continues to own any fix. The source-check clarification changes the stated
load-bearing rationale, not Gate House's `no_change` doctrine disposition or
the bounded completeness finding.
## Review triggers