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.
57 commits 1 branch 0 tags 861 KiB
Find a file
codex 4864b7852d chore: use RMASTER-WP prefix for master workplans 
Rename RAILIANCE-WP-0017..0021 to RMASTER-WP-* so railiance-master
IDs no longer collide with railiance-platform's RAILIANCE-WP series.
Hub UUIDs are unchanged.
2026-08-14 14:29:18 +02:00
activity-definitions chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +02:00
docs chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +02:00
history Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
schemas chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +02:00
tools chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +02:00
workplans chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +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 chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +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 chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +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.