Governance · Canonical

Constitutional Engineering

Constitutional Engineering is Chainplug's practice of deciding what a system is allowed to become before deciding how it is built. Governance is authored first; implementation follows it.

Why software architecture is insufficient

Software architecture answers how a system is structured: modules, boundaries, data flows, deployment. It is necessary, and it is silent on the questions that decide whether a system can be trusted over time — what the system may claim, what it must disclose, where its authority ends, and which behaviours may never diverge between products.

Architecture is also mutable by default. Any competent engineer can refactor a boundary. Nothing in an architecture diagram prevents a product from quietly acquiring a capability it was never meant to have, or from asserting a conclusion its evidence does not support. In high-trust domains, that silence is the risk.

Why constitutional architecture exists

Constitutional architecture is the layer above software architecture. It states, in writing and ahead of construction, the non-negotiable rules a system inherits: how evidence must be exposed, how uncertainty must be declared, where professional judgement remains sovereign, and which surfaces are permitted to say what.

A constitution is deliberately harder to change than the code beneath it. That asymmetry is the point. Implementation should move quickly; the rules that make implementation trustworthy should not.

Why governance precedes implementation

When governance is authored after a product ships, it can only describe what already happened. Authored before, it constrains what can happen — and every subsequent decision becomes reviewable against a written standard rather than against individual judgement in the moment.

In the Chainplug ecosystem this ordering is enforced rather than recommended. A product surface is not built until its constitutional role is stated: what it owns, what it inherits from the Constitutional Core, what it must defer to another property, and how its evolution will be recorded under KRONOS.

Scope

Constitutional Engineering is authored and maintained by Chainplug S.r.l. It is defined here, once. Every other property in the ecosystem references this page rather than restating it — a duplicated constitution is, by construction, no longer a constitution.