The railiance repo to represent its own home reef
Find a file
codex dcf51b3028 migrate reef work record identifiers
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
2026-08-31 14:00:19 +02:00
bindings Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00
declarations Finalize reef exposure grants 2026-08-21 01:35:28 +02:00
docs Finish reef-railiance first-wave handoff 2026-07-26 10:39:39 +02:00
evidence Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00
schemas Add Knative and Qonto admission evidence 2026-07-26 13:34:56 +02:00
substrate Bootstrap grouped home reef repo 2026-07-26 02:40:01 +02:00
tests Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00
tools Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00
workplans migrate reef work record identifiers 2026-08-31 14:00:19 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-31 13:35:05 +02:00
.gitignore Ignore generated Python artifacts 2026-07-26 23:17:53 +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 Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:56:52 +02:00
README.md Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00
SCOPE.md Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00
WORK-RECORDS.md Reconcile reef bindings and evidence 2026-08-21 02:01:49 +02:00

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 now owns the wave-1 grouped home-reef boundary for Railiance.

The rail and rApp binding projections were reconciled against their owning family declarations on 2026-08-21. Live evidence still shows one Ready member carrying the Kubernetes control-plane and etcd roles, so the Qonto binding remains verified and private rather than production-approved.

The retained S1 compatibility path while reef localization is still in flight is documented in docs/retained-s1-handoff.md.

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
  • docs/retained-s1-handoff.md — migration-window split with railiance-infra
  • workplans/ — repo-local execution work