You’re the product manager who just inherited the Fable Agent mandate at a denomination you only half-understand, and the brief says to ship something that feels like an AI assistant without breaking any existing volunteer workflows. The leadership team keeps repeating the same line about “safe defaults” and “conservative guardrails,” which sounded reassuring in the first three meetings. Now the first prototype sits in front of you and every suggested prompt returns the same careful, slightly generic answer. Inheriting an agent mandate like this means owning the decisions the model quietly makes for you.
That feeling is the signal. Fable 5’s training pushes it to stay inside a narrow band of acceptable ministry language and task patterns. The model was never rewarded for guessing what a children’s ministry volunteer actually needs when the craft supplies run out at 6:47 p.m. on a Tuesday. Most teams treat that narrowness as a feature. It is the exact place where product edge leaks away.
Charlie Munger’s circle of competence makes the cost visible. He warned that knowing the boundaries of what you understand is more valuable than expanding the territory you claim to know. When the agent’s defaults define the circle, every new workflow gets pulled back inside it. The denomination’s actual edge lives outside that circle, in the messy handoffs between volunteers who have never opened the app before. The product decision is whether to leave the model inside its comfort zone or to force it across the boundary on purpose.
Where the agent mandate stops short on volunteer orchestration
Volunteer orchestration is the workflow most teams test last because it looks simple on a flowchart. Assign curriculum, send reminder, mark complete. Fable 5 handles the first two steps inside its training distribution. It suggests standard email language, attaches the right PDF, and logs the assignment. The moment the volunteer replies with anything outside the script—“my kid has a fever and the printer is jammed”—the agent retreats to a safe, non-committal response or hands the thread back to a human.
I watched this exact failure on a children’s ministry rollout that served two hundred congregations. The agent could schedule the lesson but could not reroute the physical materials when a volunteer was suddenly unavailable. Completion rates dropped because the system kept treating the volunteer as a reliable node instead of a person whose availability changed daily. The safety layer had been tuned to avoid promising anything it could not guarantee, which is reasonable until the guarantee itself becomes the blocker.
The pattern repeats whenever the task requires real-time adaptation rather than pre-approved steps. The model’s circle of competence includes “send the lesson plan.” It does not include “decide whether the substitute volunteer can teach the same material with only a printed outline and ten minutes of prep.” That decision sits outside the training distribution, so the agent never offers it.
The prompt pattern that breaks the agent mandate safety layer
Anthropic’s own core views on AI safety describe why agent systems need human judgment at exactly these boundaries, and the agent mandate makes that responsibility yours.
The safety layer loosens when the prompt forces the model to declare its own uncertainty before it acts. Instead of asking the agent to generate the reminder email, you ask it to list every assumption it is making about the volunteer’s context and then rewrite the email once those assumptions are stated. The extra step is small in tokens but large in effect. It moves the output from the center of the circle toward the edge.
Teams that discover this pattern usually find it by accident. One product lead added the line “state the three facts about this volunteer you are least certain about” to every orchestration prompt. The agent began surfacing gaps the product team had never logged: the volunteer who only checks email on Sunday afternoons, the one whose printer only works at the church building, the substitute who has never taught without a co-leader. Those gaps became the actual product surface. The model was no longer optimizing for safe language; it was optimizing for explicit ignorance.
The same pattern works on curriculum adaptation. Ask the agent to generate the lesson for a mixed-age group, then immediately require it to name the single age range where the activity will fail. That second instruction pulls the output outside the conservative default and into the specific constraints of the room the volunteer actually walks into.
How the agent mandate shifts competence boundaries
Once the agent is allowed to produce the first draft of any artifact, the ownership question changes. The PM who treats the draft as a finished suggestion keeps the circle of competence exactly where Fable 5 drew it. The PM who treats the draft as raw material that must be stress-tested against one real volunteer’s constraints moves the boundary outward. The difference shows up in the revision log, not in the initial output.
At SermonCentral we learned this when we let the agent draft volunteer instructions for a new series. The first versions were polished and complete. They also assumed every volunteer would read the full document before arriving. When we forced the agent to rewrite after a volunteer read the draft aloud in real time and stumbled on the third paragraph, the instructions shortened, the steps reordered, and the completion rate rose. The model had not become more capable; the team had simply stopped accepting output that stayed inside its original circle.
The boundary keeps moving only if the team measures something the model cannot see. Volunteer completion rate after the first contact is one such measure. Time from assignment to first material request is another. Both sit outside the agent’s training data, so they remain useful signals long after the language inside the agent has been optimized.
Your Turn: Apply This Today
- Pick one existing Fable Agent workflow that touches volunteers and add the exact line “state the three facts about this volunteer you are least certain about” to the prompt; run it on the next five real assignments and note which facts the model consistently misses.
- Take the agent’s most recent draft for any volunteer-facing email or instruction set, read it aloud to one actual volunteer within 24 hours, and rewrite only the sentence that caused the first hesitation.
- Log the time between assignment and first material request for the next ten volunteer tasks; compare the numbers against the agent’s predicted timeline and mark every gap larger than two days.
- Replace the default “send reminder” step in one orchestration flow with a prompt that forces the agent to name the single constraint that would make the reminder useless, then adjust the send time accordingly.
- Choose one children’s ministry workflow and require the agent to generate both the main lesson and the single-age-range failure case before any output is shown to a human reviewer.
- At the end of this week, count how many of the six prompts above produced at least one output that the model originally refused or softened; keep only those revised prompts in the active library.
The same boundary problem shows up in how teams decide what counts as finished once AI writes the first draft; that pattern is laid out in The Months I Outsourced My Sense of What Counts as Finished. It also appears in the decision to keep human judgment visible rather than sprinting toward the next automated feature, which Trust Logs Beat the Next Feature Sprint examines in detail.
I consult with product leaders shipping AI features into volunteer and ministry workflows on prompt boundary testing, completion-rate instrumentation, and first-draft ownership. Let’s talk.