coulomb/railiance-infra
0
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

RAIL-HO-WP-0004 stale workplan cleanup

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-22 16:40:02 +02:00
parent 0328be75d6
commit c47930e2f9
1 changed files with 22 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
workplans/RAIL-HO-WP-0004-production-readiness.md
View File

@@ -4,11 +4,12 @@ type: workplan
title: "Railiance Production Readiness — Automated, Reproducible Stack"
domain: railiance
repo: railiance-infra
status: active
status: finished
owner: worsch
topic_slug: railiance
created: "2026-03-26"
updated: "2026-05-02"
updated: "2026-05-22"
completed: "2026-05-22"
supersedes: RAIL-PL-WP-0001
state_hub_workstream_id: "cee078e9-b18c-4f84-8a8a-6f27c2f9f407"
---
@@ -436,13 +437,18 @@ context.
```task
id: RAIL-HO-WP-0004-T09
status: todo
status: cancelled
priority: medium
state_hub_task_id: "d2afe78a-eb51-4ce9-b332-f181323d2370"
needs_human: true
intervention_note: "Requires decisions: final hostname/domain or tunnel-only endpoint, registry choice, private exposure model, and approval before freezing workstation writes and migrating production State Hub data."
needs_human: false
intervention_note: "Superseded by CUST-WP-0038 State Hub Full ThreePhoenix HA Migration, which owns the hostname, registry, private exposure model, HA database/storage strategy, restore drills, and production data migration approval."
```
**Superseded 2026-05-22:** State Hub cluster migration is now owned by
`CUST-WP-0038` (`State Hub Full ThreePhoenix HA Migration`). This Railiance
task is closed as superseded so `RAIL-HO-WP-0004` can finish without splitting
State Hub HA/data-migration governance across two workplans.
**Pre-condition:** T04 done (cnpg Gitea DB working); T08 done (deploy sequence
documented). Custodian-side safety gate `CUST-WP-0011-T01` must have passed:
a fresh WSL2 State Hub backup restore drill with matching row counts.
@@ -479,14 +485,17 @@ approval after stabilisation.
```task
id: RAIL-HO-WP-0004-T10
status: todo
status: done
priority: low
state_hub_task_id: "34d73215-f016-4750-8da5-69f82d63d619"
needs_human: true
intervention_note: "activity-core architecture needs review before packaging — needs confirmation of runtime (Rails/Go/other), whether it uses postgres, and what the migration strategy is for any existing on-node data."
needs_human: false
intervention_note: "Deployed activity-core as a K3s production service on railiance01 on 2026-05-22. API/worker/event-router running; health endpoint OK; migrations and sync jobs completed."
```
**Pre-condition:** T09 done (state-hub on cluster operational).
**Completion note 2026-05-22:** activity-core was deployed to the cluster
independently of the State Hub HA migration. The original T09 dependency is
superseded along with T09; ongoing State Hub migration work is tracked in
`CUST-WP-0038`.
Activity-core is the Rails/Go/other application running on CoulombCore ad-hoc.
This task packages and deploys it as a proper S5 workload.
@@ -521,11 +530,12 @@ T07 (SSH remotes) ─ independent, unblock early
T08 (deploy docs) ─ can be written in parallel with T03-T06
T09 (state-hub on cluster) ─ needs T04 (DB working) + T08 (deploy pattern)
T10 (activity-core) ─ needs T09
T09 (state-hub on cluster) ─ superseded by CUST-WP-0038
T10 (activity-core) ─ completed independently on 2026-05-22
```
Recommended order: T07 → T01+T02 → T03 → T04 → T05 → T06 → T08 → T09 → T10
Completed order: T07 → T01+T02 → T03 → T04 → T05 → T06 → T08 → T10;
T09 superseded by `CUST-WP-0038`.
## References