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

CUST-WP-0075 inbox sweep: act on activity-core reply to RPF-WP-0036-T03
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3775@bnt-lap001
Assistant-Session: cfacb6a5-ad5b-4f79-ac67-053e3b0d34a3
This commit is contained in:
codex 2026-10-03 03:33:54 +02:00
parent 4e007e46b9
commit 6cddf99a8d
1 changed files with 17 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

20
workplans/RPF-WP-0036-platform-service-assurance.md
View file

@ -8,7 +8,7 @@ status: blocked
flavor: implementation
owner: codex
created: "2026-09-05"
updated: "2026-09-27"
updated: "2026-10-03"
state_hub_workstream_id: "ca639c3d-3a87-5fa4-ad13-6f2e014b0c84"
---
@ -63,9 +63,10 @@ and package dependency rather than a blanket new-cluster project here.
```task
id: RPF-WP-0036-T03
status: wait
blocked_on: message-from:activity-core
needs_human: true
blocking_reason: "T02 done (cadence/expiry available). Proposed execution owner: activity-core (automation execution per SCOPE.md); scheduling role assigned to activity-core as source repo of its backup job (2026-10-03); remaining gates: ACTIVITY-WP-0042 bounded operation, OpenBao credential route from S3, and per-run approval-engine approval (no standing grant exists; standing authority is a gate-house/access-engine question)."
decision_id: 89f1058f-33bc-47a8-8a49-0b44d426c67e
depends_on: [ACTIVITY-WP-0042]
blocking_reason: "activity-core replied (not accepted yet): role acceptance is the founder decision ACTIVITY-WP-0042-T01 (D2); then ACTIVITY-WP-0042 bounded operation, S3 OpenBao credential route, repaired openbao-activity-core store and per-run approval-engine approval."
priority: high
state_hub_task_id: "d64446fb-870b-5ae9-9628-f1fb9d06c5a4"
```
@ -84,6 +85,19 @@ its execution is evidenced, and missing/stale/failed evidence reaches a named
operator. A template, dated successful snapshot, or same-PVC reboot does not
pass as restore proof. Record independent recovery-key access without values.
2026-10-03 (CUST-WP-0075 inbox sweep): activity-core replied (message 3b1bc698)
that the scheduling role is NOT accepted yet. It already runs
`daily-cnpg-option-a-backup` (Nextcloud lane, three clusters, no restores), and a
platform run needs a new ACT-ADR-007-successor bounded operation, an S3-owned
OpenBao credential route (the `openbao-activity-core` store has failed since
2026-09-19), per-run approval-engine authority, and an S3-owned fixed restore
tool. activity-core recorded the proposal as ACTIVITY-WP-0042, whose T01 is a
founder decision routed to hub decision 89f1058f (D2). railiance-platform's
"roles tie to the source repo" note of 2026-10-02 does not resolve that founder
gate. Changed: `blocked_on: message-from:activity-core` replaced by
`needs_human` + `decision_id` D2 and `depends_on: [ACTIVITY-WP-0042]`;
activity-core stays the proposed owner. RPF-WP-0038-T04 was not changed here.
## Produce S3 signals and prove their delivery to the evidence owner
```task