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.
111 commits 1 branch 0 tags 916 KiB
Find a file
codex 2a7f17e8f8 Hold layer: Taxonomy as an enumerated §3.1 value through the gate-house ruling. 
The custodian's estate sweep of flex-auth's FLEX-WP-0030 boundaries review
records this repository as declaring a value outside the §3 vocabulary, on
the reading that §3 admits only {Staff, Engine, Tooling}. §3 enumerates four
layers, and Taxonomy is the first row of its table with §3.1 to itself, in
every version of the standard from v0.1 through v0.8. §4 assigns the value to
info-tech-canon and net-kingdom, §7 carries it as a fourth plane line, §17 is
titled for it, and gate-house's own INTENT.md uses it.

ADR-0010 records the position with those citations. The declaration is not
changed: it is the evidence of what this repository holds itself to be, and
changing it now would pre-empt the ruling. RMASTER-WP-0027 holds the wait and
says what to do either way.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
2026-09-21 02:10:52 +02:00
activity-definitions chore: use RMASTER-WP prefix for master workplans 2026-08-14 14:29:18 +02:00
demand docs: complete canon alignment housekeeping 2026-08-18 18:12:32 +02:00
docs Hold layer: Taxonomy as an enumerated §3.1 value through the gate-house ruling. 2026-09-21 02:10:52 +02:00
history docs: align intent and scope with NetKingdom security-layer v0.7 2026-08-29 11:47:56 +02:00
reviews docs(review): attest WP0027 drill quorum availability 2026-08-23 00:24:13 +02:00
schemas docs(RMASTER-WP-0025): define universal rapp coverage 2026-08-23 01:38:29 +02:00
tools feat: implement RMASTER-WP-0023 private-by-default exposure 2026-08-15 20:08:37 +02:00
workplans Hold layer: Taxonomy as an enumerated §3.1 value through the gate-house ruling. 2026-09-21 02:10:52 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-29 11:49:15 +02:00
.gitignore chore: ignore generated AST cache 2026-08-19 20:22:49 +02:00
.repo-classification.yaml Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
AGENTS.md docs(agents): repoint remote State Hub URL to the in-cluster address 2026-08-25 00:21:49 +02:00
CLAUDE.md Establish Railiance architecture home 2026-07-25 10:54:37 +02:00
INTENT.md feat(RMASTER-WP-0026): declare Taxonomy layer and consume NetKingdom §20 2026-08-29 12:52:35 +02:00
layer.yaml feat(RMASTER-WP-0026): declare Taxonomy layer and consume NetKingdom §20 2026-08-29 12:52:35 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:54:12 +02:00
README.md feat(RMASTER-WP-0026): declare Taxonomy layer and consume NetKingdom §20 2026-08-29 12:52:35 +02:00
SCOPE.md Hold layer: Taxonomy as an enumerated §3.1 value through the gate-house ruling. 2026-09-21 02:10:52 +02:00
WORK-RECORDS.md chore(registrar): assign State Hub identifiers 2026-08-29 11:49: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.