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

Publish cluster resource evidence and gate ThreePhoenix
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
This commit is contained in:
codex 2026-08-22 12:34:25 +02:00
parent bfc991258d
commit ea0452b9a9
11 changed files with 2768 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

21
workplans/RCLUSTER-WP-0007-threephoenix-ha-cluster.md
View file

@ -10,7 +10,7 @@ topic_slug: railiance
repo_goal_id: "6ea441f7-7fe3-4598-922b-38baf20c0580"
state_hub_workstream_id: "9e208376-23f1-40c7-9813-fac1f7d6ad3b"
created: "2026-02-25"
updated: "2026-08-15"
updated: "2026-08-22"
related:
- REEF-RAILIANCE-WP-0003
- RAIL-BS-WP-0014
@ -48,6 +48,21 @@ grant.
The bootstrap copy of this file is retired. Do not re-open
`RCLUSTER-WP-0007` in `railiance-bootstrap`.
## Implementation gate
This workplan remains `backlog`; its tasks must not move to `progress` until
the preflight in `docs/threephoenix-implementation-gate.md` passes. In
particular, three independent source-backed reef members must be approved,
provisioned, and S1-converged, with their shared power, storage, host, and
network dependencies recorded. The current Railiance01 node plus guests on one
physical host do not satisfy that gate.
Passing the gate also requires an approved private inter-node network design,
join-token custody/rotation through the platform custody path, and explicit
operator approval for destructive node actions. This repository must not buy
provider capacity, open public listeners, install Longhorn, or mutate the live
single-node cluster merely to make the target appear ready.
## Why This Belongs Before Forgejo
Forgejo will be the source forge, package base, and Actions surface for the
@ -267,6 +282,10 @@ This workplan should precede the Forgejo production cutover. It should also
shape the Stage 2 and Stage 3 gates in `RAIL-BS-WP-0006` so canaries and
promotions operate against the real HA substrate.
The first executable dependency is the machine-checkable/manual preflight in
`docs/threephoenix-implementation-gate.md`; until it passes, this plan is design
and dependency preparation only.
It is the substrate dependency for:
- `reef-railiance/REEF-RAILIANCE-WP-0003` T04. After the S2 drill passes, the