2026-08-18 22:36:39 +02:00
|
|
|
# Cleanup packet — railiance-hosts
|
|
|
|
|
|
2026-08-31 21:34:23 +02:00
|
|
|
From PNEX-WP-0003-T05. Shared with `railiance-infra`.
|
2026-08-18 22:36:39 +02:00
|
|
|
|
|
|
|
|
## Already ruled
|
|
|
|
|
|
|
|
|
|
- `docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md` — superseded by
|
|
|
|
|
ADR-003. Add YAML `status: superseded` so the body and metadata agree.
|
|
|
|
|
Byte-identical copy exists in railiance-infra.
|
|
|
|
|
|
|
|
|
|
## Conflict — do not publish both
|
|
|
|
|
|
|
|
|
|
These files are **byte-identical** and **accepted** in both
|
|
|
|
|
`railiance-hosts` and `railiance-infra`:
|
|
|
|
|
|
|
|
|
|
- `ADR-003-railiance-5repo-stack-architecture.md`
|
|
|
|
|
- `ADR-004-forgejo-in-cluster-actions-runner.md`
|
|
|
|
|
|
|
|
|
|
Pick one publication source. The other becomes `superseded` or a
|
|
|
|
|
pointer, not a second current document. If the stack story moved to
|
|
|
|
|
`railiance-master`, say so.
|
|
|
|
|
|
|
|
|
|
Who rules: railiance-hosts, railiance-infra, or railiance-master.
|
|
|
|
|
Nothing is published from these two ADRs until that ruling lands.
|
