coulomb/railiance-platform
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish RPF-WP-0059: independent Qonto readback captured; collector silent since 2026-10-15 20:36Z.
All checks were successful
CCR intake gate / gate (push) Successful in 4m14s
Details
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 4s
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 236506@bnt-lap001
Assistant-Session: 09087018-91e1-48c5-ab2f-acfbb62c92e4
This commit is contained in:
codex 2026-11-03 22:01:07 +01:00
parent 22cfdb72e4
commit 3a68eaca8a
3 changed files with 125 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

35
workplans/RPF-WP-0059-hourly-cadence-receiver-custody.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Admit hourly receiver cadence and exact Qonto collector custody"
domain: financials
repo: railiance-platform
status: active
status: finished
owner: codex
topic_slug: railiance-platform
created: "2026-10-15"
@ -64,9 +64,8 @@ resume on interruption. No live effect or secret read occurred in preparation.
```task
id: RPF-WP-0059-T04
status: wait
status: done
priority: high
blocking_reason: "Independent reconciliation needs an audit-core release containing d46e89e (AUDIT-WP-0013-T06); the deployed b479801b refuses independent readers with source_not_allowed. Founder-run release: AUDIT-WP-0013-T07."
state_hub_task_id: "7d8e5315-9470-5596-a865-d451284f6f50"
```
@ -119,3 +118,33 @@ Git in `~/cadence-readback/`. Rerun the same command after AUDIT-WP-0013-T07.
A new receiver release will also move the reviewed image pin in
`scripts/audit-core-recovery-preflight.py` (RAILIANCE-WP-0024 owner contract)
again, so the next attended recovery window needs a fresh owner round.
### Independent readback captured; collector silent — 2026-11-03
After AUDIT-WP-0013-T07 released receiver `sha256:304cfb83…` (built from
audit-core `8185893`, which contains `d46e89e`), the founder reran the
readback, and it completed (`independent_custody_readback_complete`; reader
`operator`, basis `independent_reader`, no credential emitted).
Results for instance `b351fa6b…`, window 2026-10-15T19:36Z to
2026-11-03T21:00Z:
- Reconciliation counts only 2 `audit-core.heartbeat` and 1 `audit.deny`.
- The source-global stream finding is `missing_heartbeat` for sender
`rapp-qonto-collector`, class `audit.deny`, last seen
2026-10-15T20:36:30Z, overdue by 1,632,236 s (about 18.9 days).
- The exact-id reads of sequence 1 and 2 match source, tenant, instance and
sequence.
The collector heartbeated once after the first hour and then stopped. No
collector instance has emitted for this source since. This is the observer
finding the evidence exists to produce, and it belongs to the Qonto runtime
owner. Platform custody, the receiver and the finding surface worked. Receipt:
`docs/evidence/2026-11-03-qonto-independent-readback/qonto-independent-readback.json`
(sha256 `959a1112…555a`).
By founder decision, Platform's T04 part (coordination and the independent
capture) is done and RPF-WP-0059 is finished. Operational acceptance and the
silence finding are handed to King's Guard (KG-WP-0005-T03), Qonto
(QONTO-WP-0006-T03) and the runtime owner (rapp-qonto). Profile acceptance is
not claimed: the evidence is negative until the collector is restored and
re-observed.