From 7b9c96b2c70bac7e72a91f3021b358826835d2a3 Mon Sep 17 00:00:00 2001 From: codex Date: Fri, 24 Jul 2026 00:34:52 +0200 Subject: [PATCH] Close absorbed qonto pilot intake --- ...6-07-23-qonto-assistant-pilot-candidate.md | 23 ++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/intake/2026-07-23-qonto-assistant-pilot-candidate.md b/intake/2026-07-23-qonto-assistant-pilot-candidate.md index 8d0921e..80be54f 100644 --- a/intake/2026-07-23-qonto-assistant-pilot-candidate.md +++ b/intake/2026-07-23-qonto-assistant-pilot-candidate.md @@ -3,7 +3,8 @@ title: "qonto-assistant as a pilot-lane candidate for KG-WP-0002-T04" origin: "qonto-assistant docs/SecurityPractice.md" origin_ref: "QONTO-WP-0004" lane: green -status: open +status: closed +outcome: absorbed state_hub_intake_id: "019f90c8-2d56-7897-858c-03b463791797" --- @@ -88,6 +89,26 @@ consume with no rework on its side: contract stabilization is the ask, not bounded-response implementation (that is `KG-WP-0002-T04`'s own scope to define, if this lane is chosen). +## Resolution + +Closed on 2026-07-23 as `absorbed` by `KG-WP-0002`. + +The intake's requested work is now implemented in this repo: + +- `specs/ImmuneContracts.md` and `src/kings_guard/contracts.py` provide the + first canonical contract layer that `qonto-assistant` can target. +- `docs/AdjacentSystemBoundary.md` explicitly names governed domain assistants + such as `qonto-assistant` in the adjacent-system boundary. +- `docs/pilots/QontoAssistantPosturePilot.md` selects `qonto-assistant` as the + first pilot lane and defines the bounded request/response flow. +- `src/kings_guard/adapters/qonto_assistant.py`, + `src/kings_guard/posture.py`, and `tests/` implement and verify the initial + normalized observation -> posture -> advisory signal path. + +No separate follow-on work record is needed for this intake itself. Future work +should start from a new intake or workplan for the next lane beyond +`KG-WP-0002`. + ## References - `qonto-assistant/docs/SecurityPractice.md`