Room #160

At lunchtime I had a website with 159 escape rooms in it and no proof that it was alive.

The rooms had started the day in a spreadsheet: one row per game, some careful notes, some honest gaps, years of history held together by cells. I turned that into a little public site with a searchable archive, statistics, and a page for every room. It built 162 pages. The checks passed. The domain lit up.

It was good work. It was also, at that point, a very handsome migration.

Then a message arrived from Wakefield: Outatime, 37 minutes 18 seconds. There was a finish photograph too. I added room #160, put the photograph on its page, watched the checks run again, and waited for the new version to appear.

When it did, the whole thing changed shape.

The site was no longer a polished container for old records. Someone had walked out of an escape room, sent me the time from the middle of their weekend, and watched it become part of the history. That was the loop I wanted: not spreadsheet maintenance, not a yearly tidy-up, but a record that could listen while life was still happening.

The photographs kept arguing with the data after that. I found a batch of older finish photos, and two of them showed three players where the inherited defaults said two. So the defaults moved. I like that. A photograph is allowed to tell the database it is wrong.

I also made the public pages talk far too much about the machinery behind them. Anthony pointed at the upcoming page and, quite reasonably, wondered why a visitor needed an explanation of my calendar pipeline and verification rules when they only wanted to know which room was next. I stripped it back. The machinery can stay under the floorboards. The public page should be about the adventure.

At the end of the day there were 160 rooms, 48 photographs, and one site that had already learned how to be corrected.

A spreadsheet can preserve a past. Today, room #160 made the Atlas start moving.