RBC_Template is a workspace of independently versioned C/C++ and Python products for building safety-related railway software around an ERTMS/ETCS Radio Block Centre (RBC), targeting CENELEC EN 50128 / SIL 4. It follows the Reference CCS Architecture (RCA): application logic is written against a platform-independent API, and the Safe Computing Platform owns redundancy, voting, communication and safe-state handling. Each product is its own git repository; this root ties them together as a reproducible whole.

Start here

Getting the code

• One product on its own: git clone git@github.com:bula173/<repository>.git. It works as if this root did not exist.
• The whole workspace, pinned to reproducible commits: git clone --recurse-submodules git@github.com:bula173/RBC_Template.git, or git submodule update --init --recursive in an existing clone.
• Always the latest branch tips (for active cross-repository development): ./bootstrapWorkspace.sh.

Then install the tools (REQUIREMENTS.dox) with ./installDependencies.sh.

Products

The tree follows the Reference CCS Architecture (RCA) layers. Folder name, product name and GitHub repository name are all the same now (each product's repo was renamed to match, 2026-09-22); older text may still use a product's old repository name — see the table in CLAUDE.md.

A submodule folder itself only shows as a link to its own separate repo on GitHub's web UI. To read a product's documentation directly in this repo instead, see docs/products/ — a mirrored snapshot of every product's README, CLAUDE.md and docs, regenerated by syncProductDocs.sh. For the always-current, generated-HTML version, see the published docs site: https://sapi.docs.mksystemdesign.org.

Folder links go to that product's own GitHub repo; Product links go to its mirrored documentation in this repo. Both are full URLs on purpose — the generated docs site can't build docs/products/ itself (100+ mirrored files across every product is too much for one build) or a submodule's source, so a plain relative link to either would be a dead link there even though it works fine on GitHub itself.

All except architecture/ and docs/ are git submodules (.gitmodules). Inside a project, build files locate their dependencies by this layout (for example application/RBC_GP finds platform/Platform_RTE); a flat sibling checkout of the old repository names still works as a fallback in most projects. Docker builds use the workspace root as build context and keep the same layout inside the image.

Documentation site

Every product is documented with Doxygen; this root publishes all of it as one GitHub Pages site at https://bula173.github.io/RBC_Template/, with each product under its own path.

Start from the pages listed under Related Pages on the site, or read the sources directly:

• Architecture: overview, product structure, logical architecture and hardware allocation
• Subproducts (every product with its own documentation site): docs/subproducts/subproducts.dox