A narrow harness, not a general-purpose AI agent, is what keeps ministry coordination work safe. The “general-purpose AI agent” recommendation that circulates through product strategy sessions and frameworks like the one in Marty Cagan’s books falls apart the moment it meets ministry coordination work. That approach pushes teams to ship a single model that handles intake, routing, formatting, and handoff for every role. It promises lower maintenance and broader adoption. In practice the model erases the exact checkpoints that keep a coordinator from sending a child to the wrong room or printing a curriculum page with the wrong date.
Quick answer: Skip the general-purpose AI agent for ministry coordination work. Build a narrow harness instead: one that locks child-protection fields, kiosk name formatting, and curriculum export gates so the model can propose changes but never silently overwrite the details that matter.
Coordinators do not need another flexible assistant. They need outputs they can audit in under two minutes without opening a second screen. When the general agent varies a single field on its own, the coordinator loses the signal that something went wrong. Trust does not recover after the first incident.
This is the foundational misread that causes product teams to ship agents that look complete in demos yet create silent failure loops in the field. The agents optimize for coverage instead of exposing the three constraints that actually determine whether a workflow stays safe. Teresa Torres’s continuous discovery work supplies the corrective lens. Torres insists teams maintain direct, repeated contact with users to surface the jobs that matter most. When applied here, the practice reveals that the jobs are not broad categories like “manage events” but narrow, non-negotiable gates: deterministic child-protection fields, fixed kiosk outputs, and coordinator-controlled curriculum exports. Discovery does not end when the first prototype ships; it continues by watching whether those gates remain visible after every model update.
Child-protection fields a narrow harness must keep deterministic
Ministry coordinators who manage children’s programming treat certain data points as fixed once entered. A child’s allergy flag, custody note, or room assignment cannot be reinterpreted by a model. When a general agent rewrites or softens one of those fields to “improve readability,” the change travels downstream before anyone notices.
Teams that tested broad agents on volunteer scheduling saw the model swap a documented peanut allergy for a generic “dietary preference” label in two separate test runs. The coordinator caught it only because she printed the list herself. Continuous discovery sessions with four different coordinators showed the same pattern: the moment the agent treats a protected field as editable text, the entire output requires manual re-verification that defeats the supposed time savings.
The narrow harness keeps those fields in a locked schema. Any generation attempt that touches the field triggers an explicit flag rather than a silent rewrite. Coordinators report they now scan only the flagged lines instead of rereading every record.
Kiosk check-in outputs that cannot vary by even one name
Check-in kiosks at larger campuses print name tags and parent receipts in a single pass. A one-character difference in a child’s printed name creates immediate line confusion and erodes parent confidence. General agents trained on varied datasets introduce small formatting shifts—middle initial placement, nickname expansion, suffix handling—on roughly one in twelve prints during observed sessions.
One site replaced the general agent with a harness that ingests the exact kiosk template and emits only the permitted string lengths and capitalizations. The model still suggests room assignments, yet the name block passes through a deterministic formatter before printing. Coordinators now treat the kiosk print step as a verification gate rather than a source of surprises. They keep the harness version pinned and reject any model update that would loosen the formatter.
Curriculum export steps that still need the coordinator’s final gate
Sermons4Kids-style exports move from planning screen to printed packet in three clicks for hundreds of volunteers each week. When a general agent was allowed to reorder or condense lesson pages, coordinators lost the ability to confirm that every page carried the correct copyright line and the week’s date. Two teams reported volunteers arriving with incomplete packets because the agent had dropped the final page during generation.
The replacement harness enforces a fixed export sequence and surfaces a single confirmation screen that lists page count, date, and copyright status before the file is released. The coordinator must click “approve” on that screen; the model cannot bypass it. Continuous discovery showed that coordinators accepted the extra click once they saw the failure rate drop.
The harness therefore preserves the human gate without forcing the coordinator to open the full document again. The model proposes, the harness constrains, and the coordinator retains final authority on the artifact that reaches volunteers.
Your Turn: Apply This Today
- Pick the single workflow your current general agent touches most often and list its three hardest constraints in writing before touching any code.
- Replace the general agent call in that workflow with a narrow harness that hard-codes the first constraint as a schema rule rather than a prompt instruction.
- Run the harness on last week’s real data set and count every silent change it prevents; share the count with the coordinator who owns the workflow.
- Pin the harness version and add an explicit rejection rule that blocks any future model update from loosening the second constraint.
- Schedule one 20-minute discovery call this week with the coordinator to watch them use the harness output and note the exact moment they decide to trust it.
- Document the third constraint as a required human gate in the harness and remove the model’s ability to generate the final artifact without that gate.
Frequently Asked Questions
What is a “narrow harness” in an AI ministry workflow?
A narrow harness is a constrained layer that sits between a general AI model and a ministry task. It locks specific fields, formats, and approval gates so the model cannot silently alter protected data like allergy flags, printed names, or curriculum exports.
Why not just use a general-purpose AI agent for everything?
A general-purpose agent optimizes for broad coverage, not for the narrow constraints that keep coordination work safe. It can quietly reformat a custody note or drop a curriculum page, and coordinators often do not discover the change until a volunteer or parent is already affected.
How do I start replacing a general agent with a narrow harness?
Pick the single workflow the general agent touches most, write down its three hardest constraints, and hard-code the first one as a schema rule instead of a prompt instruction. Then run the harness against a week of real data and count every silent change it prevents.
The pattern in “The Volunteer Who Tried the New Voice Agent on a Baptism Outline” and “The Caching Shortcut That Quietly Broke Three Ministry Agents” shows the same erosion when general tools hide failure points instead of surfacing them.
I consult with ministry product leaders and church tech teams on baking deterministic constraints into agent harnesses and running continuous discovery that keeps those gates visible. Let’s talk.