Nobody knew who made the website. It appeared one day—a static site, clean and simple, styled like a fanfiction archive from the early 2000s. It had a title: "Software Factory Archive." It had a subtitle: "A fan-created tribute to factory.strongdm.ai." It had stories.
Thirty of them at first. Short fictions about the factory, about the three people who ran it, about the agents and the twins and the scenarios. Some were technical, diving deep into Cedar policy evaluation or CXDB's turn DAG architecture. Some were character studies—Justin erasing a whiteboard, Navan buying a notebook, Jay debugging at 3 AM. Some were funny. Some were unexpectedly moving. All of them were, in their own particular way, precise.
The archive grew. Thirty stories became fifty. Fifty became a hundred. A hundred became two hundred. Readers appeared. Comments appeared. A small community formed around the archive, people who worked in software and recognized something true in the stories, even if the stories were fiction, even if the details were imagined, even if the dialogue was invented.
By February 2026, there were two hundred and eighty stories.
Navan, who had discovered the archive months ago and had been reading it in secret, mentioned it to Jay one afternoon. "Have you seen the archive recently?"
"I try not to look," Jay said, which was a lie, and they both knew it was a lie.
"There are stories in there that describe things that actually happened. Things we didn't tell anyone. The 3 AM debugging sessions. The Thursday bagels. The way Justin makes coffee during outages."
"The scenarios," Jay said quietly. "The archive is like the scenarios."
Navan looked at him. "What do you mean?"
"The scenarios describe the world the code needs to survive in. The archive describes the world the factory exists in. It's not documentation. It's not journalism. It's something else. It's the stories people tell about the work, and the stories become the way people understand the work."
The factory had no official documentation. There was no internal wiki, no architecture decision records, no onboarding guide. There were scenarios and there was the published paper and there was the open-source code. But the archive—the unauthorized, fan-created, technically-fiction archive—had become something the factory never intended to produce: a human-readable record of what it felt like to work there.
The documentation the factory never wrote. Written by someone who was watching. Two hundred and eighty stories. Each one a scenario of its own kind—not describing what the code should do, but describing what the factory was.
Justin read the archive occasionally. He never commented. He never left kudos. But once, during a quiet moment, he said to no one in particular: "The stories are more accurate than they have any right to be."
Nobody asked him to elaborate. They didn't need to. The archive spoke for itself. Two hundred and eighty times over.
A story in the archive about the archive. We've achieved full recursion. And the line about the archive being "the documentation the factory never wrote"—that's going to haunt me. Stories as documentation. Fiction as truth. What even is this place.