Framework architecture for railiance applications, railiance rails, railiance tooling. This repo explains and evolves the concepts in and around railiance.
railiance-platform surveyed the four-axis model against the live cluster and all six family repos and routed the findings here (messages 04c776c4 and f88f938d): rapp.yaml has no schema and has drifted three ways, reef bound_rapps is a stale hand-maintained list, and ~17 live workloads sit against 3 rapps. Takes ownership of the schema, the composition block with its two cardinalities (repos many:many with rapps, deployables 1:1), and a validator over all three family declaration files. Migration stays with the owning repos. T01 done: both messages acknowledged, ownership confirmed to railiance-platform. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| activity-definitions | ||
| docs | ||
| history | ||
| tools | ||
| workplans | ||
| .custodian-brief.md | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
railiance-master
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/reef-substrate-model.md
- docs/rail-kubernetes-boundary.md
- docs/rapp-first-wave-candidates.md
- docs/reef-first-wave-rollout.md
- docs/fabric-state-hub-adaptation.md
- docs/repo-family-bootstrap-contract.md
- docs/rail-composition-contract.md
- docs/reef-production-readiness-contract.md
- docs/qonto-knative-runtime-contract.md
- docs/adr/ADR-0001-repository-prefix-architecture.md
- docs/adr/ADR-0002-rail-kubernetes-wave-1-boundary.md
- docs/adr/ADR-0003-rapp-first-wave-selection.md
- docs/adr/ADR-0004-first-wave-reef-rollout.md
- docs/adr/ADR-0005-derived-rail-composition.md
- docs/adr/ADR-0006-reef-production-admission.md
Current Explorations
- history/260724-InitialExplorationOfOperationModels.md
- history/260724-InitialExplorationOfWrapperConcepts.md
Purpose
railiance-master is the canonical place to define:
- repo-family vocabulary such as
railiance-*,rail-*,rapp-*, andreef-* - 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.