coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish first repo-family materialization wave

Browse source
This commit is contained in:
codex 2026-07-26 08:51:13 +02:00
parent 54b8cf4829
commit b6c24a7195
10 changed files with 108 additions and 60 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/adr/ADR-0004-first-wave-reef-rollout.md
View file

@ -20,7 +20,7 @@ At the same time, S1 ownership is ambiguous because `railiance-hosts` and
The first-wave reef rollout is:
1. `reef-railiance01`
1. `reef-railiance`
2. `reef-coulombcore`
3. `reef-ops-workstations`
@ -33,8 +33,8 @@ frozen, or reduced later rather than as a second canonical S1 architecture home.
### Positive
- Railiance gets a primary home-reef seed without waiting for a multi-node
future.
- Railiance gets a grouped home-reef seed whose name remains stable as more
home servers are added.
- Transitional CoulombCore reality is acknowledged without being treated as the
long-term preferred production pattern.
- Operator edge compute is modeled without defaulting to one repo per machine.
@ -43,8 +43,8 @@ frozen, or reduced later rather than as a second canonical S1 architecture home.
### Required Follow-On Work
- Create repo-local rollout work for the first reef repos.
- Decide whether Railiance01 later remains a singleton reef or becomes part of
a grouped home reef.
- Define how additional Railiance home servers join `reef-railiance` and what
future split criteria would justify narrower reefs.
- Plan the `railiance-hosts` cleanup direction relative to `railiance-infra`.
### Constraints