codex
9477319783
These workplans exist only in the retired local hub. Their random pre-ADR-007 identifiers are refused by C-06 as stale references, so they cannot be registered. Deriving from the canonical record id takes no identity from anything: central does not hold them and the old ids die with the cache. Records central already holds were deliberately left untouched. Refs CUST-WP-0068-T06 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
131 lines
4.1 KiB
Markdown
131 lines
4.1 KiB
Markdown
---
|
|
id: RAIL-HO-WP-0007
|
|
type: workplan
|
|
title: "First reef rollout and S1 canonicalization"
|
|
domain: financials
|
|
repo: railiance-infra
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: railiance
|
|
created: "2026-07-25"
|
|
updated: "2026-07-26"
|
|
state_hub_workstream_id: "9447ace8-b341-5f02-95c4-7ae4d062e9b6"
|
|
---
|
|
|
|
# RAIL-HO-WP-0007 - First reef rollout and S1 canonicalization
|
|
|
|
## Goal
|
|
|
|
Prepare the S1 side of the first reef rollout while making `railiance-infra`
|
|
the clear canonical S1 ownership repo for future architecture work.
|
|
|
|
This follows the rollout defined in
|
|
`/home/worsch/railiance-master/docs/reef-first-wave-rollout.md`.
|
|
|
|
## Boundaries
|
|
|
|
This workplan may:
|
|
|
|
- prepare the S1 cleanup direction between `railiance-infra` and
|
|
`railiance-hosts`
|
|
- define the substrate identity data future reef repos will need
|
|
- prepare the first rollout surface for `reef-railiance`,
|
|
`reef-coulombcore`, and `reef-ops-workstations`
|
|
|
|
It must not:
|
|
|
|
- silently retire `railiance-hosts` without an explicit migration direction
|
|
- move S2/S3/S5 workload ownership into S1
|
|
- create one repo per machine by default
|
|
|
|
## T01 - Record `railiance-infra` as canonical S1 for future architecture
|
|
|
|
```task
|
|
id: RAIL-HO-WP-0007-T01
|
|
status: done
|
|
priority: high
|
|
state_hub_task_id: "5fc12f17-3af6-5fed-86c3-32e9f9c1c054"
|
|
```
|
|
|
|
Document the S1 direction so new architecture work anchors on `railiance-infra`
|
|
rather than treating `railiance-hosts` and `railiance-infra` as equally
|
|
canonical.
|
|
|
|
Done when the repo has an explicit cleanup or freeze direction for the duplicate
|
|
S1 line.
|
|
|
|
2026-07-25: Recorded `railiance-infra` as the canonical S1 ownership repo in
|
|
`SCOPE.md`, `README.md`, and `docs/reef-first-wave-source-map.md`, while
|
|
leaving historical `railiance-hosts` references in superseded ADRs and archived
|
|
records as non-authoritative context.
|
|
|
|
## T02 - Prepare substrate identity data for the first reefs
|
|
|
|
```task
|
|
id: RAIL-HO-WP-0007-T02
|
|
status: done
|
|
priority: high
|
|
state_hub_task_id: "83132d76-462f-5835-a034-69102c061f6b"
|
|
```
|
|
|
|
Prepare the minimum substrate identity and topology data needed for:
|
|
|
|
- `reef-railiance`
|
|
- `reef-coulombcore`
|
|
- `reef-ops-workstations`
|
|
|
|
Done when the future reefs have a clear source-backed S1 starting point for
|
|
identity, membership, and lifecycle context.
|
|
|
|
2026-07-25: Added `docs/reef-first-wave-source-map.md`, which extracts the
|
|
current S1 identity and lifecycle starting facts for `reef-railiance`,
|
|
`reef-coulombcore`, and `reef-ops-workstations` from live inventory, host vars,
|
|
and runbook sources.
|
|
|
|
## T03 - Separate stable substrate facts from transitional labels
|
|
|
|
```task
|
|
id: RAIL-HO-WP-0007-T03
|
|
status: done
|
|
priority: medium
|
|
state_hub_task_id: "d26377c9-5c7c-5e3c-96b8-d032118a144c"
|
|
```
|
|
|
|
Record which substrate facts are stable enough for reef rollout now and which
|
|
transitional nicknames or legacy interpretations must remain provisional.
|
|
|
|
Done when the future reef repos can start from stable operational facts instead
|
|
of from narrative labels.
|
|
|
|
2026-07-25: The new reef source map now separates stable source-backed facts
|
|
from provisional labels such as future grouped-home-reef interpretations or
|
|
nickname taxonomies like "associate", "sidecar", and "comet".
|
|
|
|
## T04 - Prepare the first reef creation handoff
|
|
|
|
```task
|
|
id: RAIL-HO-WP-0007-T04
|
|
status: done
|
|
priority: medium
|
|
state_hub_task_id: "5a42eb53-6a8c-507e-ad9e-ec51a308d9c9"
|
|
```
|
|
|
|
Prepare the handoff for creating the first reef repos and for reducing the S1
|
|
duplication risk during that rollout.
|
|
|
|
Done when the first reef repos can be created without reopening the
|
|
`hosts`-versus-`infra` ambiguity.
|
|
|
|
2026-07-25: `docs/reef-first-wave-source-map.md` now provides the initial reef
|
|
creation handoff: source-backed identity, substrate kind, lifecycle stance,
|
|
primary rail stance where applicable, and explicit unresolved questions for
|
|
each first-wave reef.
|
|
|
|
2026-07-26: Updated the first home-reef target from singleton
|
|
`reef-railiance01` to grouped `reef-railiance` so the home substrate can
|
|
represent multiple Railiance servers under one reef boundary.
|
|
|
|
## Notes
|
|
|
|
This workplan is repo-local. The framework-level reef decision and sequencing
|
|
remain in `railiance-master/workplans/RMASTER-WP-0017-rail-rapp-reef-repo-separation.md`.
|