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

Clarify cluster boundary for rail-kubernetes
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 6s
Details

Browse source
This commit is contained in:
codex 2026-07-25 11:17:51 +02:00
parent 74b490a31e
commit be3b8ff31e
9 changed files with 329 additions and 146 deletions
Download patch file Download diff file Expand all files Collapse all files

21
workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "rail-kubernetes extraction from railiance-cluster"
domain: financials
repo: railiance-cluster
status: ready
status: active
owner: codex
topic_slug: railiance
created: "2026-07-25"
@ -42,7 +42,7 @@ It must not:
```task
id: RAIL-BS-WP-0012-T01
status: todo
status: done
priority: high
state_hub_task_id: "7255ef32-3fdf-473f-a5c0-62b509ee7a4e"
```
@ -55,11 +55,16 @@ Update S2 scope and related docs so they clearly distinguish:
Done when the repo no longer describes the staged workload lifecycle as a
long-term S2 ownership concern.
2026-07-25: Updated `SCOPE.md`, `README.md`, and `docs/README.md` so S2 now
claims Kubernetes substrate ownership only, while the generic workload
lifecycle is marked as transitional material targeted for future
`rail-kubernetes`.
## T02 - Inventory exact extraction candidates and retained files
```task
id: RAIL-BS-WP-0012-T02
status: todo
status: done
priority: high
state_hub_task_id: "e80b511a-33c6-445b-95e2-3d0755ea9b5e"
```
@ -70,11 +75,15 @@ files remain cluster-owned.
Done when the repo has one reviewed move map tied to real file paths.
2026-07-25: Added `docs/rail-kubernetes-extraction-map.md` with reviewed file
paths for material that moves to `rail-kubernetes`, material that remains
cluster-owned, and migration debt that must be rehomed elsewhere.
## T03 - Define the cluster substrate profile consumed by `rail-kubernetes`
```task
id: RAIL-BS-WP-0012-T03
status: todo
status: done
priority: high
state_hub_task_id: "517e2849-9b36-4508-9e2a-90f219e211c7"
```
@ -90,6 +99,10 @@ Define the minimum cluster profile that S2 publishes for the future rail:
Done when `rail-kubernetes` has a narrow substrate contract to depend on.
2026-07-25: Added `docs/rail-kubernetes-substrate-profile.md` to publish the
current S2 substrate facts, guaranteed canary mode, operator/runtime
expectations, and explicit non-guarantees for wave 1.
## T04 - Prepare compatibility shims for the migration window
```task