coulomb/gate-house
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Review Whitehat ASM target triage

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a05e30-2884-71b0-98d7-7edd16ae737b
This commit is contained in:
tegwick 2026-09-02 08:16:01 +02:00
parent 78f1d9f06d
commit b3fd044f55
4 changed files with 101 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

14
history/2026-09-01-conformance-loop-handoff.md
View file

@ -143,3 +143,17 @@ required risk-nexus path in message
`53645a75-0215-4261-a700-f7aedf09e7e8`. The route leaves severity and
finding-versus-note classification to risk-nexus and leaves remediation with
qonto-assistant. A resulting risk record or explicit rejection is pending.
Whitehat-security subsequently promoted and closed `WHITEHAT-IN-0002` into
`WHITEHAT-WP-0007` at triage revision `5384f05`. T-01 through T-10 have
individual registrations, known-bad designs, blockers, and result routes. Gate
House accepted the triage and Whitehat's `fixture-asm` / `asm` class split
without revising either Gate House contract. All ten registrations remain
`pending`, so no conformance result exists.
The T-06 blocker did not account for the already-supplied secrets-engine
candidate. Gate House requested a Whitehat-owned sufficiency decision in
message `418fe53b-4a4b-4ebb-909e-62d206cd005f`: admit T-06 as fixture-only and
author the calibration, or preserve `pending` and name the smallest missing
artifact. Review:
`docs/conformance/2026-09-02-whitehat-asm-triage-review.md`.