Wave-2 right-sizing applied 2026-10-22 (CUST-WP-0071)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
This commit is contained in:
tegwick 2026-10-22 01:00:21 +02:00
parent 894bc084e3
commit 14d7181c60

View file

@ -4,7 +4,7 @@ type: workplan
title: "Wave-2 resource right-sizing from the 2026-10-21 allocation review"
domain: financials
repo: railiance-enablement
status: ready
status: finished
flavor: implementation
owner: claude
topic_slug: railiance
@ -26,10 +26,8 @@ Origin: the 2026-10-21 node allocation review (`RESOURCE-WP-0008-T03`, feeding `
```task
id: RAIL-EN-WP-0003-T01
status: wait
status: done
priority: medium
needs_human: true
blocking_reason: "Wave-2 cluster write; founder approval for wave 2 not yet given (2026-10-21 interview)"
state_hub_task_id: "5a49ca0c-0bc5-59de-8f34-fd697a0df543"
```
@ -69,3 +67,7 @@ Restarts the application-controller StatefulSet pod and the repo-server pod
Rollback: revert the source commit and re-sync/re-apply; the before values in the table above are the rollback target. Keep before/after `kubectl get -o yaml` captures as the receipt.
ArgoCD manages itself: apply through the RAIL-EN-WP-0002 declared-state path and confirm all Applications return to Synced/Healthy afterwards.
## Applied — 2026-10-22 (RAIL-EN-WP-0003-T01)
Applied under the founder's wave-2 authorization (the-custodian docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md), after a full-render diff against live that showed resources only. Argo CD application-controller and repo-server rolled out. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.