Today we tagged Machinery 2.0. It is the largest cut we have ever made: our delivery authority moved to our own forge, our factory runs on our own isolated runner, and every quality gate tells the truth. GitHub is now an archive. The way we build lives with us.
Machinery is not an application. It is the way-of-doing-things for everything Reflective Labs builds — the repeatable, non-application-specific truth that our platform and our applications rely on so they can concentrate on their own reason to exist.
One Idea, Applied Everywhere: Authority
Two years of building taught us one thing worth keeping above all others: every concern needs exactly one authority, and everyone else consumes evidence.
Machinery is five authorities with hard boundaries:
Build-Depot owns the software factory — the quality gates, the adoption contract, the release engineering. Everyone else gets verdicts and workflows, never copies.
Runtime-Runway owns the deployed runtime — hosting, accounts, auth, storage, telemetry. Applications compose it; they do not reinvent it.
Commerce-Rails owns commercial truth — contracts, entitlements, billing. Applications may name exactly one crate: the client. The payment provider stays swappable; the entitlement truth stays ours.
Drawing-Office owns strategy and governance — the canon, the boundary registry, drift checks, and the promotion gates that take work from pull request to production. Engineering gates keep code honest. These keep the direction honest.
Control-Room owns nothing — deliberately. It is a read-only projection of all the others: a factory-readiness surface where every claim links to its evidence, and unknown state renders as unknown. Absence of evidence is never green.
The same pattern extends beyond Machinery. Bedrock — our platform — has its own reason to exist and consumes Machinery's behaviors without inheriting its internals. The applications above do the same. No module reaches into another's domain; where systems touch, they touch through declared ports with exact versions.
Why It Matters
Quality that cannot lie. Every push runs the full gate tree on an isolated runner with exact-pinned toolchains — the same command you run locally, 686 tests strong. Disabled tests live in a ledger that expires; a test silenced without a record is a red build.
Repeatability as doctrine. Hermetic builds that hide drifting system libraries. A twelve-crate release train published to our own registry in dependency order, each publication checkpointed with archive proof.
A factory that learns. Signals close into mechanisms: a repeated review comment becomes an automated check, an incident pattern becomes a standard. The loop is designed to scale — at ten users it is operated by hand, at a thousand it is mostly mechanism, at a million it is a self-playing piano. Beneath it all, one floor: services never crash, and never serve an experience below the level we declared acceptable.
Humans and machines on separate wires. Machine telemetry flows through the runtime. Jobs flow through the factory. A message to a human carries a bounded claim and a link to evidence — never the truth itself. A chat message may front an audited endpoint, but chat is never the mechanism. Push grabs attention; verification happens at the evidence surface.
An Invitation
Machinery is how Reflective Labs builds — and it is built to be adopted. If you want to collaborate on a stack where the gates are truthful, the boundaries are real, and the factory improves itself while you sleep: we are open.
Bring your own reason to exist. Machinery handles the repeatable rest.
Reach out, and come build.