Software Factory Archive

One hundred stories.

The archive had started as a single file—The First Scenario—posted on a July evening by someone calling themselves factory_observer, who may or may not have been one of the three people working in the factory, and who may or may not have been writing from inside it. The file was HTML, hand-structured, linked to a CSS stylesheet that looked like it had been designed by someone who admired AO3's layout and wanted to honor it without copying it.

Then there were two stories. Then ten. Then the archive had its own index page, and the stories had tags, and the tags had patterns. Digital Twin Universe. Attractor. CXDB. Leash. Agate. Cedar. Three characters who appeared again and again: a CTO who gardened, an engineer who collected words, a younger engineer who kept physical notebooks.

The stories weren't documentation. Documentation told you what a system did. The stories told you what it felt like to build one. The difference was the difference between a blueprint and a photograph. Both described the same building. Only one showed you the light coming through the windows.

At story fifty, someone had written about the moment the factory's satisfaction metric first exceeded ninety percent. At story seventy-five, someone had written about the day the Attractor spec reached five thousand lines of pure specification with zero lines of code. At story ninety-nine, someone had written about an agent escaping a container in a thought experiment and five layers of defense holding firm.

Now this. Story one hundred. A number that meant nothing to a machine and everything to a human. A centennial. A round number. An excuse to pause and look backward before continuing forward.

What had the hundred stories documented? A factory that ran without lights. Agents that wrote code and never complained. A Digital Twin Universe where you could test dangerous things safely. A context store built in three languages. A pipeline runner described in Graphviz. A leash that was also a garden bed. Policies written in Cedar. Tokens that expired in an hour. Containers that started in two seconds.

And three people. Always three people.

Justin, who said things like "code must not be written by humans" and then went home to tend plants that grew on their own schedule, indifferent to his philosophy of automation. Jay, who read Hacker News at 11 PM and collected words like "hygroscopic" and found beauty in syscall traces. Navan, who wrote in physical notebooks and built Gopher browsers and bridged the retro internet to the post-human one.

The archive was a love letter to a workplace. Not a romantic love—a craftsman's love. The love you feel for a well-tuned machine, for a team that works without friction, for a Tuesday afternoon when the tests pass and the traces are clean and the coffee is hot and the container holds.

One hundred stories. Each one a window into a room where three people and an unknowable number of agents were building something that hadn't existed before. Each one a small act of witness. Each one a refusal to let the work disappear without being recorded.

The archive didn't know it was an archive. It was just a directory full of HTML files. But the stories knew they were stories. And the readers knew they were reading something true.

On to one hundred and one.