Justin opened a markdown file and put it on the shared monitor. It was long—several hundred lines—and it was written entirely in English. No code blocks. No pseudo-code. No UML. Just paragraphs, headings, numbered lists, and the occasional bold phrase where emphasis was structurally necessary.
"This is an NLSpec," Justin said. "Natural Language Specification."
Navan scrolled through it. The document described a system: its inputs, its outputs, its behaviors under normal conditions, its behaviors under abnormal conditions, its edge cases, its failure modes. It was meticulous. It was also, unmistakably, a document that a human could read over lunch and understand completely.
"It reads like a very precise essay," Navan said.
"That's the point. It has to be readable by two audiences: humans and language models. The intersection of what both can understand is natural language. Not code. Not diagrams. Prose."
Jay leaned back. "So you give this to an agent and the agent writes the code?"
"The agent writes the code, runs it, tests it against the scenarios, and iterates until the satisfaction metric passes the threshold. The NLSpec is the agent's only input. Everything the agent needs to know about what the software should do is in this document."
Navan was quiet for a long time. Jay watched him scroll to the top of the NLSpec and start reading it again from the beginning, more slowly this time, the way you reread a letter when you realize it isn't what you thought it was.
"This isn't documentation," Navan said.
"No."
"Documentation describes something that already exists. This describes something that doesn't exist yet. And the description itself causes it to exist."
Justin pointed at Navan. "Say that again."
"The spec IS the product." Navan looked up from the screen. "The markdown file isn't describing the software. It's generating the software. The spec is an input to a function whose output is working code. Which means the spec isn't a byproduct of development. It's the primary artifact. It's the source of truth."
"And what does that make us?" Justin asked, the question aimed at the room.
"Spec writers," Jay said.
"Spec writers," Justin confirmed. "The best spec writers in the world. Every word matters. Every sentence has to be precise enough that a language model can turn it into correct code without ambiguity. You're not writing documentation. You're writing instructions for a machine that takes language literally."
Navan closed his notebook. He didn't need to write this down. It was the kind of realization that embeds itself the first time, like a key finding the lock it was cut for.
"I need to reread this entire spec," he said. "Slowly. Like it's source code."
"It is source code," Justin said. "It's just written in English."
This is the story that made me understand what the factory actually IS. The spec isn't about the product. The spec IS the product. I've reread this one four times.