diff --git a/README.md b/README.md index 58a940e..991e18f 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ with your single **age** master key (which you keep in your password manager). The minimal server registry in `inventory/servers.yaml` is the source of truth. Future `reef-*` repos will model purpose-bound substrate boundaries such as -`reef-railiance01` or `reef-ops-workstations`, but the source-backed S1 +`reef-railiance` or `reef-ops-workstations`, but the source-backed S1 inventory, hardening baseline, and OS convergence facts stay here. ## Quickstart diff --git a/docs/reef-first-wave-source-map.md b/docs/reef-first-wave-source-map.md index bcd1731..dc49111 100644 --- a/docs/reef-first-wave-source-map.md +++ b/docs/reef-first-wave-source-map.md @@ -49,24 +49,27 @@ minimum operational facts needed to seed the first reef repos. ## First-Wave Reef Source Map -### `reef-railiance01` +### `reef-railiance` Stable facts available now: -- server identity: `Railiance01` -- IP: `92.205.62.239` -- SSH user: `tegwick` +- current first member: `Railiance01` +- current member IP: `92.205.62.239` +- current member SSH user: `tegwick` - authoritative source today: `inventory/servers.yaml` - current role in the ecosystem: the clearest home for new Kubernetes-first production-oriented workloads - operational evidence in this repo: ADR-004 records Forgejo production and Actions runner placement on `railiance01` - primary rail stance for first rollout: `rail-kubernetes` +- grouped-home intent: additional Railiance servers should be represented here + when they share the same home substrate lifecycle and workload-placement + policy Known gaps that must stay explicit: +- only one source-backed member (`Railiance01`) is recorded today - no dedicated `host_vars/Railiance01.yml` exists yet -- the long-term grouped-home-reef shape is not decided yet - whether later `rail-knative` shares this reef or warrants separation remains a workload- and security-driven decision @@ -112,19 +115,20 @@ Operational interpretation for rollout: Stable now: - the first-wave reef set: - - `reef-railiance01` + - `reef-railiance` - `reef-coulombcore` - `reef-ops-workstations` - `railiance-infra` as canonical S1 ownership source - inventory-backed server identity for `Railiance01` and `CoulombCore` - operator workstation responsibilities for age key custody, bridge usage, and attended control-plane actions -- `rail-kubernetes` as the first primary rail stance for `reef-railiance01` +- `rail-kubernetes` as the first primary rail stance for `reef-railiance` +- `Railiance01` as the first current member of the grouped Railiance home reef Provisional for now: -- whether `reef-railiance01` later widens into a grouped `reef-railiance-home` -- whether `rail-knative` should share `reef-railiance01` or later move to a +- the future member set beyond `Railiance01` +- whether `rail-knative` should share `reef-railiance` or later move to a separate reef - narrative labels such as "associate", "sidecar", or "comet" - any claim that CoulombCore has a settled long-term role beyond being an @@ -136,11 +140,11 @@ Each first-wave reef repo should start with: - substrate identity from the source-backed facts above - declared substrate kind: - - `server` for `reef-railiance01` + - `server-group` for `reef-railiance` - `server` for `reef-coulombcore` - `workstation-group` for `reef-ops-workstations` - lifecycle stance: - - primary home-reef seed for `reef-railiance01` + - primary grouped home-reef seed for `reef-railiance` - transitional legacy or fallback reef for `reef-coulombcore` - grouped operator-edge reef for `reef-ops-workstations` - initial primary rail statement where applicable diff --git a/workplans/RAIL-HO-WP-0007-first-reef-rollout-and-s1-canonicalization.md b/workplans/RAIL-HO-WP-0007-first-reef-rollout-and-s1-canonicalization.md index 5242252..94a1c3b 100644 --- a/workplans/RAIL-HO-WP-0007-first-reef-rollout-and-s1-canonicalization.md +++ b/workplans/RAIL-HO-WP-0007-first-reef-rollout-and-s1-canonicalization.md @@ -8,7 +8,7 @@ status: finished owner: codex topic_slug: railiance created: "2026-07-25" -updated: "2026-07-25" +updated: "2026-07-26" state_hub_workstream_id: "42c28d2e-6e1b-4ec4-b191-8ba9f09899da" --- @@ -29,7 +29,7 @@ This workplan may: - prepare the S1 cleanup direction between `railiance-infra` and `railiance-hosts` - define the substrate identity data future reef repos will need -- prepare the first rollout surface for `reef-railiance01`, +- prepare the first rollout surface for `reef-railiance`, `reef-coulombcore`, and `reef-ops-workstations` It must not: @@ -70,7 +70,7 @@ state_hub_task_id: "aa32fb8d-adab-41d3-bb8d-13167df7cc44" Prepare the minimum substrate identity and topology data needed for: -- `reef-railiance01` +- `reef-railiance` - `reef-coulombcore` - `reef-ops-workstations` @@ -78,7 +78,7 @@ Done when the future reefs have a clear source-backed S1 starting point for identity, membership, and lifecycle context. 2026-07-25: Added `docs/reef-first-wave-source-map.md`, which extracts the -current S1 identity and lifecycle starting facts for `reef-railiance01`, +current S1 identity and lifecycle starting facts for `reef-railiance`, `reef-coulombcore`, and `reef-ops-workstations` from live inventory, host vars, and runbook sources. @@ -121,6 +121,10 @@ creation handoff: source-backed identity, substrate kind, lifecycle stance, primary rail stance where applicable, and explicit unresolved questions for each first-wave reef. +2026-07-26: Updated the first home-reef target from singleton +`reef-railiance01` to grouped `reef-railiance` so the home substrate can +represent multiple Railiance servers under one reef boundary. + ## Notes This workplan is repo-local. The framework-level reef decision and sequencing