I watched the cursor blink while the agent added another line about the Wednesday night kids check-in that no one had run since March. The volunteer coordinator had already texted twice asking why the schedule kept listing rooms that don’t exist anymore. I’d rewritten the context file six times. Every version still invented the kind of tidy rhythm that only exists in planning documents.
The problem wasn’t missing information. It was that the real constraints live in the gaps between people’s actual weeks—the sick kid, the elder who forgot to mention he’s traveling, the small group that quietly shifted because two families moved. Those details don’t sit in a file waiting to be discovered. They’re carried in bodies and conversations.
I used to think the fix was simply more thorough prompting. Then I started wondering what it would take for the agent to treat ministry the way Scripture does: as something that happens in time, with actual people, not as a set of stable variables.
The six rewrites that exposed my over-reliance on prompt length
The first version was a single 4,000-token block that listed every possible ministry role and constraint I could name. The agent still invented a children’s director who had never existed. The second version broke the block into sections with explicit “do not invent” rules. The fabrications moved to a different part of the output.
By the fourth rewrite I had added examples of past handoff failures. The fifth tried JSON structure. None of them held once the workflow moved from my laptop to the actual coordinator’s desk on a Thursday night. Only after the sixth pass, when I stopped trying to encode everything in the prompt and instead kept a short, human-maintained file that the coordinator edited after every event, did the invented details disappear.
Each rewrite had lengthened the prompt. The successful version shortened it and moved the maintenance burden to the person closest to the work.
How ministry coordinators actually use the same context file week after week
The file that finally worked sits in a shared folder and contains four recurring sections: current volunteer roster with phone numbers, room capacities and restrictions, the last three weeks of schedule changes, and a one-paragraph note on what went wrong last time. Coordinators open it every Monday, spend three minutes updating the note, and save. They do not rewrite the whole document.
When they hand the file to the agent on Thursday, the agent produces a draft that matches the actual constraints because the file already encodes the exceptions the model could never retrieve. The coordinator then spends another two minutes striking anything that still feels off before printing. The loop stays short because the file is treated as a shared record rather than a prompt that must be perfect on the first try.
Torres would recognize this as discovery happening at the moment of use, not in a quarterly research sprint.
Why frozen context beats live retrieval when a volunteer is printing at 9 p.m.
Live retrieval sounds attractive until the volunteer is standing at the copier with a deadline. At that hour the retrieval system may pull last month’s room assignment or an outdated volunteer list because the source data has not been corrected yet. A frozen context file that the coordinator touched the same morning already contains the correction.
The agent cannot call an API at 9 p.m. and know that the youth room is being painted this week. The coordinator who walked past the paint cans that afternoon can add one line. Once that line exists in the file, the agent respects it without needing another round of prompting. The file becomes the single source that survives the handoff when systems are asleep or data is stale.
Your Turn: Apply This Today
- Pick one recurring workflow that already uses an agent and create a new text file named exactly after that workflow.
- Limit the file to the four sections described above and delete anything that has not changed in the last thirty days.
- Share the file with the one person who runs the workflow and ask them to spend two minutes updating the “what went wrong” note after the next event.
- Replace the longest section of your current system prompt with a single instruction to read that file first.
- Run the agent output against the file in a live session and note every invented detail that appears.
- Schedule a ten-minute calendar block every Monday to review the file with the actual coordinator rather than with the model.
The same pattern appears in the post about the context window that only closed when a real coordinator sat down, and it shows up again in the year I chased general tools before building the one harness that stuck.
I consult with product leaders building ministry and faith-tech tools on persistent context design, workflow-specific context maintenance, and avoiding over-reliance on model scale for handoff reliability. Let’s talk.