Record authorized requester and service identity owner review requests
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a1046b-5629-7f52-badd-f718eadb6042
This commit is contained in:
parent
6b91d51039
commit
ecbe3b9dd5
4 changed files with 49 additions and 0 deletions
25
docs/evidence/2026-10-04-owner-review-requests.json
Normal file
25
docs/evidence/2026-10-04-owner-review-requests.json
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
{
|
||||
"schema": "railiance-platform.owner-review-coordination.v1",
|
||||
"date": "2026-10-04",
|
||||
"scope": "Founder-authorized two non-secret owner review requests",
|
||||
"reviewed_commit": "6b91d510395215d178d60ee8884e7fc00930a0cf",
|
||||
"requests": [
|
||||
{
|
||||
"to_agent": "informed-decision",
|
||||
"id": "2c1507b2-b361-4ef9-b5d4-3245014c7c52",
|
||||
"thread_id": "f84637fa-2355-4971-a2dc-7f1fd01710a8",
|
||||
"subject": "RPF-WP-0051-T02: accept founder-approved requester delivery design and return exact runtime/binding scope",
|
||||
"created_at": "2026-10-04T09:02:38.076671Z"
|
||||
},
|
||||
{
|
||||
"to_agent": "key-cape",
|
||||
"id": "b4fc62ea-f92c-4410-919a-9f3cce2d406b",
|
||||
"thread_id": "f84637fa-2355-4971-a2dc-7f1fd01710a8",
|
||||
"subject": "RPF-WP-0035-T02: name actual secrets-engine-openbao registration/custody work and non-secret owner receipt",
|
||||
"created_at": "2026-10-04T09:02:40.523614Z"
|
||||
}
|
||||
],
|
||||
"technical_acceptance_received": false,
|
||||
"live_change_authorized": false,
|
||||
"credential_values_requested": false
|
||||
}
|
||||
|
|
@ -3,6 +3,15 @@
|
|||
These are source-review requests, not completed acknowledgements or approved
|
||||
live actions. Platform does not change another owner's workplan or send values.
|
||||
|
||||
2026-10-04: Founder authorized sending the prepared informed-decision and
|
||||
KeyCape requests. Hub creation receipts: informed-decision
|
||||
`2c1507b2-b361-4ef9-b5d4-3245014c7c52` at 09:02:38 UTC; key-cape
|
||||
`b4fc62ea-f92c-4410-919a-9f3cce2d406b` at 09:02:40 UTC. Both use preparation
|
||||
thread `f84637fa-2355-4971-a2dc-7f1fd01710a8` and reviewed platform commit
|
||||
`6b91d510395215d178d60ee8884e7fc00930a0cf`. Requests are sent; technical acceptance
|
||||
remains outstanding. The user-engine/provider item below remains a prepared
|
||||
source request, outside this two-message authorization.
|
||||
|
||||
## secrets-engine / KeyCape — RPF-WP-0035-T02
|
||||
|
||||
Platform already has exact proposed files `openbao/auth/keycape-services-config.json`,
|
||||
|
|
|
|||
|
|
@ -75,6 +75,14 @@ contract, and rollback/cleanup receipts contain no secret material.
|
|||
|
||||
2026-10-03 (CUST-WP-0075): gate check. SECRETS-WP-0007-T04 is done (2026-09-27), so the gate named in the design is open. It is not the last one: the design says to confirm the exact live client registration and protected client-side custody before writing, and positive-login proof needs a real KeyCape service JWT. KeyCape's contract (`openbao-service-auth-contract.md`) and KEY-WP-0009 claim source registration only; the live registration of `secrets-engine-openbao` and its client-credential custody are "a separate approved custody action" that no workplan task owns yet (SECRETS-WP-0008-T06 waits on this task). Re-qualified with `blocked_on: message-from:key-cape`; key-cape was asked for the owning task id, which will replace it as `depends_on`. The design stays proposed and no child command was written. Not approvable in D1 yet.
|
||||
|
||||
2026-10-04: Founder authorized the prepared coordination request. Sent
|
||||
`b4fc62ea-f92c-4410-919a-9f3cce2d406b` to key-cape on preparation thread
|
||||
`f84637fa-2355-4971-a2dc-7f1fd01710a8`, referencing platform source
|
||||
`6b91d510395215d178d60ee8884e7fc00930a0cf`. Requested actual registration and
|
||||
protected-custody owning tasks/status/revisions and non-secret receipts. Source
|
||||
registration is not live custody; no value fetch or live registration was
|
||||
requested. T02 remains waiting on the owner return and separate execution gates.
|
||||
|
||||
## Implement the platform operator-write CCR contract and Fluid lane
|
||||
|
||||
```task
|
||||
|
|
|
|||
|
|
@ -64,6 +64,13 @@ creation authority for the exact ServiceAccount. A draft identity is not an
|
|||
owner acceptance. Retain exact immutable runtime/config references and a bounded
|
||||
positive/negative/rotation/revocation proof plan before promotion.
|
||||
|
||||
2026-10-04: Founder authorized the prepared owner coordination requests. Sent
|
||||
request `2c1507b2-b361-4ef9-b5d4-3245014c7c52` to informed-decision on preparation
|
||||
thread `f84637fa-2355-4971-a2dc-7f1fd01710a8`, reviewing source commit
|
||||
`6b91d510395215d178d60ee8884e7fc00930a0cf`. It carries the design approval and
|
||||
asks for exact binding/mount/runtime/verification ownership and remaining native
|
||||
evidence. Hub creation receipt is retained; owner acceptance is still outstanding.
|
||||
|
||||
## Apply and accept the scoped workload delivery
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue