I watched her hand flatten across the paper before the model could finish its sentence. The screen still glowed with the next paragraph it wanted to write, but her fingers stayed put.
“That phone number stays out,” she said. Not angry. Just final.
We’d given the agent every scrap from the file, names, notes, the custody flag, even the tone we wanted for the kids. It sounded right until it didn’t. The real limit wasn’t tokens. It was the person who knew when the output had to end.
Quick answer: A context window closes safely only when a named human who owns the outcome can override the model before anything ships. Retrieval can surface the correct policy paragraph, but only a coordinator with the live family details knows when that paragraph no longer applies, so the fix is a manual override gate between generation and export, not a bigger context window.
Solomon’s judgment turned on the mother’s willingness to surrender what she claimed as hers. The false claimant accepted the sword because she treated the child as an object to be divided. The true owner revealed herself by refusing any outcome that damaged the child. The test was not clever wording. It was whether the person who carried the real cost would override the proposed solution in the moment.
That same pattern shows up when an agent holds ministry policy in its context window. The model can retrieve the written rule, yet it still proposes the split that looks efficient on paper. Only the coordinator who owns the outcome will stop the generation before the output leaves the table.
The retrieval step that still needed the printed sheet on the table
The curriculum agent had been tuned on every prior policy document we could load. Child-protection language, consent requirements, and emergency contact rules all sat in the vector store. Retrieval returned the correct paragraphs on the first pass.
Still the generated plan included a suggested follow-up that would have violated the rule in practice. The policy text described “no direct contact without documented guardian consent.” The live case involved a split household where one parent had already revoked consent verbally. The model treated the stored paragraph as sufficient. The coordinator treated the current family as the actual constraint.
She kept her hand on the paper until the new prompt was rewritten with the specific names removed. Only then did she lift it. The sheet had done work the retrieval step could not.
How the 12-factor pattern failed the moment policy language met live family data
The 12-factor approach treats configuration as external and immutable. Secrets and rules live outside the codebase so the same container can run in any environment. That separation works when the rules themselves stay stable across deployments.
Ministry policy does not behave that way. The written rule stays fixed, but the live data changes every week. A single custody update, a new restraining order, or a verbal clarification from a parent alters what counts as compliant output. The agent cannot treat the policy paragraph as a static config value and still produce safe results.
When we tested the same prompt across two different families, the model produced nearly identical lesson structures. Only the coordinator’s override distinguished the safe version from the unsafe one. The 12-factor separation had removed the very signal the workflow required.
The override gate that turned the agent from liability into usable tool
We added a single gate after generation but before any export. The output paused and required the named coordinator to review and either approve or edit in place. The gate did not ask for a second model pass. It asked for the person who would answer for the decision if something went wrong.
That change dropped the false-positive contact suggestions to zero in the following month of use. More importantly, the coordinators began feeding the agent tighter constraints because they knew their edit would actually hold. The model stopped being a black box that occasionally leaked protected information and became a drafting tool that still answered to the owner of the constraint.
The printed sheet stayed on the table for the first few sessions. After the gate proved reliable, the coordinator left it in her bag. The override had moved from paper to process, but the principle stayed the same: the person who bears the real cost keeps the final say.
Frequently Asked Questions
Why did retrieval alone fail to keep the AI agent’s output safe?
Retrieval correctly surfaced the stored policy paragraph, but the paragraph described a general rule while the live case involved a specific, recently changed family circumstance the stored text couldn’t capture. Only a person with current context could catch the mismatch.
Why doesn’t the 12-factor “config as external and immutable” pattern work for ministry policy?
That pattern assumes rules stay stable across deployments. Ministry policy paragraphs stay fixed, but the underlying family data changes weekly, custody updates, revoked consent, new restrictions, so treating the policy as a static config value strips out the signal the workflow actually needs.
What exactly is an “override gate” and why did it work better than a bigger context window?
It’s a required pause between generation and export where a named coordinator reviews and approves or edits the output. It worked because it put final authority with the person who would answer for the outcome, dropping false-positive contact suggestions to zero within a month.
Your Turn: Apply This Today
- Pull the three policy documents that govern your highest-volume workflow this week and load them as separate files rather than one merged context block.
- Identify the single coordinator who signs off on edge cases for that workflow and schedule a thirty-minute test session with her before any new agent prompt ships.
- Build a manual override gate that stops generation and surfaces the full draft for her review before export or sharing.
- Run the same prompt against two live cases with differing constraints and log exactly where the model output diverges from the policy owner’s decision.
- Update the gate prompt to include the specific names or case numbers the coordinator flags during the test so future runs surface them automatically.
- Measure the number of agent generations that required an override in the first week after the gate goes live and adjust the retrieval window size based on that count.
The Agent Loop Ministry Teams Quietly Rebuilt by Hand showed what happens when coordinators keep the real constraint outside the model. The Harness Ministry Coordinators Built Instead of the General Tool described the moment the override moved from ad-hoc fixes to a repeatable gate.
I consult with ministry product leads on agent context design, policy override mechanisms, and workflow ownership in faith-tech tools. Let’s talk.