What the page downloads
Entries, not a bundle — and a ceiling per entry, because one number over several jobs is a label rather than a gate.
gated by budget({ js, grow }), measured on the real walk over HTTP —
this framework has no bundler, so there is no bundle to measure instead.
The gate is the real walk over HTTP — 26,551 B brotli for the demo — and the build writes weft.budget.json so a change is a diff.
Each capability has its own entry and its own ceiling, so the first feature to arrive cannot spend the headroom every later one needs.
In plain terms
There is no bundler. The browser fetches the files on disk with their types stripped, so what you read is what runs. The budget is measured on that real fetch, not on an imaginary bundle.
Entries, not a bundle. A page that only adopts and binds imports the adoption path and nothing else; deltas, epochs, the channel, navigation, discovery and staging are each a further entry. What that buys is a cost model you can read off a page’s features rather than off a build report.
A ceiling per entry, and why
The design stated one server-side figure — "target under 8 KB" — and the kernel it describes does more than one job. A single number over several jobs is a number you can satisfy by moving its boundary, which makes it a label rather than a gate. So every entry below is a real module a deployment can import on its own, and each says where its ceiling came from.
| Entry | Covers | Ceiling | Where the figure comes from |
|---|---|---|---|
runtime | Client runtime, everything | 6 KB | stated in the design |
content-route | Content route: adopt and bind, no updates | 5 KB | stated in the design |
kernel | Server kernel: the document request path | 8 KB | stated in the design |
kernel-nested | Server kernel plus a document made of nested layouts | 9 KB | measured here, then fixed |
kernel-refresh | Server kernel plus surgical refresh and epochs | 12 KB | measured here, then fixed |
kernel-patch | Server kernel plus the surgical rung that needs no projectable values | 12 KB | measured here, then fixed |
kernel-intent | Server kernel plus intent dispatch | 10 KB | measured here, then fixed |
kernel-transport | Server kernel plus a live Warp channel | 14 KB | measured here, then fixed |
kernel-stage | Server kernel plus a route staged over the channel | 15 KB | measured here, then fixed |
kernel-journal | Server kernel plus somewhere an invalidation waits for a client that is not connected | 15 KB | measured here, then fixed |
kernel-authority | Server kernel plus a capability model and signed intents | 12 KB | measured here, then fixed |
kernel-discover | Server kernel plus lazy plan extension | 15 KB | measured here, then fixed |
kernel-render | Server kernel plus a catalogue of fragments a client can ask for by opaque id | 14 KB | measured here, then fixed |
kernel-region | Server kernel plus a page composed out of regions on other deployments | 12 KB | measured here, then fixed |
kernel-region-channel | Server kernel plus a region on another deployment, refreshed over a live channel | 17 KB | measured here, then fixed |
discover-route | Navigation plus what the client knows about routes it has not been to | 6 KB | measured here, then fixed |
channel-route | Channel route: an app route plus arriving frames | 5 KB | measured here, then fixed |
expose-route | Channel route plus a shell signal reaching a region on this page | 5 KB | measured here, then fixed |
patch-route | Channel route plus the ladder rung that needs no resident template | 5 KB | measured here, then fixed |
nav-route | Channel route plus instant navigation | 5 KB | measured here, then fixed |
front-door | The front door’s code, bundled and minified — not what a page downloads | 15 KB | measured here, then fixed |
app-route | App route: adopt, bind, patch, persist | 12 KB | stated in the design |
Read out of packages/bench/src/budget.ts when this page rendered, so the ceiling here is the one the gate compares against. pnpm bench budget measures them: rolldown, minified, brotli at quality 11 — what ships.
How a ceiling survives a feature
A new capability that would push an entry past its ceiling gets its own entry instead, with its own figure and the sentence saying why it needed one. That is why several rows above say "no design figure": the design did not name them, the repository measured them and drew the line where it actually was. A budget that moves silently is not a budget.
The application-level equivalent is weft.budget.json, committed, so a growth cap is a diff somebody reviews rather than a threshold somebody remembers.