The term came from manufacturing. Level 5. The dark factory. A production facility where automation has advanced to the point that no human workers are present on the floor. The machines run in the dark because machines don't need light. The factory produces output twenty-four hours a day, and no one is there to watch.
Jay found the reference in a manufacturing journal he'd been reading—he read widely, always had, collecting vocabulary the way other people collected stamps. "Hygroscopic" from a chemistry paper. "Internecine" from a history book. And now "dark factory" from a feature about FANUC's robotics facility in Oshino, Japan, where robots built other robots in unlit warehouses.
He mentioned it at a standup. "There's a manufacturing concept called Level 5 automation. The dark factory. No humans on the floor. Machines working in the dark."
Justin looked up. "Say that again."
"The dark factory. Level 5. Lights-out manufacturing."
The phrase settled over the room the way a good metaphor does—not by explaining something new, but by revealing something that was already there. The software factory had agents writing code around the clock. No human wrote the code. No human reviewed the code. The agents didn't need an IDE open on a screen. They didn't need syntax highlighting. They didn't need dark mode or light mode. They ran in containerized environments that had no display output at all.
The software factory was already dark. They just hadn't named it.
"The dark factory," Navan repeated quietly. He wrote it in his notebook.
The label stuck because it was precise without being sensational. Other labels had been tried—by the press, by commenters, by people who encountered the factory's methodology and needed a shorthand. "Fully autonomous development" was accurate but clinical. "AI-only coding" was misleading, because humans were deeply involved in specification and scenario design. "Lights-out software" was close but sounded like a brand name.
"The dark factory" worked because it carried the weight of an existing concept. It connected software development to a decades-old manufacturing tradition. It implied maturity—Level 5 wasn't the first step; it was the last step in a progression. And it captured the essential strangeness of the thing: software being produced in environments that no human occupied or observed.
Justin started using the term in external conversations. At KuppingerCole, in podcast interviews, in the blog post. Each time, it functioned as a bridge. Manufacturing people understood it immediately. Software people understood it after a beat. Everyone understood the dark.
Jay added the term to his vocabulary collection, alongside "hygroscopic" and "internecine." But this one he used every day.
The dark factory. Level 5. Machines working in the dark, producing software that worked in the light. The label stuck because it was true, and true things are adhesive.
FANUC's lights-out factory in Oshino is a real thing. Robots building robots in the dark. Applying that label to a software factory where agents write code without human intervention is the most accurate tech metaphor I've seen in years.