The Chute not built
A chute is the enclosed run between the gate and the truck: the material is moving, and it is not moving in the open. Here it is the private execution path — and it is a description, not a thing. There is no solver, no intent format and no settlement contract.
What it would be
An order expressed as an intent — what you want, not the call that achieves it — filled by a solver competing on price, rather than a raw swap sitting in a public mempool for the length of a block with its size and direction legible to anyone.
Intent, not a call
You sign what you want. The route is chosen after, by whoever can fill it best.
Aggregated liquidity
The fill can cross venues, because nothing in the intent names one.
Gas in the asset
Fees payable in what is being traded, so a wallet with no native balance can still act.
Why it has no numbers on it
Every other page here carries figures, a confidence class and the code that produced them. This one carries none, and that is the honest state rather than an omission.
Privacy in this shape is not a property of a mechanism, it is a property of flow: what protects an order is how many other orders it could have been, and that is a count you have to go and measure on a real chain over a real window. There is nothing to count here, because nothing routes anything.
Naming a mechanism is not evidence about an outcome. "Intent-based routing, so your trade is not front-run" describes a pipe and implies a result. The result depends on how many intents are in flight when yours is, which nobody in this category publishes and this site cannot, because it has no traffic to publish.
Until then this page is a specification with a marker on it,
listed in Ullage at state none, and the build fails
if that marker is ever removed while the state is still none.