In most modern stacks, the compiler, the type system, and the runtime are owned by different projects, with different assumptions and different release cycles. That is fine in isolation. It gets expensive when you are trying to ship a product across the full stack.
Seams are where the bugs live
Every time a value crosses a boundary — from the frontend to an API, from an API to a database, from a type definition to a validation layer — there is an opportunity for drift. A field gets renamed in one place and forgotten in another. A null sneaks through. A deploy succeeds because each piece passed its own tests in isolation.
App Marché treats the compiler, type system, and runtime as one system with one mental model. The types you write for your data are the same types the runtime validates. The steps the compiler emits are the same steps the interpreter executes. There is no second source of truth to keep in sync.
What you get back
When the seams are gone, the feedback loop is shorter. A typo in a field name becomes a compile-time error instead of a production incident. A missing permission becomes an orchestrator warning instead of a 500 at 3 AM. The platform catches things early because it is actually paying attention across layers.
A coherent model is not a luxury. It is how you keep complexity from eating the team that is trying to ship.
We will keep publishing deeper notes on the precompiler and type system over the next few posts. The short version: the runtime was written once, in Rust, so the rest of the platform can lean on it.
