The children’s coordinator pulled the warm pages from the printer tray and crossed the hallway to the volunteer holding the supply closet key. She handed over the agent’s Wednesday schedule, then took out a pen and struck through three of the listed rooms. The volunteer watched without comment and pointed to the actual key ring on the wall that only two people could access after 6 p.m.
Quick answer: General AI agents fail in ministry settings because they optimize against calendar data, not physical constraints like locked closets, key holders, and volunteer time limits. The fix is a narrow harness: a small set of hard-coded checks that encode the real-world rule (who holds the key, when the room is reachable) so the agent’s output never reaches a volunteer before it’s been validated against reality.
That single correction happened in under a minute. The agent had generated a clean list based on room availability data it pulled from the shared calendar. It had no way to know the closet key lived on a physical hook or that one volunteer unlocked it only during a narrow window before the first kids arrived. The coordinator fixed it by hand because she already carried the real constraints in her head.
This pattern repeats whenever a general agent meets ministry work. The agent produces output that looks complete on screen. The person closest to the physical room and the actual volunteer then edits it by hand, and harm, yet it wastes limited volunteer minutes and creates friction that drives people away from the work they came to do. A harness built around the actual constraint prevents that harm before the output reaches anyone.
Encoding the closet key and the 7-minute window
The Sermons4Kids team once tracked how long a volunteer spent on prep. Seven minutes was the average before attention fractured. Any output that required re-reading, re-checking, or walking to a different room ate into that window and lowered completion rates.
A harness can hold the key location and the seven-minute limit as hard rules. When the agent proposes a schedule, the harness rejects or rewrites any assignment that places materials behind a locked door the assigned volunteer cannot open in time. The rule lives in code rather than in one coordinator’s memory.
The same harness can flag when a room assignment requires two keys instead of one. It does not need longer context. It needs the right constraint written down once.
Why a small adapter beats a bigger model
An adapter that sits between the agent and the output can enforce the fixed sequence: check key holder, check time window, check room access. The adapter stays small because the steps do not change. Each new agent can plug into the same adapter without retraining.
Ministry teams already rebuild these adapters by hand when the general tool fails. One coordinator keeps a printed list of key holders. Another maintains a separate spreadsheet of room capacities after 6 p.m. The adapter simply moves that list into executable checks instead of separate documents.
The maintenance difference when the harness lives in code
When the constraint lives only in a person’s head, every staff change risks losing it. The new coordinator reprints the schedule and the same three rooms get crossed out again next week. When the constraint lives in the harness, the rule survives the person.
Maintenance also becomes measurable. The team can see how often the harness rejects an assignment, and harnesses improve when the actual closet key moves or the volunteer schedule shifts. The update happens in one place and applies to every future run.
Frequently Asked Questions
Why does a general AI agent keep producing schedules that need manual fixes?
The agent only sees the data it’s given, usually a shared calendar. It has no way to know about physical constraints like a locked closet, a single key holder, or a volunteer’s real availability window. Those facts live in a person’s head until someone encodes them.
What is a “harness” in this context?
A harness is a small set of hard-coded checks that sits between the agent and its output. It validates proposed schedules against real-world constraints, like key access and time windows, before anything reaches a volunteer.
Why not just use a more advanced or larger AI model instead?
A bigger model still lacks the specific physical facts about your building and your volunteers. The fix isn’t more intelligence, it’s encoding the fixed local constraints once so every future agent run respects them automatically.
Your Turn: Apply This Today
- Pick one recurring agent output your team edits by hand and list the exact physical constraint that forces the edit.
- Write a single check that tests for that constraint before the output reaches the volunteer.
- Run the next three schedules through the check and count how many get caught.
- Move the check into a lightweight script or spreadsheet formula so it runs without manual review.
- Replace the original general prompt with a call to the new check for that one workflow only.
- Track volunteer completion rate on the adjusted workflow for two weeks and compare it to the prior baseline.
The pattern shows up again in The Harness Ministry Coordinators Built Instead of the General Tool and The Agent Loop Ministry Teams Quietly Rebuilt by Hand.