Establish Railiance architecture home

This commit is contained in:
codex 2026-07-25 10:54:37 +02:00
parent dd54aee0da
commit 8022665b35
22 changed files with 2925 additions and 1 deletions

View file

@ -1,3 +1,38 @@
# railiance-master
Framework architecture for railiance applications, railiance rails, railiance tooling. This repo explains and evolves the concepts in and around railiance.
Architecture home for the Railiance framework.
This repository defines how Railiance concepts map to repositories, how the
different repo families compose, and where new architecture decisions should be
recorded before they are spread across implementation repos.
## Current Architecture Baseline
- [docs/repository-axes.md](docs/repository-axes.md)
- [docs/reef-substrate-model.md](docs/reef-substrate-model.md)
- [docs/rail-kubernetes-boundary.md](docs/rail-kubernetes-boundary.md)
- [docs/rapp-first-wave-candidates.md](docs/rapp-first-wave-candidates.md)
- [docs/reef-first-wave-rollout.md](docs/reef-first-wave-rollout.md)
- [docs/fabric-state-hub-adaptation.md](docs/fabric-state-hub-adaptation.md)
- [docs/adr/ADR-0001-repository-prefix-architecture.md](docs/adr/ADR-0001-repository-prefix-architecture.md)
- [docs/adr/ADR-0002-rail-kubernetes-wave-1-boundary.md](docs/adr/ADR-0002-rail-kubernetes-wave-1-boundary.md)
- [docs/adr/ADR-0003-rapp-first-wave-selection.md](docs/adr/ADR-0003-rapp-first-wave-selection.md)
- [docs/adr/ADR-0004-first-wave-reef-rollout.md](docs/adr/ADR-0004-first-wave-reef-rollout.md)
## Current Explorations
- [history/260724-InitialExplorationOfOperationModels.md](history/260724-InitialExplorationOfOperationModels.md)
- [history/260724-InitialExplorationOfWrapperConcepts.md](history/260724-InitialExplorationOfWrapperConcepts.md)
## Purpose
`railiance-master` is the canonical place to define:
- repo-family vocabulary such as `railiance-*`, `rail-*`, `rapp-*`, and `reef-*`
- cross-repo architectural boundaries
- the relationship between ownership, execution mode, workload packaging, and
substrate realities
- the migration direction when current repos must be split or renamed
Implementation repos should follow the architecture recorded here rather than
each inventing local meanings for the same terms.