You open the spreadsheet on a Tuesday morning and the number stares back like it already made the decision. Ten months of runway, a headcount line, and a blank “use case” field that everyone expects you to fill before the next steering call.
The demo you watched last week produced clean, safe copy in under a minute. It just didn’t sound like anyone who has ever had to stand in front of real people on a Sunday and own what was said.
That single choice exposed the real constraint. The denomination’s surface area is not compute. It is the distance between an output and the moment a volunteer decides whether to use it or rewrite it by hand. Sovereign control over routing would have sent that task to a smaller, fine-tuned model trained on actual volunteer feedback instead of routing everything through the frontier model for marginal coherence gains.
Zone-based coordination replaced feature ownership once the team stopped assigning agents to single product areas. Instead they mapped three zones: preparation, delivery, and follow-up. Each zone carried its own data residency rule and latency budget. Preparation agents could use heavier models because they ran overnight. Delivery agents stayed on lighter, on-premise inference so a last-minute children’s lesson change did not depend on an external queue. Follow-up agents lived inside the existing volunteer workflow tool so completion data stayed inside the same system that already measured whether the lesson was actually taught.
The shift removed the old feature-owner meetings where one person defended their agent’s scope. Decisions moved to routing tables reviewed every two weeks. The tables listed model, residency, maximum cost per task, and the single human checkpoint required before the output reached a volunteer. Ownership became maintenance of the table rather than defense of a feature.
The routing rule that protected Sunday validation emerged from the same table process. Any agent output intended for direct use in a worship service had to route through the on-premise model first. Only if that model returned a low score did the task escalate to the larger hosted model, and even then the output carried a required human review tag before it could be scheduled. The rule looked conservative on paper. In practice it cut the number of unusable drafts that reached the Sunday morning test by more than half. The cost per validated item dropped because the expensive model was invoked only after the cheaper one had already filtered obvious mismatches.
The rule also surfaced a second pattern. Volunteer completion rate, not generation volume, became the metric that determined whether a routing change stayed in the table. When completion dipped, the team adjusted residency or model size before touching prompt language. The routing table turned into the place where taste was enforced rather than hoped for.
The first decision that revealed the taste gap
The vendor demo surfaced the gap because no one had defined what “good enough for a seven-minute volunteer” actually meant in tokens or latency. The team measured against public leaderboards instead of against the printed sheet that gets left on a kitchen table. Sovereign routing starts by writing that definition down before any agent is turned on.
How zone-based coordination replaced feature ownership
Feature ownership rewarded the person who shipped the most agents. Zone coordination rewarded the person who kept the routing table accurate when volunteer data changed. The difference showed up in the first month the new table ran: three agents were retired because their residency rule no longer matched the actual data sources used on Sunday.
The routing rule that protected Sunday validation
The rule required on-premise inference for any worship-facing output and a human checkpoint for anything that escalated. It did not eliminate the frontier model. It made the frontier model the exception rather than the default path. That single constraint preserved the judgment that lives in the room on Sunday morning.
Your Turn: Apply This Today
- Write one explicit routing rule this week that names the model, the residency location, and the maximum cost allowed for any task that reaches a volunteer.
- Map the three zones your current agents touch and assign each zone its own residency requirement before the next sprint planning meeting.
- Pick the single human checkpoint that must occur before any escalated output reaches Sunday materials and add it to the routing table as a required field.
- Run last week’s highest-volume agent task through the new rule and record the change in cost and volunteer completion signal.
- Remove any agent whose routing table entry cannot be defended with a real volunteer metric by Friday.
- Schedule the first two-week review of the routing table with the people who actually print and use the outputs.
The same tension between default scale and retained judgment shows up in both Letter to the PM Who Now Arbitrates Taste and Why Top PMs Still Route Specs Through Sunday Validation. The posts walk through parallel cases where control over the path mattered more than model size.
I consult with product leaders at faith-based organizations on inference routing, data residency choices, and Sunday validation loops. Let’s talk.