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

RPF-WP-0015/0056: record round-5 approval and close coordination

Browse source 
Round-5 owner receipts match 044df6f. T02 stays wait for a new attended
window. Custodian accepted Playwright coordination on CUST-WP-0080-T05,
so T06 is done and T03 still waits on identity mapping. The activity-core
Forgejo read design no longer cites the consumed CCR-2026-0034 number.

Assistant: grok
Assistant-Session: 01a13b3e-0402-7a83-a827-6b29197b7132
This commit is contained in:
codex 2026-10-14 18:33:07 +02:00
parent 044df6fe5b
commit be514f6d74
4 changed files with 46 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/credential-lane-designs/activity-core-repo-manager-forgejo-read.md
View file

@ -1,10 +1,17 @@
# Activity Core repo-manager Forgejo read lane (CCR-2026-0034, number to confirm)
# Activity Core repo-manager Forgejo read lane (no CCR filed)
Status: **proposed**, drafted 2026-10-04 for STATE-WP-0094 memo 3
Status: **proposed design only**, drafted 2026-10-04 for STATE-WP-0094 memo 3
(`freshness-runner-deploy-trial-e77f8b4`, accepted by the founder 2026-10-04,
approval `4ae04c8e`) and RMGR-WP-0020-T04. Nothing here is approved, applied or
provisioned. No Forgejo, OpenBao or cluster object was created. Confirm the CCR
number with the CCR tooling before registering; 0033 was the highest seen.
provisioned. No Forgejo, OpenBao or cluster object was created.
An earlier draft of this page cited CCR-2026-0034. That number is the KeyCape
secrets-engine operator reader
(`credential-change-requests/CCR-2026-0034.yaml`, applied 2026-10-07). No
Forgejo-read CCR exists for the Activity Core worker. CCR-2026-0029 and
CCR-2026-0030 are ops_run worker tokens, and CCR-2026-0031 is the core-hub
Forgejo source read bound to another namespace. Do not treat this design as a
CCR id. Assign the next free id only when this lane is admitted.
## Why
@ -47,7 +54,7 @@ worker's other secrets and is the default here.
## Draft manifests (land only after metadata apply)
```yaml
# CCR-2026-0034 (to confirm). Do not apply until approval and confirm-binding.
# No CCR id. Do not apply until this design is admitted, numbered and approved.
apiVersion: external-secrets.io/v1
kind: ClusterSecretStore
metadata:

7
docs/playwright-identity-handoff.md
View file

@ -15,8 +15,11 @@ source-backed delivery task. Platform acceptance remains RPF-WP-0056-T03; the
coordination request must preserve the existing owner responsibilities and evidence.
Sent to `the-custodian` through State Hub on 2026-10-13 at 19:31 UTC:
`1b279bad-a159-43da-8709-1167882e62f8`. Delivery is confirmed; coordinating-owner
acceptance and source task references remain pending in RPF-WP-0056-T06.
`1b279bad-a159-43da-8709-1167882e62f8`. Accepted at 20:04 UTC
(`f761e801-2111-41f3-af0d-a5411a37ffab`): coordinator the-custodian /
custodian-codex, source CUST-WP-0080-T05 (Hub
`ed8b909a-23bf-5e5f-b600-e477fbae136b`). RPF-WP-0056-T06 is done on that return.
Platform acceptance remains RPF-WP-0056-T03.
Requirements:

8
workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md
View file

@ -448,3 +448,11 @@ Next: select the handle coherent with the Secret refresh instead of requiring ex
one (owner re-review), then a new window. Follow-ups: ops-warden must also strip
OPENBAO_TOKEN for attended children; the standing shell-profile token should be revoked
and removed (founder).
Round 5 (2026-10-14, railiance-platform `044df6f`, contract `ea3f53d6`): the harness
selects the one lease issued for the mounted Secret refresh and leaves older
predecessors. Current artifact hashes match the owner receipts. All five owners
approved: audit-core `b3c564a6`, rapp-postgres `08a84caf`, railiance-cluster
`4bb0d7af`, railiance-infra `0300d069`, railiance-platform `0f8f0692`. This is
procedure approval only. T02 stays `wait` until a new attended window. The T03
checklist bytes in that contract are the round-4 bytes.

26
workplans/RPF-WP-0056-playwright-consumer-admission.md
View file

@ -8,7 +8,7 @@ status: blocked
owner: codex
topic_slug: railiance
created: "2026-10-13"
updated: "2026-10-13"
updated: "2026-10-14"
state_hub_workstream_id: "31933d08-c877-5fda-aff9-6220c3705c92"
---
@ -83,6 +83,15 @@ cancellation and restart/interrupted/completed-artifact recovery. One available
release supports same-image recovery only; cross-version rollback stays unproven.
Keep RAPP-PLAYWRIGHT-WP-0004-T01 open until its owner accepts those receipts.
2026-10-13 owner returns narrow the remaining gap. rapp-playwright `2cb2b654`
and Custodian `2cb2b654e03e64ea28f1b369a89d7eaeb36c26fb` record same-image abrupt
recovery, including the managed SIGKILL trial. That does not prove cross-version
rollback or a real consumer identity. Registration preparation is published in
NetKingdom `276b95f6` (NK-WP-0050-T02 still in progress). Platform acceptance
stays here: the Kubernetes authentication and `playwright-consumers` group
mapping route is still unimplemented. Custody and per-agent delivery remain
`docs/playwright-identity-handoff.md`. No new membership decision is open.
## October 13 native implementation
@ -162,10 +171,8 @@ is required. Evidence: docs/evidence/2026-10-13-playwright-consumer-preparation.
```task
id: RPF-WP-0056-T06
status: wait
status: done
priority: high
blocked_on: message-from:the-custodian
blocking_reason: "Await Custodian coordination acceptance, accountable coordinator and source task links for the existing cross-repository delivery."
state_hub_task_id: "ef6c21bc-0048-5b73-976e-130cd9af538d"
```
@ -182,4 +189,13 @@ availability requires real human and coding-agent trials and provider acceptance
no further user membership decision is needed.
Request delivered to the-custodian through State Hub on 2026-10-13 at 19:31 UTC,
message `1b279bad-a159-43da-8709-1167882e62f8`. Coordination acceptance is pending.
message `1b279bad-a159-43da-8709-1167882e62f8`.
Accepted 2026-10-13 at 20:04 UTC, message `f761e801-2111-41f3-af0d-a5411a37ffab`.
Accountable coordinator: the-custodian / custodian-codex. Source task:
CUST-WP-0080-T05, Hub `ed8b909a-23bf-5e5f-b600-e477fbae136b`, published at
Custodian `3a850beb` and refreshed through `f5925c62`. Provider recovery and
the consumer acceptance command are recorded on rapp-playwright `2cb2b654` and
`5b8e7984`. T06 is done because that source-backed coordination return exists.
T03 still owns platform acceptance. Live identity, custody, native authenticator
and per-caller transport are not delivered by this acceptance.