> For the complete documentation index, see [llms.txt](https://docs.moduluszk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moduluszk.io/the-problem/why-the-architecture-forces-it.md).

# Why the architecture forces it

Take any contract platform in production. A developer writes intent in a design document, then translates it into a high-level language, which a compiler translates into bytecode, which a virtual machine executes against state. Each translation is a place for meaning to drift, and the final artifact, the one the chain actually enforces, is the one furthest from anything a human meant. Reviews compare artifacts; they cannot make them the same object. Test suites sample behaviour; they cannot exhaust it. Formal verification proves the code against a model of the intent, and the model is a third artifact with a gap of its own on either side. 

The conclusion is uncomfortable for the tooling industry and unavoidable for everyone else: a system with two artifacts has a gap, and a gap has a price, paid either upfront to reviewers or later to an attacker.

<br>