Follow a single invoice through an agentic process. Every shape below comes straight from the APMN canvas — by the last chapter, you can read any model in the app.
WORK IN PROGRESS — new chapters added as the notation growsA supplier's invoice lands in the finance inbox. That moment — not a meeting, not a form — is what wakes the process up. The document itself joins the drawing too.
THE SHAPES → Start / Trigger · Input Artifact
"Read the invoice" is a single job, so it gets a single box. The AI that extracts the details works inside that box — a helper, not a separate step in the business story.
THE SHAPES → Work Unit · LLM Call · dashed line = "uses a helper"
Is this vendor real? Does the order match? The finance system answers, and everything learned so far is written down where the next steps can see it.
THE SHAPES → Tool Call · State Object · dashed line = information moving
The amount is higher than usual. Instead of deciding quietly, the process asks its question out loud — and the company's payment policy stands right beside it. A sticky note keeps the context honest.
THE SHAPES → Decision / Router · Guardrail · Text Note · every road out gets a name
Because money is involved, the invoice takes the "needs a look" road. Maya checks the details a person should check; her manager gives the formal yes. Judgment first, then accountability.
THE SHAPES → Human Review · Human Approval · drawn where the risk actually lives
Twelve minutes, one human check, zero mystery. The invoice is approved, and the audit trail remembers who did what, when — so nobody has to reconstruct it in a meeting six months from now.
THE SHAPES → End / Output · Audit Log · dashed olive line = proof captured
Chapter seven is still being written. The invoice's story will grow as the notation does — these shapes are already on the drawing board:
Open the canvas and model the process you know best — or tell us which scene this guide still needs.