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

Bind Coulomb routine recovery access to governed scoped APIs

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a17f16-d99c-7ea3-95f0-8212897fba6b
This commit is contained in:
codex 2026-10-28 01:34:12 +01:00
parent 1eca6d00c7
commit 2d8a554c10
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
workplans/RPF-WP-0053-coulomb-paired-backup-admission.md
View file

@ -306,3 +306,16 @@ credentials. Existing email recovery proves the isolated-project mechanism, not
a grant for Coulomb. Resource-specific grants and independent kit custody still
need native execution through an attended platform operator front door. Approval
is recorded; implementation/verification remain T02/T03/T04.
## One-time provider bootstrap, routine programmatic access — 2026-10-28
User instruction recorded as decision6139e02b-3fb7-4eff-be8a-efe127c45ce5:
the offered attended Scaleway Console login is bootstrap only; regular later
access must use scoped APIs. Provision governed publisher, independent archive
reader and custodian escrow API access within the already approved Coulomb
recovery custody scope. Their credentials/kit must survive primary-node and
workstation loss. Personal Console session state is never a scheduled worker or
regular recovery/drill credential. Retire the temporary session after native API
verification. No standing organization-wide operator key or publisher IAM admin
right follows from this instruction. First aborted attempt saved no state; fresh
attended browser is waiting for user confirmation, with no provider mutation.