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

Record native receiver custody and prepare actual Approval lifecycle readback
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-astra
Assistant-Session: 01a13eab-1e6a-7b33-9c37-372e90ada3a2
This commit is contained in:
codex 2026-10-15 21:40:48 +02:00
parent ce5344da69
commit 6e24b09eaa
8 changed files with 372 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -50,7 +50,7 @@ immutable compatible receiver image before attended execution.
```task
id: RPF-WP-0059-T03
status: progress
status: done
priority: high
state_hub_task_id: "c4e69d60-030e-592b-ac56-9f77468f7da9"
```
@ -64,7 +64,7 @@ resume on interruption. No live effect or secret read occurred in preparation.
```task
id: RPF-WP-0059-T04
status: wait
status: progress
priority: high
state_hub_task_id: "7d8e5315-9470-5596-a865-d451284f6f50"
```
@ -74,3 +74,23 @@ source/tenant/instance scope and real elapsed-hour periodic evidence, isolated
wrong-namespace denial, actual formerly-valid bearer revocation, independent
protected readback, missing-class/lag/divergence, restart/scale-zero evidence.
Never infer profile acceptance from a model test or registry projection.
### Native admission progress — 2026-10-15
Root executed the explicit approved packet in an attended platform-admin
session. Wrapper exit0 and self-revocation confirmed; receiver-custody-live.json
records registry15→16 CAS, durable version1 custody, preserved Approval
credentials/other senders, reader scope/negative/revoke checks, ESO projection
and actual loaded registry equality, and Ready receiver reload. CCR0047 is
applied, not verified/active. An initial ambient OPENBAO_TOKEN attempt was
correctly refused before custody mutation; that session also self-revoked.
Retry removed token aliases before launching OIDC, without relaxing guards.
Collector native receipt proves heartbeat1/deny1 own-instance reconciliation,
duplicate200, wrong-source400/wrong-tenant400/archive-read403/invalid-bearer401,
pending0; actual collector pod restart preserved first202 receipts and pending0.
Exact root receipts copied to docs/evidence/2026-10-15-cadence-receiver/.
The real hourly observation started19:36 UTC with authorized health polling;
it is still running. No elapsed-hour or independent observer acceptance is
claimed. T04 remains progress for actual timed capture and protected readback.