Part 3 — gated agent practice. Part 1 is click-and-do pedagogy: Click-and-Do Before Slide Decks. Part 2 is role-fit on the analysis path: Role Paths Before Generic Analytics.
Everyone wants to skip the 80%. I did too. And I paid for those mistakes myself.
The pitch is always the same. One agent, one goal, full autonomy: emails, outreach, research, strategy, marketing, video, follow-ups, reporting. It sounds great until you try to build it. Then the uncomfortable part shows up. You cannot automate a process you do not understand. If the workflow lives in someone’s head, if the rules are implicit, if exceptions are handled “by experience,” the agent has nothing reliable to operate on.
On 2026-08-13, promptanatomy.app soft-launched Modules 10–12, the Agent path, for a limited tester cohort among existing buyers. For how blog vs training fit, start with The Prompt Anatomy Ecosystem Map.
Three bands before a build
Before AI can run a process, you need the process in detail. What triggers it? What information is required? Which decisions get made? Where are the exceptions? What can go wrong? When does a human need to step in?
That changes the order. The figure’s 80 / 15 / 5 split is a planning heuristic, not a measured mix and not an ROI claim. Autonomy is not the starting point. It is the last step.
3A is a portfolio mix, not a promotion ladder. You assign each process a band before anyone builds. That is a different axis from the five-stage path in From Prompt to Agent—control maturity there, mix of work here.
| Band | When it fits | Typical miss |
|---|---|---|
| Automate | Rules fire without a judgment call. Spine is trigger, then condition if needed, then action. | Wrapping a form-to-CRM flow in an “agent” because the vendor used the word |
| Assist | A human decides; the model drafts, classifies, or summarizes. | The draft reaches the customer with no confirm step |
| Autonomize | A bounded agent with escalation and an audit trail. Narrow by default. | Autonomize as the default because it sounds mature |
The stealable move takes ten minutes. Write three of your processes. Assign a band to each. If all three land on Autonomize, that is hype, not a plan.
A webhook is a type of trigger, not a fourth step. A router splits work by type. An orchestrator (coordinator) splits the job, delegates, and joins results. Mixing those labels is how you get three “agents” and no owner. Human approval is risk architecture: consequence times whether you can reverse the action—not a badge that you are “not mature yet.” Bounded tasks, allowed tools, and escalation still live in How to Design an AI Agent Workflow. The lesson host on .app assembles practice; ChatGPT, Claude, or Gemini execute. That wedge is The Model Is Not the System.
The Northline jump
Northline’s enablement lead (composite) shipped a “support agent” in a week. It was Autonomize with no Assist gate. A concession email went to a customer with a fabricated credit. The same flow as Assist would have been: draft, named human confirms, then send. The label was not the failure; skipping the band was. That maps to 10 Signs Your Company Is Vibe Prompting when a product name replaces a control.
Who can test M10-12
We are recruiting a limited tester cohort while we close remaining bugs, check tools and schemas, and finish design polish. Soft launch is not a promise that every interactive schema passed full manual QA. The path stays gated so we can watch real buyers work trigger-condition-action and human-approval drills before Corporate checkout exists.
Who: Existing Core buyers with Modules 1–6 on promptanatomy.app. M7–9 helps; it is not required. Starter (Modules 1–3) is out until Core.
Offer: Free M10–12 access during the soft-launch window. This is a tester grant, not a public price change. Pilot training from 399 EUR is the forthcoming Corporate list price when that checkout opens—not what is live today.
Apply: Email info@promptanatomy.app with subject M10-12 tester, your purchase email, and LT or EN.
Ask: Work the path within 30 days. Reply with three bullets—what confused you, what worked, one bug or typo—plus one sentence: which process you put on Autonomize and why it is not Assist. Feedback shapes the general-availability cut; it does not replace support SLAs.
Guardrails
Treat .app progress as practice, not a production agent:
- A finished Agent path or certificate does not replace a workflow ID, RACI, eval gate, or runtime you own.
- Do not paste training copy into procurement decks.
- Plans stay on promptanatomy.app/#pricing.
