Add rail-kubernetes extraction workplan
This commit is contained in:
parent
c3757c5b19
commit
a770c0b589
2 changed files with 155 additions and 0 deletions
42
WORK-RECORDS.md
Normal file
42
WORK-RECORDS.md
Normal file
|
|
@ -0,0 +1,42 @@
|
|||
# Work Records — railiance-cluster
|
||||
|
||||
> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
|
||||
> stage 3). Do not edit by hand — edit the source file/block listed for
|
||||
> each record and re-run fix-consistency to refresh this index. Archived
|
||||
> workplans are omitted; closed decisions/intakes/engagements stay listed
|
||||
> so recently-resolved work is still visible. [auto]
|
||||
|
||||
| Kind | ID | Status | Lane | Source |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| workplan | RAIL-BS-WP-0007 | backlog | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| workplan | RAIL-BS-WP-0008 | finished | — | workplans/RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md |
|
||||
| workplan | RAIL-BS-WP-0009 | finished | — | workplans/RAIL-BS-WP-0009-activity-core-admin-sync-smoke.md |
|
||||
| workplan | RAIL-BS-WP-0010 | finished | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| workplan | RAIL-BS-WP-0011 | finished | — | workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md |
|
||||
| workplan | RAIL-BS-WP-0012 | ready | — | workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md |
|
||||
| task | RAIL-BS-WP-0007-T01 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T02 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T03 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T04 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T05 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T06 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T07 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0008-T01 | done | — | workplans/RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md |
|
||||
| task | RAIL-BS-WP-0008-T02 | done | — | workplans/RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md |
|
||||
| task | RAIL-BS-WP-0008-T03 | cancel | — | workplans/RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md |
|
||||
| task | RAIL-BS-WP-0008-T04 | done | — | workplans/RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md |
|
||||
| task | RAIL-BS-WP-0009-T01 | done | — | workplans/RAIL-BS-WP-0009-activity-core-admin-sync-smoke.md |
|
||||
| task | RAIL-BS-WP-0010-T01 | done | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| task | RAIL-BS-WP-0010-T02 | done | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| task | RAIL-BS-WP-0010-T03 | done | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| task | RAIL-BS-WP-0010-T04 | done | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| task | RAIL-BS-WP-0010-T05 | done | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| task | RAIL-BS-WP-0010-T06 | done | — | workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md |
|
||||
| task | RAIL-BS-WP-0011-T01 | done | — | workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md |
|
||||
| task | RAIL-BS-WP-0011-T02 | done | — | workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md |
|
||||
| task | RAIL-BS-WP-0011-T03 | done | — | workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md |
|
||||
| task | RAIL-BS-WP-0011-T04 | done | — | workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md |
|
||||
| task | RAIL-BS-WP-0012-T01 | todo | — | workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md |
|
||||
| task | RAIL-BS-WP-0012-T02 | todo | — | workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md |
|
||||
| task | RAIL-BS-WP-0012-T03 | todo | — | workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md |
|
||||
| task | RAIL-BS-WP-0012-T04 | wait | — | workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md |
|
||||
113
workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md
Normal file
113
workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md
Normal file
|
|
@ -0,0 +1,113 @@
|
|||
---
|
||||
id: RAIL-BS-WP-0012
|
||||
type: workplan
|
||||
title: "rail-kubernetes extraction from railiance-cluster"
|
||||
domain: financials
|
||||
repo: railiance-cluster
|
||||
status: ready
|
||||
owner: codex
|
||||
topic_slug: railiance
|
||||
created: "2026-07-25"
|
||||
updated: "2026-07-25"
|
||||
state_hub_workstream_id: "2b01ce91-35be-4947-832b-2f462c6ba472"
|
||||
---
|
||||
|
||||
# RAIL-BS-WP-0012 - rail-kubernetes extraction from railiance-cluster
|
||||
|
||||
## Goal
|
||||
|
||||
Prepare the S2 side of the `rail-kubernetes` split so `railiance-cluster` can
|
||||
return to a clean Kubernetes substrate identity while the generic
|
||||
workload-on-Kubernetes contract moves to a future `rail-kubernetes` repo.
|
||||
|
||||
This workplan follows the boundary defined in
|
||||
`/home/worsch/railiance-master/docs/rail-kubernetes-boundary.md`.
|
||||
|
||||
## Boundaries
|
||||
|
||||
This workplan may:
|
||||
|
||||
- clarify cluster-owned scope and retained files
|
||||
- prepare compatibility notes and substrate-profile outputs
|
||||
- identify exact move candidates and compatibility shims
|
||||
|
||||
It must not:
|
||||
|
||||
- silently move files into a new repo that does not exist yet
|
||||
- break current `bin/railiance` users during the migration window
|
||||
- reassert S2 ownership over generic workload lifecycle semantics once the
|
||||
boundary is clear
|
||||
|
||||
## T01 - Align `railiance-cluster` scope with the wave-1 boundary
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0012-T01
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "7255ef32-3fdf-473f-a5c0-62b509ee7a4e"
|
||||
```
|
||||
|
||||
Update S2 scope and related docs so they clearly distinguish:
|
||||
|
||||
- Kubernetes substrate ownership that stays in `railiance-cluster`
|
||||
- generic workload lifecycle ownership that belongs to `rail-kubernetes`
|
||||
|
||||
Done when the repo no longer describes the staged workload lifecycle as a
|
||||
long-term S2 ownership concern.
|
||||
|
||||
## T02 - Inventory exact extraction candidates and retained files
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0012-T02
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "e80b511a-33c6-445b-95e2-3d0755ea9b5e"
|
||||
```
|
||||
|
||||
Inventory the current lifecycle docs, schema, examples, CLI commands, and
|
||||
scaffolding assets that should move to `rail-kubernetes`, and record which
|
||||
files remain cluster-owned.
|
||||
|
||||
Done when the repo has one reviewed move map tied to real file paths.
|
||||
|
||||
## T03 - Define the cluster substrate profile consumed by `rail-kubernetes`
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0012-T03
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "517e2849-9b36-4508-9e2a-90f219e211c7"
|
||||
```
|
||||
|
||||
Define the minimum cluster profile that S2 publishes for the future rail:
|
||||
|
||||
- ingress class and routing modes
|
||||
- supported canary capabilities
|
||||
- certificate path
|
||||
- storage constraints
|
||||
- operator/runtime prerequisites
|
||||
- namespace and RBAC expectations
|
||||
|
||||
Done when `rail-kubernetes` has a narrow substrate contract to depend on.
|
||||
|
||||
## T04 - Prepare compatibility shims for the migration window
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0012-T04
|
||||
status: wait
|
||||
priority: medium
|
||||
state_hub_task_id: "fdc9fa63-bee2-4774-b92f-63cf7a315603"
|
||||
```
|
||||
|
||||
Blocked on T01-T03 and the creation of the future `rail-kubernetes` repo.
|
||||
|
||||
Plan the thin compatibility path that keeps current operators functional during
|
||||
the split, including any temporary `bin/railiance` delegation or short pointer
|
||||
docs left behind in `railiance-cluster`.
|
||||
|
||||
Done when the migration can proceed without a flag day for current users.
|
||||
|
||||
## Notes
|
||||
|
||||
This workplan is intentionally repo-local. The framework-level separation plan
|
||||
lives in `railiance-master/workplans/RAILIANCE-WP-0017-rail-rapp-reef-repo-separation.md`.
|
||||
Loading…
Add table
Add a link
Reference in a new issue