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

Diagnose attended custody finish failures with safe staged receipts
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1029d-2c93-7500-a0e0-e3e089668b29
This commit is contained in:
codex 2026-10-03 21:08:56 +02:00
parent b8f8a7ada6
commit 33ff82210e
8 changed files with 397 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/RPF-WP-0049-platform-root-custody-record-delivery.md
View file

@ -190,3 +190,14 @@ owner baseline and direct governed history provider roundtrip receipt. No new
generic approval, storage service or credential is requested. If the historical
exposed grant matches current lane, existing coordinated owner incident flow
must resolve it before backup proof; authority remains no-grant meanwhile.
## Failed finish diagnosed safely — 2026-10-03
First attended finish child failed without a receipt. Audit verifies all three
OpenBao reads succeeded; provider failure boundary was not retained. Corrected
stdlib startup bootstrap and full-main stage/error receipts eliminate that gap;
closed diagnostic allowlist preserves secret suppression. No IAM change or
provider protocol relaxation is made. Private full-main tests with actual age
and fake owner/provider I/O verify success and each meaningful failure boundary.
T05 still waits on actual governed provider roundtrip; exact command unchanged,
with a fresh receipt path mandatory.