CUST-WP-0075: reconcile owner waits and decision routing

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a10391-6355-7b41-b0fa-3e14e874f091
This commit is contained in:
tegwick 2026-10-04 00:48:22 +02:00
parent e3f5f1b42a
commit cc5eab2e44

View file

@ -8,7 +8,7 @@ status: blocked
owner: codex
topic_slug: qonto-canonical-cadence-adoption
created: "2026-10-03"
updated: "2026-10-03"
updated: "2026-10-04"
state_hub_workstream_id: "d6ed8fec-06a4-504d-8119-80575d87afbf"
---
@ -46,6 +46,7 @@ status: wait
priority: high
blocking_reason: "Runtime owner and audit-core must supply the structured-stdout delivery binding, accepted-class mapping and sender receipts. No actual audit-core sender exists in this source implementation."
state_hub_task_id: "77af5db4-8919-5da7-ab91-924a5f8ad63f"
blocked_on: message-from:audit-core
```
Qonto runtime owner must provide the pinned collector/sender implementation,
@ -78,8 +79,11 @@ A source fixture or stdout event alone does not close this task.
id: QONTO-WP-0006-T03
status: wait
priority: high
blocking_reason: "King's Guard requires actual sender/mapping proof before independent missing-heartbeat, gap and count-divergence acceptance."
state_hub_task_id: "9eb725b2-a9bc-594a-b43b-e24c37dfc6a1"
blocking_reason: King's Guard requires actual sender/mapping proof before independent missing-heartbeat, gap and count-divergence acceptance.
state_hub_task_id: 9eb725b2-a9bc-594a-b43b-e24c37dfc6a1
depends_on:
- QONTO-WP-0006-T02
- KG-WP-0005-T03
```
King's Guard must consume the canonical declaration and owner inventory, bind
@ -111,3 +115,37 @@ zero MUST/SHOULD findings. Exact source-owned assertions: `--attributive audit.a
`6d52692eb1e4d1325e0d6062d95acded98beddaae5bcfe24c6f0e91f1b6be6ae`;
reviewed contract/schema revision `4d0851c3fca306538b53838421f4499baf352778`.
This is static source adoption, not live runtime or observer acceptance.
## Wait reconciliation — 2026-10-04
T02 now names the audit-core owner-return for actual Qonto sender admission
and accepted-class/count mapping. No matching Qonto sender commitment ID was
found in current audit-core workplans; request and record its real owner ID
before replacing this qualifier. Runtime collector/delivery remains rapp-qonto
owned. Finished RAPP-QONTO-WP-0003 proves the historical sequenced source
rollout and captured-event checks, explicitly leaving independent collector
acceptance open; it is not a new sender commitment or receiver receipt.
T03 depends on T02 and names kings-guard for independent operational observer
acceptance. Finished KG-WP-0003-T07 is the historical source-event pilot, not
current canonical sender/mapping evidence. AUDIT-WP-0011 registers Informed
Decision, not Qonto. Neither terminal record is used as an unsatisfied blocker.
The owner-return must identify a new scoped record or a concrete accepted
extension, rather than assign ownership in this source repo. No owner may
wait on Qonto T03 to deliver T02 sender/mapping evidence; the order is runtime
collector plus audit-core admission/mapping, then independent kings-guard
observation, then Qonto records T03 acceptance. Both tasks remain wait.
No sender, deployment, bank API access or completeness claim is introduced.
## Observer owner commitment correction — 2026-10-04
Current kings-guard owner record KG-WP-0005-T03 already holds deployed-stream
acceptance, including actual receiver read/mapping receipts. T03 therefore
links that real owner task alongside QONTO-WP-0006-T02, replacing the provisional
kings-guard owner-return qualifier. KG-WP-0005-T03 waits for runtime-owner
captures and receiver evidence; Qonto T02 coordinates that input. Neither
owner waits on Qonto T03 completion to supply its evidence. This records the
existing commitment and requests no new scope or live action. The earlier
provisional owner-return note is superseded for observer task identity only.