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

Record live receiver gate and isolate readiness from attestation jobs
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: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
codex 2026-09-11 07:26:16 +02:00
parent 5cc325b744
commit 290e2b51fd
4 changed files with 211 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

21
workplans/RPF-WP-0035-credential-lane-implementation.md
View file

@ -397,11 +397,11 @@ into this client-identity grant.
```task
id: RPF-WP-0035-T08
status: progress
status: wait
priority: high
assignee: railiance-platform
needs_human: true
intervention_note: "CCR-2026-0021/0022 need named platform-operator, audit-core-owner and producer-owner reviews. Receiver upgrade and namespace readiness remain separate preconditions; approval alone does not admit factory execution."
intervention_note: "All named CCR-2026-0021/0022 reviews are approved. Compatible receiver and namespaces are ready. Attended OIDC failed before owner-command handoff; Warden could not confirm remote session revocation. Await operator browser/MFA feedback and login/session resolution before custody retry. Do not repeat sender approval."
state_hub_task_id: "0ef52c26-2669-5cd1-8149-b1f6fcdda6cb"
```
@ -481,3 +481,20 @@ platform-operator, audit-core-owner and both producer owners. Both exact request
are approved; their existing State Hub decisions are resolved. This clears the
review request only. Receiver rollout, namespace readiness, attended custody and
positive/negative native evidence remain the execution gates.
### Native receiver and attended execution return — 2026-09-11
Audit Core c82e0442de0f is deployed and passes the native synthetic contract.
Its existing 32-event chain/head is unchanged. The owner Approval Engine
namespace now exists and all four ESO objects pass strict server dry-run.
The two exact ingress rules are applied; sender custody/ESO application is not.
Warden selected founder_required/oidc_login and attempted the reviewed silent
seed command through the contained wrapper. Login failed before command
handoff; no custody receipt was created. Warden could not confirm remote
session revocation. Await operator browser/MFA feedback and login/session
resolution. Approvals remain valid; T08 waits for the identity act, not review.
The receiver check now selects component=receiver, so retained attestation-job
pods cannot falsely block a stable receiver. Eighteen custody tests pass.
[Native return](../docs/evidence/2026-09-11-factory-receiver-live.json).