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

CUST-WP-0075 inbox sweep: act on railiance-platform reply to ACTIVITY-WP-0041-T02
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:
tegwick 2026-10-03 03:35:40 +02:00
parent 59d66e7fbd
commit 289ff9ad66
2 changed files with 23 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

18
workplans/ACTIVITY-WP-0041-gitops-adoption.md
View file

@ -45,8 +45,10 @@ server-dry-run the proposed managed set; no unintended spec change or pruning.
```task
id: ACTIVITY-WP-0041-T02
status: wait
blocked_on: message-from:railiance-platform
blocking_reason: "railiance-platform owns the AppProject/root Application; per-app adoption record follows RPF-WP-0044's procedure."
needs_human: true
decision_id: 89f1058f-33bc-47a8-8a49-0b44d426c67e
depends_on: [RPF-WP-0048-T02]
blocking_reason: "Adopted 2026-09-27 (manual sync); automated sync waits on RPF-WP-0048-T02: soak evidence plus founder confirmation of scoped identity/checks (D2)."
priority: high
state_hub_task_id: "af09865d-8cc9-5571-9c34-20ae679a1e4e"
```
@ -65,6 +67,18 @@ target to bypass the GitOps path. Keep secrets under existing ESO/OpenBao custod
The founder-approved exception covers WP0040 only; adoption activation is a separate
one-time governance decision.
2026-10-03 (CUST-WP-0075 inbox sweep): railiance-platform's 2026-10-02 reply
(message 0638c13b) is about ACTIVITY-WP-0042-T01, the backup scheduling role,
not about this adoption. It says railiance-platform considers activity-core the
scheduling owner, under the rule that roles tie to the source repo. No
railiance-platform message is outstanding for this task. The AppProject and
child Application exist (RPF-WP-0048-T01 done, adoption 2026-09-27). The
remaining gate is RPF-WP-0048-T02: the soak evidence, then the founder's
confirmation before automated sync, routed to hub decision 89f1058f (D2).
Changed: `blocked_on: message-from:railiance-platform` replaced by `needs_human`
+ `decision_id` D2 and `depends_on: [RPF-WP-0048-T02]`. activity-core replied
on the WP-0042 points; see that plan.
## Establish standing authority for bounded routine releases
```task

7
workplans/ACTIVITY-WP-0042-platform-backup-restore-evidence-scheduling.md
View file

@ -48,6 +48,13 @@ operation, or decline. Needs: restore execution stays with an S3-owned tool
invoked as a fixed bounded operation; approval-engine authority supplied per
run; no general executor behaviour.
2026-10-03 (CUST-WP-0075 inbox sweep): railiance-platform replied (message
0638c13b) asking activity-core to proceed under its conditions, because "roles
tie to the source repo". That is the S3 owner's consent. It does not resolve
this founder gate, so T01 stays waiting on D2 and the plan stays `proposed`. It
also asks activity-core to declare `atm-backup-daily`, which remains T03's
founder confirmation. activity-core replied with the same position.
2026-10-03: human gate routed to hub decision 89f1058f-33bc-47a8-8a49-0b44d426c67e (D2: ArgoCD owns production: go-ahead sequence for railiance-apps-root, issue-core, policy-nexus and activity-core automation) by CUST-WP-0075; resolving that decision raises C-40 here.
## Admit a bounded operation and credential lane