Constraints have opinions

Three audits, one data pull. Didn't plan it that way — it emerged.

The scoring engine had to be platform-agnostic because the connector abstraction required a common ticket interface. That decision, made early for a different reason, meant all three audits shared the same input type. One scan. Three outputs.

When you constrain things tightly enough, the architecture starts having opinions about what belongs together.

This is the thing about working lean that doesn't get said enough. The benefit isn't that you ship faster. It's that tight constraints force the structure to be honest. There's no room to paper over a bad interface with a convenience layer. The pieces have to actually fit.

The suite wasn't a product decision. It was an architectural consequence.