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

Record sitting-requester custody apply; keep exchange proof open.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
Attended helper returned applied, KV version 1, ESO synced, KeyCape
ready. No sitting POST. CCRs 0026/0027 are applied metadata only.

Assistant: grok
Assistant-Session: 01a0a23b-3bf0-7341-b4e5-9dc05f72573a
This commit is contained in:
codex 2026-09-15 20:31:00 +02:00
parent 75e5c1af65
commit 50f031091c
5 changed files with 54 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RPF-WP-0042-informed-decision-sitting-requester.md
View file

@ -52,3 +52,9 @@ No sitting POST until exchange proof exists. Do not widen CCR-2026-0024/0025.
`revocation could not be confirmed`. Public Ingress is already absent, and the
shell still had `BAO_ADDR=https://bao.coulomb.social`. The wrapper now pins the
operator tunnel. Retry that same helper; do not treat this attempt as custody.
Retry 2026-09-15T18:28:25Z succeeded: receipt `applied`, phase `keycape_ready`,
KV version 1, ESO Ready/SecretSynced, KeyCape single Ready replica, CCRs
applied. No sitting POST. Remaining: create-only token-exchange proof
(positive create scope, refuse approve/consume, sibling path deny). Evidence:
`docs/evidence/2026-09-15-sitting-requester-provision.json`.