coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Framework architecture for railiance applications, railiance rails, railiance tooling. This repo explains and evolves the concepts in and around railiance.
52 commits 1 branch 0 tags 861 KiB
Find a file
codex 28cbba1025 Add rapp declaration schema with composition block (WP-0021 T02, T03) 
schemas/rapp.schema.json defines one normative shape for the rollout, smoke and
rollback contracts in place of the three mutually unreadable variants found
across the live rapps, promotes contract_version, readiness_state,
data_classification and criticality to required, and forbids the rapp- prefix
on workload_identity.name.

composition replaces the flat members list per amendment f88f938d: purpose,
member_repos with deployables, and pinned upstream_components. Repos are
many:many with rapps; deployables are 1:1, which is what makes the T06 coverage
check well-formed.

ownership_repo left permissive pending an architecture-owner call; the tighter
alternative is written up in schemas/README.md.

Validated against all three live declarations: openbao 10 errors, postgres 10,
qonto 4 — precisely the reported drift and nothing else.

Also found: three further rapp-* repos (secrets-engine, tenant-engine,
user-engine) carry no declarations at all, which the routed survey missed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 22:56:22 +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
schemas Add rapp declaration schema with composition block (WP-0021 T02, T03) 2026-08-11 22:56:22 +02:00
tools Advance OpenBao migration to consumer waves 2026-08-03 21:30:17 +02:00
workplans Add rapp declaration schema with composition block (WP-0021 T02, T03) 2026-08-11 22:56:22 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-11 20:40:56 +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 Sync RAILIANCE-WP-0021 hub ids and tidy T01 completion note 2026-08-11 20:41:17 +02:00

README.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

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.