weft
ir 2.6.0 · warp 1.8.0

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.

21 modules, served as written, types stripped 30,075 B brotli

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 bundled figure is the code, not the download, and the difference is 1.8×. The gated number is the walk over HTTP, which agrees with the build's own walk within 0.34%.
✓ Valid An entry inside its ceiling

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.

✕ Refused an entry over its ceiling
what you wrote→budget({ js, grow }) is enforced by weft build→build failure

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.

EntryCoversCeilingWhere the figure comes from
runtimeClient runtime, everything6 KBstated in the design
content-routeContent route: adopt and bind, no updates5 KBstated in the design
kernelServer kernel: the document request path8 KBstated in the design
kernel-nestedServer kernel plus a document made of nested layouts9 KBmeasured here, then fixed
kernel-refreshServer kernel plus surgical refresh and epochs12 KBmeasured here, then fixed
kernel-patchServer kernel plus the surgical rung that needs no projectable values12 KBmeasured here, then fixed
kernel-intentServer kernel plus intent dispatch10 KBmeasured here, then fixed
kernel-transportServer kernel plus a live Warp channel14 KBmeasured here, then fixed
kernel-stageServer kernel plus a route staged over the channel15 KBmeasured here, then fixed
kernel-journalServer kernel plus somewhere an invalidation waits for a client that is not connected15 KBmeasured here, then fixed
kernel-authorityServer kernel plus a capability model and signed intents12 KBmeasured here, then fixed
kernel-discoverServer kernel plus lazy plan extension15 KBmeasured here, then fixed
kernel-renderServer kernel plus a catalogue of fragments a client can ask for by opaque id14 KBmeasured here, then fixed
kernel-regionServer kernel plus a page composed out of regions on other deployments12 KBmeasured here, then fixed
kernel-region-channelServer kernel plus a region on another deployment, refreshed over a live channel17 KBmeasured here, then fixed
discover-routeNavigation plus what the client knows about routes it has not been to6 KBmeasured here, then fixed
channel-routeChannel route: an app route plus arriving frames5 KBmeasured here, then fixed
expose-routeChannel route plus a shell signal reaching a region on this page5 KBmeasured here, then fixed
patch-routeChannel route plus the ladder rung that needs no resident template5 KBmeasured here, then fixed
nav-routeChannel route plus instant navigation5 KBmeasured here, then fixed
front-doorThe front door’s code, bundled and minified — not what a page downloads15 KBmeasured here, then fixed
app-routeApp route: adopt, bind, patch, persist12 KBstated 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.