coulomb/reef-railiance
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The railiance repo to represent its own home reef
7 commits 1 branch 0 tags 185 KiB
Find a file
custodian-sync e6bede5798 chore(consistency): sync task status from DB [auto] 
Updated by fix-consistency on 2026-07-26:
  - update .custodian-brief.md for reef-railiance
2026-07-26 10:38:21 +02:00
bindings Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
declarations Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
docs Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
substrate Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
workplans Close reef-railiance registration task 2026-07-26 08:49:44 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-26 10:38:21 +02:00
.repo-classification.yaml Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
AGENTS.md Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
CLAUDE.md Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
INTENT.md Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
LICENSE Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
README.md Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
SCOPE.md Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
WORK-RECORDS.md Sync reef-railiance work records 2026-07-26 09:00:52 +02:00

README.md

reef-railiance

Wave-1 grouped home reef for Railiance-managed server substrates.

Purpose

reef-railiance is the first concrete reef-* repo in Railiance. It owns the grouped home-substrate boundary that should describe current and future Railiance home servers without creating one repo per machine.

This repo exists to hold:

  • the source-controlled reef declaration for the Railiance home substrate
  • grouped substrate identity and topology facts
  • rail and workload binding surfaces for this reef
  • the migration path from source-backed S1 facts in railiance-infra

Boundary

reef-railiance does not own:

  • generic S1 provisioning, hardening, or server inventory authority
  • generic Kubernetes runtime ownership
  • platform-service governance or workload packaging
  • one permanent repo per host in the Railiance home substrate

Those concerns stay with railiance-infra, railiance-cluster, railiance-platform, or the relevant rapp-* repo.

Current Status

This repo is in first-wave bootstrap.

The boundary and source material come from:

  • railiance-master/docs/reef-first-wave-rollout.md
  • railiance-master/docs/reef-substrate-model.md
  • railiance-infra/docs/reef-first-wave-source-map.md

Initial Layout

  • declarations/reef.yaml — source-controlled reef contract
  • substrate/ — grouped substrate identity and topology facts
  • bindings/ — rail and rapp binding surfaces for this reef
  • docs/ — wave-1 contract and source import plan
  • workplans/ — repo-local execution work