Framework architecture for railiance applications, railiance rails, railiance tooling. This repo explains and evolves the concepts in and around railiance.
Find a file
codex f3c44c7a80 Open RAILIANCE-WP-0021 for the rapp declaration schema
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>
2026-08-11 20:40:40 +02:00
activity-definitions Schedule OpenBao retention closeout 2026-08-04 00:53:34 +02:00
docs Schedule OpenBao retention closeout 2026-08-04 00:53:34 +02:00
history Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
tools Advance OpenBao migration to consumer waves 2026-08-03 21:30:17 +02:00
workplans Open RAILIANCE-WP-0021 for the rapp declaration schema 2026-08-11 20:40:40 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-04 00:35:41 +02:00
.repo-classification.yaml Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
AGENTS.md Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
CLAUDE.md Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
INTENT.md Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:54:12 +02:00
README.md Define derived rail and Qonto readiness architecture 2026-07-26 11:45:07 +02:00
SCOPE.md Finish first repo-family materialization wave 2026-07-26 08:51:13 +02:00
WORK-RECORDS.md Schedule OpenBao retention closeout 2026-08-04 00:53:34 +02:00

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

Current Explorations

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.