58 lines
2.2 KiB
Markdown
58 lines
2.2 KiB
Markdown
# Retained S1 Handoff
|
|
|
|
## Purpose
|
|
|
|
Define the migration-window handoff between `reef-railiance` and
|
|
`railiance-infra` while grouped reef localization is still in flight.
|
|
|
|
Wave 1 makes `reef-railiance` the durable owner of the grouped Railiance
|
|
home-reef identity, topology, hosted-rail statement, and future `rapp`
|
|
bindings. `railiance-infra` remains the canonical S1 owner of raw inventory,
|
|
provisioning, hardening, and source-backed host facts that have not yet been
|
|
localized into the reef repo.
|
|
|
|
## Canonical Reef Surface
|
|
|
|
Use `reef-railiance` as the canonical home for:
|
|
|
|
- `declarations/reef.yaml`
|
|
- `substrate/identity.yaml`
|
|
- `substrate/topology.yaml`
|
|
- `bindings/rails.yaml`
|
|
- `bindings/rapps.yaml`
|
|
- repo-local grouped-boundary docs, questions, and future reef-local runbooks
|
|
|
|
New grouped-reef behavior, membership interpretation, hosted-rail stance, and
|
|
future `rapp` binding decisions should land here first.
|
|
|
|
## Retained S1 Surface
|
|
|
|
Still owned by `railiance-infra`:
|
|
|
|
- `inventory/servers.yaml` as the raw server identity source
|
|
- Terraform/cloud-init/Ansible provisioning and convergence logic
|
|
- generic OS hardening and substrate verification
|
|
- canonical S1 docs such as `docs/reef-first-wave-source-map.md`
|
|
- source-backed host facts that are still broader than the grouped home-reef
|
|
boundary
|
|
|
|
## Current Compatibility Path
|
|
|
|
Current operators do not need a flag day:
|
|
|
|
1. Continue using `railiance-infra` for server provisioning, inventory edits,
|
|
SSH/bootstrap mechanics, and raw host-fact maintenance.
|
|
2. Use `reef-railiance` for grouped home-reef identity, topology, hosted-rail
|
|
stance, and reef-local `rapp` binding decisions.
|
|
3. When a raw server fact changes, update `railiance-infra` first, then refresh
|
|
the reef-local projection only where that fact affects the grouped reef
|
|
boundary.
|
|
4. Keep unresolved grouped-membership or split criteria explicit in this repo
|
|
rather than forcing one permanent repo per server.
|
|
|
|
## Exit Condition
|
|
|
|
The migration window can end once the reef-specific interpretation no longer
|
|
depends on broader S1 docs for routine operator understanding, and the
|
|
remaining source-backed member facts needed by the grouped reef have been
|
|
localized cleanly.
|