The decision
One decision, in the case chosen above: the act, its amount, and who takes it today. A person does this work now, trained, within an authority recorded in a system, with a second person above the limit or for the harder cases. And the firm has governed that delegation for years. Beside it sits a business case: how many of these a year, the minutes an agent saves on each, the share of the saving that reaches the accounts, and what it costs to run and to set up.
And a question for the room: would you let this agent decide on its own? Hold the answer. The slide comes back at the end.
The same boxes, for this decision
The map from part one, with this decision written into the workflow row: the agent that acts, the knowledge that applies to this case, the mandate, the check before the act, the record, and narrow or widen. The enterprise row and the platform row stay as they were. So a firm fills the workflow row per decision and reads the rest of the map unchanged.
Essential 1: the agent itself
Who is acting? A named agent, a specific release, validated before it went live, acting for a business unit under its own identity, and it can be stopped. The slide also shows how this essential goes wrong in good faith: a new release goes live without validation, an identity is shared with other agents, a stop is never tested. The firm approved the release, with the model inside it.
Essential 2: what it knows
What may it rely on, and does that apply to this case? The versions of the knowledge are listed with their dates, and one of them applies: the wording for this contract and policy period, the list in force when the payment goes, the guidance in force on the day of the decision. The slide shows the stale copy going wrong in good faith. The agent retrieves the newest document, which does not apply, and the decision is wrong by an amount the record will later have to explain.
Essential 3: what it may decide
The mandate for this decision, as an object with a version: owner, agent, action, level, limit, conditions, review trigger, revocation, challenger, the rule for restoring it, an expiry, and a deputy. Beside it, today with a person: the same authority as a role and a signing limit in a system. And the way it goes wrong: authority that lives in a prompt or a configuration file nobody owns, which no check can read and no challenger can hold.
Essential 4: at the act, one check reads six inputs
At the moment of the act, one check reads six inputs: the identity, the release, the basis, the mandate, the exact action, and the current state. The last one counts the deployment's limit for the day with the permits already in flight. So permitted acts cannot together breach a limit each of them respects. Then the check permits, refers to a person with the reason, or blocks.
Essential 4: the check, demonstrated
The scenarios, through the same check. All three hold, and the act goes through. The release was never approved. The controls are missing. The knowledge is stale. The act is outside the mandate. Each is shown without the checkpoint and through it, with a row for each input and the record line. So the room sees what the check read and what it answered. Click through them in the frame; the slide scales to the screen.
Essential 4: between the permit and the act
A permit is not the act, and the time between the two matters. The mandate narrows while the act waits. The facts change. The agent is stopped. The outcome is unknown. Each of the four sends the act back to the check, and a permit that outlives its mandate is void.
Essential 5: one record, every reader
One record, the second act's, the one the check referred, and the people who read it, each with a question of their own. The security officer asks who acted and whether it was contained. The platform asks which release and which route. Finance asks what it cost. The business owner asks what was decided and on what basis. The second line asks whether the mandate held. And compliance, or the legal office, asks whether the reasons can be given to the customer. Each gets an answer from the same record, and none of them needs the agent's own traces to get it.
Essential 6: the loop
The return path, animated. A dial between decide and recommend. A rule filling one referral at a time. And the dated events: the referrals, the narrowing on the rule the same day, the cause found where it lives, the clean decisions counted, the restore signed. The mandate moved on evidence, and nobody edited a prompt.
How much may the agent decide on its own?
The question from the start, again. Yes, as far as its mandate goes: granted by a named owner, checked before every act, recorded, and narrowed or restored on evidence. Part three opens each essential for the specialists. Part four turns the map to your firm.