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.

• Intent and direction
• Current scope and authority boundaries
• Reviewed architecture-demand intake

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/exposure-posture-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
• docs/adr/ADR-0007-rapp-declaration-contract.md
• docs/adr/ADR-0008-private-by-default-exposure.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-*, 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.