The build record · read out of the archives

165 builds,
read by checksum.

Every version of this estate ships as a dated archive. 172 of them are still on the shelf — v251 through v424 — and this page was made by opening all of them and comparing the checksum of every file inside, pair by pair. It is a record of what actually changed, not a recollection of it.

What it shows: where the work went, build by build; the eleven releases that added a property that had not existed the day before; and the shape of a hundred versions of steady maintenance around them. Nothing here was typed from memory, and where the numbers are awkward — long runs where almost nothing moved — they are printed as they came out.

The shape

A hundred versions, in four figures.

The bars below are one per build: how many of the property’s OWN source files changed. The pale part of each bar is the estate’s shared chrome — one edit to a stylesheet every property carries a copy of, which lands as eighty changed files at once. They are drawn apart because otherwise six housekeeping sweeps would tower over every week of real work.

The eras

What the hundred versions were spent on.

Grouped by what was being built rather than by month. The build numbers and the properties named in each are taken from the archive diff; the sentence about what it was FOR is the one thing on this page written rather than derived.

  1. v251–258

    The register learns to describe itself

    Six properties arrive in eight builds — in-house, the roster that reads the site’s own register and walks you through every desk on it; jewelry, omnifile, watermark, legal and rates. The pattern for the rest of the run is set here: each one ships as a paper edition and a generated dark one, with its own stylesheet copy rather than a shared dependency.

  2. v259–283

    The instruments

    The longest stretch, and the quietest-looking: twenty-five builds where the file counts are small and the work is deep. composer and laband land together at v259 — sheet music that plays itself, and a turntable — and then are worked on in almost every build for two months: the DSP, the deck, the placard that turns a piece into a shareable serial, the ranges, the generator. RINSE first appears at v269. This is what maintenance looks like when it is going well: three files a build, for weeks.

  3. v284–290

    The rooms

    The largest structural change in the whole record. rxluxury, the clinical desk, arrives at v284; then at v286 eleven property directories appear in a single build — design, words, brands, world, utilities, internet, markets, news, sound, games, cities — with earth the build after and labs three later. The estate stops being a list and becomes thirteen rooms with doors between them.

  4. v291–310

    Live desks

    traffic at v291, commercial at v300, health at v303, and rxluxury deepened in nine separate builds — the register, the conditions, the narrow view, the ZIP lookup, saving. The traffic desk grows a basemap and then a world. Everything in this era reads something live and has to say what it could not reach.

  5. v311–325

    RINSE, rebuilt twice

    A single property taken apart and put back together: a volatility pass and a fundamentals pass at v311 with an SEC relay behind them; at v312 a FINRA relay, the sector board and a whole SECOND scoring pass built to argue against the first; then the chart, the datasheet, a 7,661-name universe and the roulette at v324. The scale was inverted and rescaled to ten somewhere in here, which meant every sentence on the page about the old one had to be found and rewritten.

  6. v318–322

    The assistant, and small movements

    ask.js at v318 — a semantic index of every page on the estate, built at ship time — and then the Lab Assistant on top of it, answering out of the site’s own text and quoting what it links. The three big sweeps in this stretch (v319, v321, v322) are the shared chrome going out to every property at once: micro-interactions, the assistant’s sheet, the search styling.

  7. v326–334

    Clockwork

    The bench of ten stopwatches and countdowns at v326; the moon at v327, and then rebuilt three times — drawn from primitives, then engraved as a stipple plate, then finally replaced with the Lunar Reconnaissance Orbiter’s own photograph, lit by arithmetic. Both the engraving and the photograph shipped in the end, one press apart. The last two builds carried the plate lab’s notification card out to two more properties.

  8. v335–346

    VIZZI, and a page that reads its own archives

    The visualiser arrives and is worked on in ten of these twelve builds. The moon gets a property of its own, and so does this page: the changelog stopped being a hand-written list and became a CRC diff of the shipped zips, which is why nothing on it is remembered. The sweep figure for this stretch is 112 — the largest in the record — because the shared chrome went out to every property twice inside a fortnight.

  9. v347–358

    VIZZI again, and TAP

    Six more builds on the visualiser: modes, the shelf behind a password, the import path for a file you drop on it. TAP lands as its own property. The deep figure here is 94 against a sweep of 27, which is the shape of a stretch spent inside properties rather than on the furniture around them.

  10. v359–370

    EZSCORE, and the small instruments

    A scoreboard property from nothing, and then the quiet ones around it — TAP, Windy, Traffic, Conditions, Padel. Twelve builds and a deep figure of 41: the smallest stretch in the record, and the one where the estate stopped growing for a moment and was tended instead.

  11. v371–383

    ATLAS, ORBIT, and the heaviest fortnight on record

    A deep figure of 177 across thirteen builds — more source changed than any other stretch here. Atlas and Orbit are new; Padel, Tides, Traffic, Quake, Pulse and Liquid are all reworked. Four archives from around here are gone for good (394, 395, 398, 399), which is why the record skips.

  12. v384–397

    THE PRESS, and the water

    A press property, and Liquid taken apart three times: the bottled sources audited against Wikidata coordinates, then the reservoirs, then the aquifers underneath them. A sweep of 103 in the same stretch — the chrome going out estate-wide while one property was being rebuilt underneath it.

  13. v400–411

    Eight new properties in twelve builds

    The densest run of new work in the record: Courier, Diff, Docket, Outposts, Resolver, Root, Routing and Undersea all arrive, and Padel is touched in eight of the twelve. Every one of the eight reads something real: a court docket, a DNS root, 701 submarine cables drawn from their own coordinates.

  14. v412–424

    The rooms fill up

    A history of the internet with its own drawn plates; a portal that drops any desk into any page; the courier gets a worked example; ezscore gains tennis, the European leagues and a live status bar. Songbuilder’s transport is rebuilt twice in here, and the visualiser gains a status panel and an EQ.

  15. v425–427

    Counting the same things twice

    Three plates added to the internet’s history for the moments the needle moved. Then the room count: the Labs room had shipped switched off, so the opening said thirteen doors and the dropdown said twelve, and the two registers behind them — the room pages’ own cards and the homepage’s fold — disagreed by seven. Every figure was computed correctly and they were counting different things. All thirteen rooms got a hand-drawn share plate, the room search learned both spellings of jewellery, and eight outposts were unfiled from rooms they were never desks in.

  16. v428–430

    A door, not a destination

    Songbuilder’s studio took another pass — the transport, the style engine and the sheet. Pulse was rebuilt on its own stylesheet rather than borrowed chrome. The change that reached every page was smaller and further down: Practices in the bar had been a plain anchor that scrolled you to a band explaining what the four practices are, which is an argument rather than a way in. It became a drawer instead, opening onto every desk on the estate grouped by the room it lives in — the same list the portal property keeps, so the bar can now reach any of them in one move.

  17. v431–434

    The streamers desk

    A new property: streamers, shipped whole in one build with its own chrome, fonts and both editions. Three builds later it got the two files that make it live rather than illustrative — a wire that fetches, and a register of the accounts it reads. The rest of those builds were the internet history’s pages and the portfolio register catching up with it.

  18. v435

    aetheria becomes rxluxury

    One property renamed, twenty-four files moved from /aetheria/ to /rxluxury/. The old path was not dropped: it answers a 301 to the new one, so anything already linking to it still arrives. The clinical desk had outgrown a name chosen before it knew what it was.

  19. v436

    Seventeen feeds, and a way to ask the card desk

    Search had been telling readers it federated thirteen feeds. It federates seventeen, and worse, the All switch listed only nine of them — so a visitor who asked for everything got barely half the wire. Both were corrected, the results gained structured data, and every control on the page was flattened to a four-pixel corner: no pill shapes, one height, ink fill for the chosen one. The card desk carried thirteen offers and no way to ask it a question, only four category buttons; it gained a search across every word each card puts on screen — the issuer, the fee line, the discipline it is filed under.

  20. v437

    What the pages could not support

    Yum was rebuilt: two hundred and eighteen loose city tiles became a strip of the twenty-one cities that actually carry the collection, with the rest folded into forty-seven countries; the toast stopped printing the word undefined after every message; and the page gained photographs, honestly captioned, because the collection holds none of its own. Then the corrections: the menus quoted Yum at 671 rooms against a register of 1,085, and graded Rinse “0 to 100 over three windows” when it publishes out of ten over four. The Lab assistant turned out to be answering on no host but this one — its index, a file nothing in the markup references, had never shipped to any of the thirty-one standalone domains, so every one of them failed on the first question asked. It ships everywhere now.

  21. v438

    The clinical desk, rebuilt

    Rx.Luxury rebuilt in one build: the symptom checker became a live ladder with a digital readout of the conditions still in play, the register grew from 148 to 219, a natural compounds shelf arrived with evidence graded and cautions printed, a redrawn body now sits on the checker, the shelf, both finders, intake and vitals, and the desk gained a multi-page PDF engine, a real calendar and a mailer.

  22. v439

    Four new rooms’ worth of desks

    Finance, Paper, Deadline and Holidays join the estate as full properties in the Markets, Words, Utilities and Earth rooms, each with its own hand-drawn share plate, both editions, a rooms drawer, a sitemap entry and a place in the assistant’s brain. Search gains its own relay and a retry pill on every silent feed; Rx.Luxury gets its plate. Thirty-five placards regenerated on the estate’s engine.

  23. v440

    The one relative canonical

    Two hundred and seventy-three pages carry a canonical and two hundred and seventy-one of them are absolute. Nexus, in both editions, declared href="./" — which resolves to the right address and is still the one page on the estate whose canonical has to be worked out rather than read. Its own og:url had said https://sites.llc/nexus/ all along, so the fix was to make the two agree. The version stamp went the same way: seven pages had been left on the previous build’s cache token while two hundred and forty-one moved, so a returning reader could hold an old copy of the file that names the build. All two hundred and forty-eight now carry one token.

  24. v441

    Six files the archive never held

    Every property page now carries its room in the drawer. The register files all one hundred and sixty-three properties onto thirteen shelves, so a hamburger can list the ten to twenty neighbours a reader might actually want instead of the whole estate: chess offers the nine other tables, finance the twelve other desks in Markets. Then the generators were asked what they thought, and three of them disagreed with the tree. Eleven static stamps still read v439 while version.js had moved on — the number a reader sees in the bar was a literal somebody typed, which is the failure the version generator exists to catch. Four copies of assistant.css had drifted, all four of them in properties added in the last build. The sitemap page still advertised a hundred and eighty-eight versions ending at v437. And six media files — three tracks under the turntable, a composer take, its video, and the illusion the mind sphere is built from — turned out to live on the server and in no archive, twenty-one megabytes that every copy of this site was missing and answering 404 for.

  25. v442

    Four rooms, one behind

    The build before last added four properties — one to Markets, one to Earth, one to Utilities, one to Words — and every one of those four rooms went on saying how many desks it held before the new one arrived. Markets offered ten doors under a headline reading nine. Earth pointed nineteen instruments at the planet and said eighteen. Utilities kept nine tools and claimed eight; Words held six reading rooms and said five. The cards themselves were right the whole time, because a generator writes them from the register; the numbers were words somebody typed, and they are the last part of a room nobody regenerates. Five hundred and twenty-six of them across ninety-one files, since every hamburger on the estate repeats its neighbours’ descriptions. The count now comes out of the same register the doors do.

Every build

All 165, in order.

One row per release. Work is the property’s own source files that changed; sweep is shared chrome copied estate-wide. A row with nothing in either column is a build that moved only markup or a version stamp — and those are printed too, because leaving them out would make the run look busier than it was.

Method

How this was derived, and what it cannot see.

Where the numbers come from

172 shipped archives, labs251.zip to labs424.zip, listed with their internal CRC-32 checksums and compared consecutively. A file counts as changed when its checksum differs from the same path in the build before. Nothing was extracted and nothing was read into a model: a checksum either matches or it does not.

Why HTML is not counted

Every build stamps a content hash into the ?v= of each stylesheet and script reference, so one line changed in one file rewrites two hundred pages. Counting those would make all eighty builds look identical and enormous. The same goes for version.js, the sitemaps, the generated site index and the generated assistant index — and for one property whose front page rotates by design on every single build.

What it cannot tell you

A checksum knows that a file changed, not whether the change was a rewrite or a comma. Three builds in this record touch one file each and are among the most consequential in it; one touches ninety and is a stylesheet being copied around. The bars measure reach, not effort, and the era notes above are there because the bars alone would mislead.

The gaps

Before v251

Two hundred and fifty builds precede this record and their archives are not on the shelf, so they are not described here. The estate did not begin at v251; this page simply refuses to describe what it cannot check.