Rename first home reef target to reef-railiance

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