reef-railiance/docs/source-import-plan.md

54 lines
1.6 KiB
Markdown
Raw Normal View History

2026-07-26 02:38:10 +02:00
# Source Import Plan
## Purpose
Record which reviewed source materials are expected to seed this repo.
## Imported In The Current Wave
Imported source documents from `railiance-master`:
- `docs/reef-first-wave-rollout.md`
- `docs/reef-substrate-model.md`
- `docs/repo-family-bootstrap-contract.md`
Imported source documents from `railiance-infra`:
- `docs/reef-first-wave-source-map.md`
- `inventory/servers.yaml`
- `docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md`
## Pending First-Wave Imports
Expected future source surfaces from `railiance-infra`:
- reef-localized runbooks once they stop being generic S1 ownership material
- any additional source-backed member facts for future Railiance home servers
- explicit grouped `rapp` binding decisions when they become substrate-local
## Deferred Migration Debt
Do not import these into `reef-railiance` as part of wave 1:
- generic S1 provisioning or inventory ownership
- generic Kubernetes runtime behavior
- workload packaging or platform governance
## Current Migration-Window Compatibility
During wave 1:
- `reef-railiance` is the canonical home for grouped home-reef identity,
topology, hosted-rail stance, and future `rapp` bindings
- `railiance-infra` remains the canonical owner of raw inventory, provisioning,
and broader S1 source-backed host facts
- raw host-fact changes should be made in `railiance-infra` first and then
projected here when they affect the grouped reef boundary
See `docs/retained-s1-handoff.md` for the active handoff contract.
2026-07-26 02:38:10 +02:00
## Rule
Imports into this repo should preserve the grouped home-reef boundary already
reviewed in `railiance-master` and `railiance-infra`.