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.
32 commits 1 branch 0 tags 861 KiB
Find a file
codex 708cd30f32 Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 
Maintainer decision, 2026-07-29: adopts TRSL V1C1 as this repo's
preliminary governing license, per target-revenue's
workplans/TREV-WP-0008-governance-and-pilot-rollout.md T05. Full
specialist legal review is deferred until out of beta (target-revenue
SCOPE.md §1). No Phase is yet declared for this repo.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-30 00:54:12 +02:00
docs Define derived rail and Qonto readiness architecture 2026-07-26 11:45:07 +02:00
history Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
workplans Finish Knative Qonto framework workplan 2026-07-29 23:13:51 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-29 23:08:44 +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 Knative Qonto framework workplan 2026-07-29 23:13:51 +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.