Rename first home reef target to reef-railiance

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