Framework architecture for railiance applications, railiance rails, railiance tooling. This repo explains and evolves the concepts in and around railiance.
Find a file
codex 3cc0dc31d6 Finish RAILIANCE-WP-0021: family schemas, validator, and ADR-0007
Add rail and reef schemas, derive reef bound_rapps from rapp.bound_reefs,
and ship a standalone family-declaration validator with an inventory-fed
coverage check. Point the bootstrap contract at the schemas, record the
dimension and cardinality decisions in ADR-0007, correct the first-wave
candidates document, and release the shape to downstream repos.
2026-08-13 15:29:07 +02:00
activity-definitions Schedule OpenBao retention closeout 2026-08-04 00:53:34 +02:00
docs Finish RAILIANCE-WP-0021: family schemas, validator, and ADR-0007 2026-08-13 15:29:07 +02:00
history Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
schemas Finish RAILIANCE-WP-0021: family schemas, validator, and ADR-0007 2026-08-13 15:29:07 +02:00
tools Finish RAILIANCE-WP-0021: family schemas, validator, and ADR-0007 2026-08-13 15:29:07 +02:00
workplans Finish RAILIANCE-WP-0021: family schemas, validator, and ADR-0007 2026-08-13 15:29:07 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-13 15:03:32 +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 Finish RAILIANCE-WP-0021: family schemas, validator, and ADR-0007 2026-08-13 15:29:07 +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.