Bootstrap grouped home reef repo

substrate/identity.yaml

@@ -0,0 +1,16 @@
+reef_id: reef-railiance
+display_name: Railiance Home Reef
+substrate_kind: server-group
+ownership_repo: railiance-infra
+lifecycle_state: active
+criticality: high
+primary_rail: rail-kubernetes
+current_members:
+  - Railiance01
+current_role: Grouped home substrate for Kubernetes-first Railiance workloads.
+source_of_truth:
+  repo: railiance-infra
+  paths:
+    - inventory/servers.yaml
+    - docs/reef-first-wave-source-map.md
+    - docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md

substrate/topology.yaml

@@ -0,0 +1,22 @@
+reef_id: reef-railiance
+membership_policy: Add Railiance home servers here when they share one durable home-substrate boundary.
+members:
+  - member_id: Railiance01
+    role: first-current-member
+    provider: HostEurope
+    ip: 92.205.62.239
+    ssh_user: tegwick
+    evidence:
+      - repo: railiance-infra
+        path: inventory/servers.yaml
+      - repo: railiance-infra
+        path: docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md
+access_surfaces:
+  - type: ssh
+    member: Railiance01
+    user: tegwick
+  - type: kubernetes-runtime
+    rail: rail-kubernetes
+unresolved_questions:
+  - Which future Railiance servers should join this grouped home reef first?
+  - At what point would member divergence justify splitting this reef?