At every level a person is in the picture. This chapter shows what that person does: the four patterns of working with an agent, the screens each person sees, the nine settings that shape every agent and who owns each, and the feedback loop in which every approve, edit and reject teaches the next cycle.
What passes between the agent and the person is different at each level, and so is the screen.
The ladder gave each level a definition. Read from the person’s chair, the four levels where an agent runs are four patterns of working together, and each is named by what passes between the two. At A0 the work stays with people and ChatLima answers their questions, as J. Harrison’s credit hold showed in the last chapter.
The agent informs; the person decides and acts. What passes: a ranked list with its evidence. As designed, the shortage agent ranks Monday’s shortages by revenue at risk and L. Tan decides who gets the parts.
The agent decides and drafts; a named person approves each action. What passes: a draft with its basis and its confidence, then the go-ahead. The PO cancellation agent drafts 29 cancellations and D. Okafor approves each one.
The agent executes within versioned rules; the person handles exceptions only. What passes: the exceptions, each with its reason. As designed, the baseline forecasting agent refreshes stable SKUs inside its error band and L. Tan takes the SKUs that breach it.
The agent executes and self-corrects; the person audits after the fact. What passes: the record of every action, read as a sample. As designed, the cash application agent matches, re-tries and re-routes, and J. Harrison audits a sample each week.
Three of the four scenes are designed roles from the agent blueprint, yet to be built. The A2 scene is the PO cancellation agent, which runs in production at a high-tech manufacturer. blueprintproduction
Read the two columns together and the handoff is the whole relationship: the agent hands over a draft it can explain, and the person hands back a decision with a name on it. The rest of this chapter is about what the person sees and sets on each side of that line.
The buyer approves, then handles exceptions only; the finance lead reads one record; the director reads the report.
| Line | What the agent drafted, and why | Value | Confidence | Decision |
|---|---|---|---|---|
| 4500067123 · 00020 | Cancel 200 of 7741-X at plant 1210 excess 11.4 weeks · window open to Thu 24 Sep · supplier class standard | $8,420 | 91% | Approved as drafted · 09:12 |
| 4500068004 · 00020 | Cancel 1,200 of 8802-K at plant 1210 excess 9.3 weeks · window open to Wed 23 Sep · supplier class standard | $24,100 | 93% | Approved as drafted · 08:58 |
| 4500067990 · 00030 | Cancel 300 of 5513-B at plant 1220 excess 8.6 weeks · window open to Thu 24 Sep · supplier class standard | $7,160 | 88% | Edited to 200 · approved 09:03 |
| 4500068110 · 00010 | Cancel 150 of 9021-M at plant 1220 excess 12.1 weeks · window open to Fri 25 Sep · supplier class standard | $5,900 | 90% | Approved as drafted · 09:05 |
| 4500068221 · 00050 | Cancel 80 of 4410-T at plant 1210 excess 10.2 weeks · window open to Thu 24 Sep · supplier class standard | $2,280 | 90% | Approved as drafted · 09:10 |
Each row carries the action, the basis in the words of the policy, the confidence and the value at stake. The three decisions are approve, edit and reject with a reason. Showcase estate.
| Line | Why it reached a person | What the agent did | For the person |
|---|---|---|---|
| 4500069310 · 00010 | Value $31,600, above the $25,000 threshold | Drafted the cancellation and sent it to D. Okafor as buyer, with the reason | Buyer · D. Okafor · approve · edit · reject |
| 4500069402 · 00030 | Confidence 0.76, under the 0.80 floor: two systems report the supplier class differently | Paused the run on this line, reported both readings and told the owner | Owner · L. Tan · choose which reading to trust |
| 4500069188 · 00020 | The write-back returned an error: the line is blocked in SAP | Held the change and sent it to the owner with the message | Owner · L. Tan · clear the block |
At A3 the queue holds only what a limit or a thin finding handed over, each with the reason. Everything else was executed inside the rules, written back and confirmed. Showcase estate.
| Part | What the record holds |
|---|---|
| Signal | 06:00 run · exception message for 7741-X at plant 1210 · 38 open lines read from SAP S/4HANA and Oracle Fusion |
| Reasoning | Policy version 3 · three conditions matched: excess 11.4 weeks, window open to Thu 24 Sep, supplier class standard |
| Recommendation | 06:06 · cancel 200 of 7741-X, the open quantity on line 00020 of order 4500067123 · $8,420 · confidence 0.91 |
| Limits checked | Value under $25,000 · daily budget 29 of 60 · confidence floor 0.80 · all passed |
| Approval | D. Okafor · approved as drafted · 09:12, after 3 h 06 min in the queue · role and session recorded |
| Action | Purchase order change posted to SAP S/4HANA through its released interface |
| Acknowledgement | Message 20260921-114, stored as returned |
| Outcome | Day 14: projected cover 6.2 weeks against 11.4 · verdict met |
| Measure | Six weeks | Per 1,000 decisions |
|---|---|---|
| Drafts produced (decisions) | 212 | 1,000 |
| Approved as written | 203 | 958 |
| Edited, then approved | 9 | 42 |
| Rejected | 0 | 0 |
| Overridden | 0 | 0 |
| Exceptions handed to a person at A2, a line above the value threshold, sent to D. Okafor as buyer | 66 | 311 |
| Write-backs confirmed by the ERP | 212 | 1,000 |
| Line the team set for a move to A3 | 95% approved as written, held four consecutive weeks | met · weeks 3 to 6 |
The audit view holds the eight parts of one decision, the record chapter 5 reads in full. The manager report counts one agent over six weeks; each agent built later from the blueprint would be counted the same way. An exception at A2 is a line above the value threshold, which reaches D. Okafor as buyer with the reason. Showcase estate.
Each screen is a SmartApp over the same decision records, cut for one person. The buyer’s queue ranks drafts by value and time left, with a clock per queue and a named next desk when the clock runs out. The auditor opens one record by its reference; the director reads counts per 1,000 decisions, so agents of different sizes would compare once more than one is built.
The screens differ; the record behind them is one. The draft D. Okafor approved at 09:12 is the record J. Harrison opens by its reference and one of the 212 decisions J. Ridley counts. That is what lets a level review rest on evidence.
Seven are the parts you met in chapter 2; the level and the feedback decide how much the agent may do and how it improves.
Seven of the nine you met in chapter 2 as parts of the agent: objective, data scope, rules, trigger, actions, limits and escalation. The eighth part, the tests, is how a change to any of them is proved before it takes effect: a simulation on last quarter for a rule, a test on recorded cases for a level. The level and the feedback turn the parts into a working relationship.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Cancel purchase order lines that stand above the need, inside their cancellation window | The planner, in a sentence | New version |
| Data scope | Purchase order lines, schedule lines, demand, stock and supplier class at plants 1210 and 1220 | The data lead | New version |
| Rules | The policy sentence and its planning table, version 3 | The planner with the Planner Agent | New version, simulated first |
| Trigger | 06:00 each working day, after the planning run | The planner | At once |
| Actions permitted | Draft a cancellation · send a change · open a query to the buyer | The owner | New version |
| Limits | Value threshold $25,000 · daily action budget 60 · confidence floor 0.80 | L. Tan and J. Harrison, finance | New version |
| Escalation | Above the threshold, to D. Okafor as buyer, with the reason · a failed write-back, to the owner, L. Tan · a limit breach pauses the run and tells the owner | The owner | At once |
| Level | A2 Supervised with D. Okafor as the named approver | The manager, J. Ridley | Up on evidence, down in one step |
| Feedback | Every approve, edit and reject is recorded and used | Always on | Fixed |
The nine elements as they stand on the PO cancellation agent after the Friday release. The last column says when a change takes effect. Showcase estate.
Three owners, three kinds of change. The planner and the data lead change what the agent knows and looks for; the owner and finance change what it may do and how far; the manager changes how much of the work it carries. Each is a version, simulated or tested first. Only the trigger and the escalation route change at once, because they move the work and leave the decision alone.
A correction is recorded with the facts of the moment, and the next version of the rule is built from the corrections that repeat.
A correction records both values: what the agent drafted and what the person sent, with the reason the person chose from a list and the facts as they stood at 06:00. A reason chosen from a list teaches faster than one typed by hand, because the same reason can be counted across decisions.
This is where the fourth cause from chapter 1 is answered. Corrections that live in an inbox are lost to the next cycle; corrections on the record are read by it. A buyer approving 40 drafts a day leaves 40 signals a day, and sees better drafts each week.
One of the 9 edits in six weeks, as the record holds it. Showcase estate.
Over six weeks the agent drafted 212 cancellations. D. Okafor approved 203 as written and edited 9, which is 96% approved as written, and those 9 edits are the signals the next version reads. Rule discovery also reads what buyers did before the agent existed: they had kept every line for one allocation-bound supplier, so Juno proposed an exclusion and j.park approved it as version 4. MIT NANDA, July 2025: 95% of pilots show a profit effect too small to measure, and the tools that retain feedback do better.
A limit carries the name of the team that set it, and the agent checks all of them before every action.
| Limit | Set by | What it does on this agent | On the Monday |
|---|---|---|---|
| Value threshold · $25,000 | Finance · J. Harrison, with the owner | A line of $25,000 and above goes to D. Okafor as buyer, with the reason; at A2 a named person approves every line either way | 9 of 38 lines |
| Daily action budget · 60 | Operations · the owner | Caps the changes the agent may send in one day; at the cap the run pauses and the owner is told | 29 of 60 used |
| Confidence floor · 0.80 | Operations · the owner | A finding under the floor pauses the run on that line and reaches the owner with both readings; the recommendation stays empty | every draft sat above it |
| Two-person rule · bank details | Finance · J. Harrison | A change to bank details or payment terms waits for two named people, on any agent whose actions can reach those fields | this agent’s actions leave those fields untouched |
Four limits on one agent, and the team that owns each. Showcase estate.
The threshold decides who sees a line first, and at A2 a named person approves every line either way. Finance co-owns it with L. Tan because it is a statement about money at risk. J. Harrison moves it with her as a new version, simulated first, while the rules and the trigger stay exactly as L. Tan set them.
The two-person rule runs the other way. Finance sets it once and it applies to every agent whose permitted actions could reach a supplier’s bank details or payment terms. The cancellation agent’s three actions leave those fields untouched, so the rule waits, and it would apply the day such an action were added.
Each element has one owner, named on the panel: finance for the value limits, the manager for the level, the owner for actions and escalation. A change is a new version with a name and a reason, on the record.
The 29 took 22 minutes on the Monday, because the reason and the facts sat on each row. The work they replaced was the day of assembling that evidence by hand, which chapter 1 counted inside the 2.5 days.
A named colleague receives the queue as cover, each item keeps its clock, and when a clock runs out the escalation route sends the item to the next desk. Both names go on the record.
Yes. An override is a signal like an edit, recorded with its reason. A run of overrides is also the evidence that brings a level down one step, at once, by the owner or the manager.
Settings are only worth having if turning them into a working agent is fast. How long does it take to make one?
From one sentence in plain language to a released agent on a Friday, and what happened on the Monday after.
Each one builds on the one before it.
Reads your rows in place.
Connect and move ↗One record per real thing.
Master and govern ↗Apps for every decision.
Operate and decide ↗Asks and acts, at your level.
Ask and act ↗Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.