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

Mark as superseded by railiance-infra
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Verified 2026-08-11: railiance-hosts and railiance-infra are distinct remotes
with unrelated git histories but byte-identical INTENT.md and near-identical
content, and this repo has zero files that are not also in railiance-infra. It
has been quiet since 2026-07-30 while railiance-infra continued.

The INTENT asserted this repo IS the canonical S1 substrate home, which made it
the most actively misleading file in the family - the hub still carries an S1
goal against it. Adds a superseded banner rather than deleting anything, since
retirement is railiance-master's call and needs a git-history check plus a move
of the live goal to railiance-infra first.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-11 23:19:51 +02:00
parent 880d229db0
commit 25bd3ba912
1 changed files with 24 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
INTENT.md
View file

@ -7,6 +7,30 @@
---
> **⚠ SUPERSEDED — do not start new work here.**
>
> This repository is superseded by **`railiance-infra`**, which is the canonical
> S1 Infrastructure Substrate home. Verified 2026-08-11: the two are distinct
> remotes with **unrelated git histories** but byte-identical `INTENT.md` and
> near-identical content, and `railiance-hosts` has **zero files that are not
> also in `railiance-infra`**. This repo has been quiet since 2026-07-30 while
> `railiance-infra` continued.
>
> It was one of four repos (`bootstrap`, `cluster`, `hosts`, `infra`) created by
> copying working trees as the S1/S2 layering idea emerged — the INTENT was
> copied along with everything else, which is why this file reads as though this
> repo is the canonical substrate home. It is not.
>
> **Retirement is pending** in `railiance-master`. Before deletion, two things
> must happen: its git history must be checked for anything not carried into
> `railiance-infra`, and its live State Hub goal *"Secure Single-Server
> Bootstrap at HostEurope"* must be moved to `railiance-infra` or it will keep
> resurfacing as unstarted S1 work.
>
> Context: `railiance-platform/ArchitectureBlueprint.md` section 4.
---
## One-liner
**The infrastructure substrate — turning bare machines into hardened, verified, ready-to-build-on servers, declaratively and reproducibly.**