Generate a web rendering engine from specs and tests.
\nBuilding a web engine by hand costs hundreds of engineers and many years, so only a few companies can have one, and only they decide how the web works. Bez generates the engine instead: from the specifications, with the three shipping browsers (checked against each other) and WPT as the tests. Once the pipeline exists, each extra engine costs very little.
\nSpec text → model writes many candidates → candidate runs inside the engine → Chromium/Firefox/WebKit cached dumps check whether boxes and places match → on yes, commit as ordinary Rust; on no, regenerate.
\nDOM, style, box tree and fragment tree are hand-written and pass browser checks. Nine CSS 2.1 layout rules live in generated layout code; eight were written by models and admitted against the three-browser vote. Together they pass all 227 recipe cases and all 11 usable WPT normal-flow pages. Overall generated coverage against browser-compat-data remains small (~0.6% generated as of 2026-09-25).
\nOriginal: tangled.org/burrito.space/bez
","headings":[{"level":1,"text":"Bez - a generated web engine","id":"bez-a-generated-web-engine"},{"level":2,"text":"Why","id":"why"},{"level":2,"text":"Goals","id":"goals"},{"level":2,"text":"How it works","id":"how-it-works"},{"level":2,"text":"Status","id":"status"},{"level":2,"text":"Findings so far","id":"findings-so-far"}]}}