kings-guard/workplans/KG-WP-0005-qonto-source-cadence-admission.md

76 lines
2.8 KiB
Markdown
Raw Normal View History

---
id: KG-WP-0005
type: workplan
title: "Admit and validate qonto-assistant source completeness evidence"
domain: infotech
repo: kings-guard
status: active
owner: codex
topic_slug: netkingdom
created: "2026-09-04"
updated: "2026-09-05"
origin: cross-repo
origin_ref: QONTO-WP-0005
state_hub_workstream_id: "db9c1dfb-cab3-5887-963a-bfcdf01cff69"
---
# Admit and Validate Qonto-Assistant Source Completeness Evidence
Qonto-assistant has shipped the source-side contract requested by KG-WP-0003:
source-owned cadence, instance and sequence fields, startup/periodic/shutdown
heartbeats, and a reconciliation view. Kings-guard must consume and validate
those claims without confusing source transition counts with authorization or
claiming completeness beyond an observed process instance.
## Consume source-emitted observation context
```task
id: KG-WP-0005-T01
status: done
priority: high
state_hub_task_id: "f65d9f88-2ce3-5b32-b3a0-2395d79c5923"
```
Prefer source-emitted `identity_binding` and `egress_destination` over legacy
normalization hints, retain the hints for old records, and prove the live
mapping does not drift.
## Validate cadence, heartbeat, sequence, and reconciliation locally
```task
id: KG-WP-0005-T02
status: done
priority: high
state_hub_task_id: "4978e781-ad4a-5601-ac18-d67dbab61885"
```
Consume the source-owned cadence separately from kings-guard's Taxonomy draft.
Drive qonto-assistant's real AuditLogger emit path, require one stream instance
with contiguous sequence numbers, translate heartbeat claims, compare source
transition counts with captured request evidence, and prove the resulting deny
stream evaluates complete without findings.
## Validate the deployed stream
```task
id: KG-WP-0005-T03
status: wait
priority: medium
state_hub_task_id: "d2f59a1b-ee01-51b5-b9b6-6e7875d6c988"
```
Observe an authorized deployed qonto-assistant process from startup through at
least one allow/deny transition and reconciliation read. Confirm the deployed
configuration emits periodic heartbeats at the declared interval, preserves
sequence/instance semantics, and produces no unexplained divergence. This is
operational evidence; the local source-path proof does not substitute for it.
**Review 2026-09-05:** Local source-path tests pass with source context,
heartbeat counters, sequence and reconciliation checks. The canonical cadence
fixture migration and rejection-path hardening are tracked in KG-WP-0006.
T03 remains waiting: the source workplan explicitly leaves deployment with the
runtime owner; this repository supplies no authorized deployed stream endpoint
or process-lifecycle observation route. Required input is a runtime-owner
capture from startup, a request transition, periodic heartbeat timing, and a
same-instance reconciliation snapshot. No cluster or Tooling client was used.