---
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: finished
owner: codex
topic_slug: railiance
created: "2026-07-26"
updated: "2026-07-26"
state_hub_workstream_id: "da64c718-68bf-4719-aa42-fcf26687ab23"
---

# 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
state_hub_task_id: "c7f85080-527c-48ec-bffc-0bb045b08a62"
```

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
state_hub_task_id: "acb010ad-a430-414c-8f63-06b13cdc00f7"
```

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: done
priority: medium
state_hub_task_id: "c6365200-9e2b-4299-9464-0620d94aad2a"
```

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

2026-07-26: Added `docs/retained-s1-handoff.md` to define the migration-window
split with `railiance-infra`. `reef-railiance` is now the canonical home for
the grouped home-reef identity, topology, hosted-rail stance, and future
`rapp` bindings, while `railiance-infra` retains raw inventory, provisioning,
and broader S1 source-backed host facts. `README.md`, `docs/README.md`,
`docs/wave-1-contract.md`, `docs/source-import-plan.md`, and `SCOPE.md` now
point operators at the explicit no-flag-day handoff.

## T04 - Register `reef-railiance` in State Hub and Fabric

```task
id: REEF-RAILIANCE-WP-0001-T04
status: done
priority: medium
state_hub_task_id: "21b7e7e9-1cb5-412b-88f1-f8e1a4689576"
```

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

2026-07-26: Registered `reef-railiance` in State Hub from
`.repo-classification.yaml`, generated `.custodian-brief.md` and
`WORK-RECORDS.md`, reconciled the local grouped-reef bootstrap with the
existing remote `main`, and pushed the clean history to
`forgejo-remote:coulomb/reef-railiance.git`. Added the repo to
`railiance-fabric/registry/railiance-repos.yaml` and ran a targeted live
registry sync against `http://127.0.0.1:8765`. Fabric now stores
`reef-railiance` as a registered repo with `repo_family: reef`,
`ownership_repo: railiance-infra`, `primary_rail: rail-kubernetes`,
`substrate_kind: server-group`, and snapshot `id: 97`.