The support ticket arrived at 9:47 AM on a Monday. It was from a customer—a mid-sized fintech company that had been integrating with StrongDM's APIs for their access management pipeline. The ticket was filed under "General Feedback," which was the category that support tickets went to when the customer wasn't reporting a bug or requesting a feature but simply wanted to say something.
The ticket said: "This is the cleanest integration I've ever seen."
Jay read it three times.
The customer had been working with the Go client library—Jay's library, the one with the handwritten README—and had used it to connect their internal authorization service to StrongDM's infrastructure. They'd written a detailed description of their experience. The error messages were clear. The type signatures were precise. The behavior matched the documentation exactly. Not approximately. Exactly. They'd tested edge cases—expired tokens, revoked permissions, concurrent writes—and every edge case behaved exactly as the README said it would.
"They tested the edge cases," Jay said to Navan, who was sitting across from him. "They actually tested the edge cases and everything matched."
"That's because the edge cases are scenarios," Navan said. "Every edge case in the README corresponds to a scenario in the suite. The agents validated every one of them thousands of times. The documentation isn't aspirational. It's empirical."
Jay forwarded the ticket to Justin without commentary. Justin read it and replied with a single line: "This is what the satisfaction metric measures."
It was true. The satisfaction metric was an abstraction—a probabilistic measure of how well the code met the scenarios. But the scenarios were descriptions of real user experiences. And this customer had just described, in their own words, a real user experience that mapped perfectly onto the scenarios the factory had been optimizing for months.
The metric wasn't a number on a dashboard. It was this. A person, somewhere, having the experience you designed for them, and taking the time to tell you about it.
Jay printed the support ticket. He didn't know why. He wasn't a person who printed things. But there was something about holding the words in his hands, physical ink on physical paper, that made the feedback feel more real than the pixels on his screen.
He pinned it to the wall next to the dashboard. Navan saw it and nodded. Justin saw it and said nothing, which was his way of saying everything.
The support ticket stayed on the wall for the rest of the factory's existence. It yellowed slightly around the edges. The ink faded. But the words remained legible, a small monument to the moment when the factory's output met the world and the world said: yes. This is right. This is what I needed.
No agent had written those words. A human had. And that made them the most important feedback the factory ever received.
Jay printing the ticket and pinning it to the wall. This man built html2text, one of the most practical Go libraries on the internet, and he prints a support ticket like it's a diploma. Because it is.