From 78ee1c0b8ac581edc2911f0ec11a8bbbe276915c Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 1 Sep 2026 20:48:33 +0200 Subject: [PATCH] Record GH-WP-0001-T06 handoff and wait gate Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a05e30-2884-71b0-98d7-7edd16ae737b --- .../2026-09-01-conformance-loop-handoff.md | 85 +++++++++++++++++++ workplans/GH-WP-0001-foundation.md | 12 ++- 2 files changed, 96 insertions(+), 1 deletion(-) create mode 100644 history/2026-09-01-conformance-loop-handoff.md diff --git a/history/2026-09-01-conformance-loop-handoff.md b/history/2026-09-01-conformance-loop-handoff.md new file mode 100644 index 0000000..a84595a --- /dev/null +++ b/history/2026-09-01-conformance-loop-handoff.md @@ -0,0 +1,85 @@ +# Conformance-loop handoff + +**Repository:** gate-house +**Project family:** NetKingdom +**Status:** Handoff complete; first loop return pending +**Date:** 2026-09-01 +**Workplan:** GH-WP-0001-T06 +**Artifact commit:** `8cb7250` + +## What Gate House published + +- `docs/assurance/asm-t01-t10-executable-targets.md` — hostile setup, + observable oracle, evidence, and known-bad calibration for every Canon test; +- `docs/assurance/asm-targets.yaml` — machine-readable T-01…T-10 index; +- `docs/contracts/conformance-reporting.md` — outcome and doctrine-disposition + return contract; +- `docs/contracts/posture-findings-return.md` — posture asymmetry, origin + linkage, stream completeness, and findings return path; +- `docs/conformance/README.md` — Gate House review-register rules and honest + `not_run` initial state. + +## Agreement already in force + +King's Guard accepted the Staff placement, posture asymmetry, and Engine-only +actuation boundary in `KG-DEC-2026-001`. Its `KG-WP-0003-T06` requires +containment proposals to retain observation/signal origin, and T07 requires the +first live observation to be reported to Gate House. The return-path contract +consolidates those accepted and planned obligations; it does not assign a new +responsibility. + +Whitehat-security's layering review note and open `WHITEHAT-IN-0001` name the +split: Gate House specifies T-01…T-10; whitehat-security attacks and judges +whether controls held. The executable-target handoff supplies the missing +specification detail without changing whitehat-security's targeting and +authorization rules. + +## Durable handoffs + +### Whitehat-security + +State Hub message: +`8229c9a4-862f-4d55-842c-5c95702f79d9` + +Requested disposition: + +- triage all ten tests as applicable, not applicable, or pending; +- map or extend whitehat's target representation in its own repository; +- name target surface, known-bad calibration, and report route; +- preserve Canon IDs when revising or splitting a target; +- return every outcome under `conformance-reporting.v1`; +- treat the handoff as no authorization for any fixture or live probe. + +### King's Guard + +State Hub message: +`50d392ad-b342-4e90-85e7-d4c5495f3671` + +Requested disposition: + +- apply or contest the consolidated contract through existing + `KG-WP-0003-T06/T07`; +- preserve posture's restrictive asymmetry and Engine-only actuation; +- return origin-linked posture/findings via the named State Hub envelope; +- report stream completeness separately from record richness. + +## Why T06 is waiting + +Publication and handoff are necessary but do not make the conformance loop +turn. At this point: + +- whitehat-security has not returned a triaged ASM target or calibrated run; +- kings-guard T06/T07 are still open and no live-observation result has + returned under this contract; +- `docs/conformance/` therefore truthfully records `not_run`. + +T06 can move from `wait` to `done` after: + +1. whitehat-security records disposition for the target set and returns at + least one known-bad-calibrated fixture or authorized target outcome; +2. kings-guard confirms or revises the return-path contract and reports the + status of its origin-link/live-observation lane; +3. Gate House records the first returned report's doctrine disposition and + routes every residual to a live owner. + +Anything less would establish document flow, not a conformance loop. diff --git a/workplans/GH-WP-0001-foundation.md b/workplans/GH-WP-0001-foundation.md index de13e4a..3e311bb 100644 --- a/workplans/GH-WP-0001-foundation.md +++ b/workplans/GH-WP-0001-foundation.md @@ -106,7 +106,7 @@ and agent guidance now point to the current document. ```task id: GH-WP-0001-T06 -status: todo +status: wait priority: medium state_hub_task_id: "8cc018e1-2787-5435-9c2c-c2b01cf75ae4" ``` @@ -115,3 +115,13 @@ Close the conformance loop. Hand the assurance specifications T-01…T-10 to whitehat-security as executable targets, agree the posture and findings return path with kings-guard, and establish how conformance review reports back. Until this turns, Gate House is a paper generator by its own falsifier. + +Waiting on the first return — Gate House's side is published at commit +`8cb7250`. The executable target set and reporting contract were handed to +whitehat-security in State Hub message `8229c9a4-862f-4d55-842c-5c95702f79d9`; +the posture/findings contract, grounded in `KG-DEC-2026-001` and `KG-WP-0003`, +was handed to kings-guard in message +`50d392ad-b342-4e90-85e7-d4c5495f3671`. T06 becomes done after a calibrated +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`.