I opened the review doc on Tuesday and saw the same three constraints written out in full, again. Not because anyone forgot. Because the thread from Friday had already been cut.
We’d hit 82 generations the week before. Clean count on the dashboard. Then we swapped the general chat for a harness that carried the actual rules. Output fell to 61. The surprise wasn’t the drop. It was that every single one of those 61 still made sense on Wednesday morning.
The 50-generation score that flipped when the harness locked the calendar
We ran a controlled test on children’s ministry scheduling. The general agent produced 50 usable drafts across four weeks. Each draft still required the coordinator to paste the current date range, the room list, and the volunteer availability back into the thread because the model had already forgotten them.
After the harness added a persistent calendar object that updated only through a single approved tool call, the same team reached the same 50-generation mark in nine days. The difference was not speed of generation. It was that no draft after the first one needed the coordinator to restate the constraints.
The reset count fell from 3.2 per completed schedule to 0.4. Most of those remaining resets came from external changes, not from the agent losing its place. Munger would call this the difference between a system that compounds and one that restarts.
How tool adapters replaced three separate Slack threads
Before the harness, a volunteer confirmation workflow lived in three channels: one for the initial ask, one for room confirmation, and one for last-minute swaps. The general agent could generate the text for any single channel, but it could not carry the decision from one channel into the next without a human pasting the outcome.
The harness added three small adapters. One read the room calendar API, one wrote to the volunteer database, and one posted the final confirmation. The agent now moved the decision across all three without new context. The coordinator stopped opening Slack to reconcile the threads.
The same pattern appeared in curriculum assignment for SermonCentral-style resources. The harness kept the volunteer skill tags and the print deadline in one object. Output volume stayed roughly flat, but the number of follow-up messages dropped by more than half.
The repeatable job that finally stayed inside the 11 p.m. boundary
One coordinator ran volunteer scheduling every Tuesday night. The general agent often produced a first draft by 9:30, yet the back-and-forth over missing constraints pushed the final sign-off past 11:00 on six of the last eight weeks. The extra time came from repeated explanations of blackout dates and age-group rules.
Once the harness stored those rules in a locked object and required the agent to call an update tool rather than restate them, the Tuesday workflow closed by 10:10 in seven of the next eight weeks. The coordinator reported sleeping through the night for the first time in months.
The measurable change was not the agent’s intelligence. It was the removal of the context tax that had been invisible in the generation count.
Your Turn: Apply This Today
- Choose one ministry task that repeats at least weekly, such as volunteer scheduling or print-ready lesson assignment, and write down its three fixed constraints in a single document.
- Build a one-page harness that stores those constraints as a persistent object and exposes only a single update tool call instead of free chat.
- Run the task through both the general chat agent and the new harness for two cycles, counting every message that restates a constraint already given earlier in the thread.
- Log the reset count and the clock time from start to final approval for each cycle in a simple spreadsheet.
- Compare the two sets of numbers and note which column, resets or raw generations, moved more.
- Keep the harness version for the next four weeks and record whether the reset count stays below one per cycle before deciding to expand it.
The Year I Chased General Tools Before Building the One Harness That Stuck shows the cost of measuring only volume. The Context Window That Only Closed When a Real Coordinator Sat Down tracks what happens when the harness finally holds the variables that matter.
I consult with ministry product leaders on custom harness design for repeatable workflows, context reset measurement in AI agents, and volunteer-facing product constraints. Let’s talk.