Bootstrap grouped home reef repo

workplans/REEF-RAILIANCE-WP-0001-bootstrap-and-wave1-import.md

@@ -0,0 +1,107 @@
+---
+id: REEF-RAILIANCE-WP-0001
+type: workplan
+title: "Bootstrap reef-railiance and import the wave-1 grouped substrate surface"
+domain: financials
+repo: reef-railiance
+status: active
+owner: codex
+topic_slug: railiance
+created: "2026-07-26"
+updated: "2026-07-26"
+---
+
+# REEF-RAILIANCE-WP-0001 - Bootstrap reef-railiance and import the wave-1 grouped substrate surface
+
+## Goal
+
+Turn `reef-railiance` into the concrete home of the first grouped Railiance
+home reef.
+
+## Boundaries
+
+This workplan may bootstrap the repo, publish the initial reef declaration,
+and import the first source-backed grouped substrate facts from
+`railiance-infra`.
+
+It must not:
+
+- absorb generic S1 provisioning or inventory ownership from `railiance-infra`
+- pretend one repo per server is the default reef model
+- normalize generic rail or platform behavior into this repo
+
+## T01 - Establish the repo baseline and reef declaration
+
+```task
+id: REEF-RAILIANCE-WP-0001-T01
+status: done
+priority: high
+```
+
+Create the baseline repo files, the initial reef declaration, and the first
+wave-1 contract summary.
+
+Acceptance:
+
+- baseline repo files exist
+- `declarations/reef.yaml` exists
+- the repo states its boundary with `railiance-infra`
+
+2026-07-26: Created the initial repo baseline, grouped reef declaration, and
+wave-1 contract summary.
+
+## T02 - Import the first source-backed grouped substrate facts
+
+```task
+id: REEF-RAILIANCE-WP-0001-T02
+status: done
+priority: high
+```
+
+Bring the reviewed first grouped-substrate fact set into this repo in a
+migration-safe sequence.
+
+Acceptance:
+
+- the import sequence is anchored in the reviewed S1 source map
+- imported material stays reef-local rather than generic S1 ownership
+- the repo becomes a real grouped home reef rather than only a shell
+
+2026-07-26: Imported the first grouped substrate facts from `railiance-infra`,
+including the current member identity from `inventory/servers.yaml`, the
+grouped home-reef rollout stance from `docs/reef-first-wave-source-map.md`,
+and the operational substrate evidence from ADR-004.
+
+## T03 - Prepare the retained S1 handoff from `railiance-infra`
+
+```task
+id: REEF-RAILIANCE-WP-0001-T03
+status: wait
+priority: medium
+```
+
+Define the thin compatibility path that keeps current operators functional
+while reef-localization proceeds.
+
+Acceptance:
+
+- the retained S1 surface is explicit
+- current operators do not need a flag day
+- the retained S1 surface stays narrow and temporary
+
+## T04 - Register `reef-railiance` in State Hub and Fabric
+
+```task
+id: REEF-RAILIANCE-WP-0001-T04
+status: wait
+priority: medium
+```
+
+Register the repo from classification and add it to the Fabric repository
+registry with `reef`-family metadata.
+
+Acceptance:
+
+- State Hub recognizes the repo and its workplan
+- Fabric recognizes the repo as `repo_family: reef`
+- ownership, primary-rail, and substrate-kind metadata are visible