You’re looking at a finished lesson at 11:42 p.m. The model wrote the whole thing—story, questions, craft, even the verse the kids are supposed to memorize. It took less than a minute. The only person whose name actually goes on it is two states away until Friday, and she still has to read every line before anything leaves the building.
The question isn’t whether the output is good enough. It’s what happens when the person who carries the weight isn’t in the room when the thing gets made.
Solomon’s old test still works. The one who refused to let speed settle the matter was the one who actually had something to lose.
This is the foundational misread that causes product teams to treat approval as a routing problem instead of a knowledge problem. When the model runs ahead of the person who carries the cost, the output simply waits in a queue that no one has capacity to review. The 7-minute volunteer then inherits the risk.
At one children’s curriculum ministry the real retention metric was never download volume. It was whether the volunteer finished the lesson and used it without having to improvise under time pressure. The same constraint applies to any agent that generates curriculum or service copy. Fluency at generation does not reduce the need for the one human who can say, without looking at a screen, whether the content will land in the actual room.
Systems thinking applied to one physical signature
Systems thinkers map every handoff. The signature is the last handoff, and it is still physical. It happens on a printed sheet, a PDF markup, or a verbal confirmation after the staff member has read the full set of changes against the names and stories they know. Every upstream agent that assumes this step can be parallelized or batched will eventually produce work that sits idle until that one person is available.
The constraint is not reluctance. It is capacity. One person cannot absorb the volume the model can produce while also carrying the pastoral load that justifies their authority in the first place. The system must therefore reduce the surface area of what reaches the signature, not increase the speed at which drafts arrive.
This matches the logic in Solomon’s judgment. The decision was never about who could claim the child fastest. It was about who would still be responsible after the claim was settled. In product terms, the signature is the point at which responsibility is accepted. Design everything else to make that acceptance possible in the time the signer actually has.
When the dashboard score and the room decision diverge
Dashboards track completion rates, generation time, and version counts. None of them capture whether the final version was usable in the room where the volunteer stood. A lesson can score 94 on every automated check and still require the staff member to rewrite the closing prayer because the model used language the church’s particular tradition avoids. The dashboard will never register that mismatch.
The person who signs off holds the memory of previous rooms and previous failures. That memory is not stored in the model weights and cannot be queried through a prompt. When the dashboard and the signer disagree, the correct signal is the signer’s refusal, not the dashboard’s score. Treating the refusal as noise is how teams erode the very authority they claim to respect.
The pattern repeats across ministry tools. The coordinator who has led the same group for three years will reject a perfectly formatted schedule because she knows two families will be traveling. The model cannot hold that fact. The dashboard cannot weigh it. Only the signature step can.
Your Turn: Apply This Today
- Pick the single approval step that still sits outside every agent loop in your current workflow and write the exact handoff rule that tells the agent what information must reach the signer and in what format.
- Block two 30-minute slots on the signer’s calendar this week labeled only “review window” and instruct the agent to hold all output until those slots rather than pushing drafts as they finish.
- List the three facts the signer must know that the model cannot access (recent pastoral conversations, family situations, last-minute room changes) and create a one-paragraph template the volunteer or coordinator fills before the output reaches the signer.
- Remove any automated “ready for signature” notification that does not include the name of the person who will actually be in the room and one constraint that person has already named this month.
- Run the next generated artifact through the 7-minute test: open it on a phone, give yourself seven minutes, and note every line that would require the signer to stop and ask a question. Rewrite the handoff rule to surface those lines first.
- Document the last three times the signer changed an agent-generated draft and turn each change into a standing check the agent must run before it reaches the signature step again.
The Permission Gate That Kept the Agent From Running the Schedule and Why Ministry Coordinators Still Ask Me About the Routing Step both trace the same pattern: authority remains with the person who will still be present when the work is used.
I consult with product leaders building faith-tech tools and ministry leaders running volunteer workflows on approval gates, signature timing, and dashboard versus room decision alignment. Let’s talk.