One manifest,
a whole delivery CLI
The same five verbs on every product, whatever it is written in. Build / test / release / deploy / monitor, declared in one YAML file and assembled into a command line - so somebody who has worked on the Java product can operate the C++ one without being told anything. Not a CI server: yours calls this.
The manifest is the CLI
A command is a declaration, not a hand-written argument parser. Add three lines to the manifest and the command exists, with its help, its options and its place in the tree.
Tasks that travel
The kernel carries the mechanism - render docs, run a suite, push a stack - and the product supplies the data. A capability written once is available to every product that imports its namespace.
A reference that cannot go stale
The command reference on this site is read off the assembled application during the build. It lists what can be typed, not what was intended.
Rules you can check
Six design rules, each with the mechanism that forces it and a way to find out in ten minutes whether your own code has the same shape.
Environment-first where it matters
Deploying and monitoring take a target environment as the outer token; building and testing refuse one. The distinction is declared once and enforced by the assembly.
Nothing to vendor
The kernel is an ordinary PyPI dependency. A fresh clone plus the generated launcher is the whole setup: it provisions its own virtual environment and installs the pinned kernel.