Bootstrap grouped home reef repo

docs/README.md

@@ -0,0 +1,5 @@
+# reef-railiance Docs
+
+- `wave-1-contract.md` — current grouped home-reef contract and boundary summary
+- `source-backed-substrate-facts.md` — source-backed first-wave facts imported from S1
+- `source-import-plan.md` — source material and migration direction from existing repos

docs/source-backed-substrate-facts.md

@@ -0,0 +1,33 @@
+# Source-Backed Substrate Facts
+
+## Purpose
+
+Record the first source-backed facts imported into `reef-railiance` for the
+grouped home reef bootstrap.
+
+## Imported Facts
+
+From `railiance-infra/inventory/servers.yaml`:
+
+- current first member: `Railiance01`
+- member IP: `92.205.62.239`
+- member SSH user: `tegwick`
+
+From `railiance-infra/docs/reef-first-wave-source-map.md`:
+
+- this repo represents the grouped Railiance home reef rather than a singleton
+  host repo
+- `rail-kubernetes` is the first primary rail stance
+- additional Railiance home servers should join this reef when they share the
+  same lifecycle and workload-placement boundary
+
+From `railiance-infra/docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md`:
+
+- Forgejo production and the in-cluster Actions runner already use
+  `railiance01` as a Kubernetes-first operational substrate
+
+## Explicit Gaps
+
+- only one source-backed member is declared today
+- there is still no dedicated `host_vars/Railiance01.yml`
+- future grouped members and split criteria remain explicit follow-up work

docs/source-import-plan.md

@@ -0,0 +1,40 @@
+# Source Import Plan
+
+## Purpose
+
+Record which reviewed source materials are expected to seed this repo.
+
+## Imported In The Current Wave
+
+Imported source documents from `railiance-master`:
+
+- `docs/reef-first-wave-rollout.md`
+- `docs/reef-substrate-model.md`
+- `docs/repo-family-bootstrap-contract.md`
+
+Imported source documents from `railiance-infra`:
+
+- `docs/reef-first-wave-source-map.md`
+- `inventory/servers.yaml`
+- `docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md`
+
+## Pending First-Wave Imports
+
+Expected future source surfaces from `railiance-infra`:
+
+- reef-localized runbooks once they stop being generic S1 ownership material
+- any additional source-backed member facts for future Railiance home servers
+- explicit grouped `rapp` binding decisions when they become substrate-local
+
+## Deferred Migration Debt
+
+Do not import these into `reef-railiance` as part of wave 1:
+
+- generic S1 provisioning or inventory ownership
+- generic Kubernetes runtime behavior
+- workload packaging or platform governance
+
+## Rule
+
+Imports into this repo should preserve the grouped home-reef boundary already
+reviewed in `railiance-master` and `railiance-infra`.

docs/wave-1-contract.md

@@ -0,0 +1,57 @@
+# Wave-1 Railiance Home Reef Contract
+
+## Purpose
+
+Summarize the initial grouped home-reef contract `reef-railiance` owns in wave
+1.
+
+This repo starts from already-reviewed source documents rather than inventing a
+new substrate model:
+
+- `railiance-master/docs/reef-first-wave-rollout.md`
+- `railiance-master/docs/reef-substrate-model.md`
+- `railiance-infra/docs/reef-first-wave-source-map.md`
+
+## What `reef-railiance` Owns
+
+Wave 1 assigns these concerns to the reef:
+
+- the grouped Railiance home-substrate identity
+- current member and topology facts for that grouped reef
+- the default hosted-rail statement for the home substrate
+- future grouped `rapp` bindings for that substrate
+- reef-local runbooks, overlays, and evidence when they become substrate-owned
+
+## What Stays In `railiance-infra`
+
+Wave 1 keeps these concerns in the canonical S1 ownership repo:
+
+- server inventory authority
+- OS provisioning and hardening logic
+- SSH key and convergence mechanics
+- source-backed server facts that are not yet reef-localized
+- future split criteria that still depend on broader S1 review
+
+## Published Substrate Assumptions
+
+Wave 1 `reef-railiance` may assume:
+
+- `Railiance01` is the first current member
+- `rail-kubernetes` is the first primary rail stance
+- additional Railiance home servers may join when they share the same grouped
+  substrate boundary
+
+Wave 1 `reef-railiance` must not assume:
+
+- that every future Railiance server belongs here automatically
+- that platform or workload ownership moves into this repo
+- that grouped membership is permanent if lifecycle or security boundaries split
+
+## Migration Constraint
+
+Until the extraction is complete, `railiance-infra` remains the canonical S1
+source of truth.
+
+`reef-railiance` should become the durable grouped substrate home first. Only
+then should additional bindings, runbooks, and substrate-local overlays move
+here in a migration-safe sequence.