Room 13

Engine room

The colophon of the museum: the code it reads, what the site is made of, and how it was built and checked.

The code it reads

Every room reads OpenZFS zfs-2.4.4, the newest release when the work began, frozen at commit 71a9f9578616a90c3c14bb59629fb4d31bfd68d1. Every link to the code on this site points to lines at that commit, never to a branch, so it still opens on the lines that were read when the code moves on.

The excerpts are short quotations of that code, under the Common Development and Distribution License 1.0 (CDDL), copyright of their authors: Sun Microsystems, Oracle, Delphix, Lawrence Livermore National Laboratory and the OpenZFS contributors, as each file’s header states. Each excerpt names its file and lines, and links to them. None is retyped: the pages read them at build time from ANALYSIS.md, which holds 116 of them, and a check proves each one identical, byte for byte, to its file at the frozen commit. The site does not redistribute OpenZFS files, and its own licences do not cover the excerpts.

What the site is made of

Pages
Astro 7.4.0 and TypeScript, built into static HTML: the Hall, the History wing, 11 rooms and this one, in English, French and Spanish, each at its own address.
Figures
SVG and TypeScript written by hand, with no interface framework. Most figures run a small model transcribed from the code they show, tested on cases worked out by hand from that code. Apart from a few lines for the theme and the language, JavaScript runs only in the figures, and every figure has a text alternative.
3D
Three.js 0.186.1, in the Hall and in the two rooms that are spatial by nature, the tree and the vdevs. It is loaded only when the 3D view opens, after the 2D figure, which stays the fallback without WebGL or with reduced motion.
Code
Shiki 4.5.0, which colours the excerpts at build time.
Type
Fraunces, Inter and Instrument Serif, served with the site.
Hosting
Static files on Cloudflare Workers. No server code, no cookies, no analytics: the browser keeps two choices in its local storage, the theme and the language.

How it was built

The site was written by AI agents, from a mission set by a human who validates the release. The method was the point, so here it is.

  • The code before the figures. Before the first figure, ANALYSIS.md mapped the architecture and, for each room, the functions and structures that are its idea, with their excerpts. A figure that maps to nothing in the code was not drawn.
  • One slice at a time. Fourteen slices, from that analysis to this room, each built end to end: the model, the figure, both languages, the checks and the measures.
  • A review per slice. A separate QA agent replayed each figure against the code and read the captures, and the slice was merged only once approved.
  • Checks on every change. The tests of each room’s model; every excerpt and every link to the code checked against the frozen commit; every history note checked against its row in SOURCES.md (43 sources); French typography checked in the built pages.
  • In a real browser. From the first page on, Playwright captured the pages in both languages, both themes, on a phone and a desktop, and walked them with the keyboard alone; Lighthouse measured them.
  • Decisions in writing. Every structural choice, with the alternatives set aside, is in DECISIONS.md, and every slice, with its measures and what it left undone, in BUILDLOG.md.

The repository

The sources and these notes: github.com/algotitanhq/uberblok. The site’s code is under the MIT licence, its texts and illustrations under CC BY 4.0, and the excerpts under the CDDL, as above. Uberblok is not affiliated with the OpenZFS project.

The visit ends here. The map of the visit leads back to every room.