Software Factory Archive

Justin wrote it on the whiteboard in blue marker, underlined it twice, and stepped back like he'd just unveiled a cathedral.

0.99999

Jay looked at it. Looked at Justin. Looked back at the number.

"Five nines," he said flatly.

"Five nines of satisfaction," Justin confirmed, capping the marker. "Across all scenarios. That's the target."

Navan, who had been eating a granola bar at his desk, stopped chewing. "Justin. We're at ninety-three percent."

"Ninety-three point four," Justin corrected.

"Right. So you want us to go from point-nine-three-four to point-nine-nine-nine-nine-nine." Navan paused. "That's—that's not the same kind of distance as going from zero to ninety-three."

"No," Justin agreed cheerfully. "It's much harder."

Jay leaned back in his chair. He'd been at the factory for three months now. He'd learned to recognize Justin's moods. There was focused-Justin, who could debug a scenario definition in his head. There was philosophical-Justin, who would monologue about the nature of software correctness while making pour-over coffee. And then there was this Justin—the one who set targets that sounded like they'd been generated by a random ambition engine.

"Five nines is what they use for uptime at tier-one cloud providers," Jay said carefully. "That's five minutes of downtime per year."

"I know what five nines is."

"For satisfaction metrics, it would mean that out of every hundred thousand observed trajectories through our scenarios, at most one fails to satisfy the user."

"I also know what it means for satisfaction metrics," Justin said. "I invented the satisfaction metrics."

Navan looked at Jay. Jay looked at Navan. They had developed a silent communication protocol over the past few months—a shared vocabulary of eyebrow movements and slight head tilts that roughly translated to "is he serious?" and "I think he's serious" and "we're going to be here a while."

The current exchange meant all three simultaneously.

"Here's the thing," Justin said, sitting on the edge of his desk. "Ninety-three percent sounds good. It sounds like an A. But it means that roughly one in fifteen user journeys through our scenarios has a moment where the system does something unsatisfying. One in fifteen. If you went to a restaurant and one out of every fifteen bites of your meal was wrong, you'd leave."

"I would leave at one in fifteen," Navan admitted.

"Five nines means the system is so correct, so aligned with user intent, that failure becomes a statistical event rather than an experiential one. Nobody will ever encounter it. It exists only in the math."

Jay stared at the whiteboard. The number glowed in blue marker like a dare.

"The agents will need harder scenarios," he said finally. "A lot harder. If we want them to converge on five nines, the scenario space has to be rich enough to expose every remaining failure mode."

"Now you're thinking about it right," Justin said, and smiled.

Navan finished his granola bar. "For the record," he said, brushing crumbs off his keyboard, "I think this is insane. But I thought non-interactive development was insane four months ago and now I can't imagine going back to code review, so." He shrugged. "Five nines. Sure. Why not."

Jay pulled up the scenario editor. "I'm going to need more coffee."

"We're going to need more tokens," Navan corrected.

Justin was already back at his desk, typing. Probably calculating how many thousand-dollar days stood between 0.934 and 0.99999. Jay suspected the answer was "a lot" and that Justin already knew the exact number and had decided it was worth it.

He was usually right about these things. That was the most annoying part.