Every agent in Lima Juno carries one setting: its autonomy level, from A0 to A4.
Five sentences say how one piece of work is shared between an agent and a person.
The two middle columns together are the definition. Each example is a designed role from the blueprint, told as a scene below. blueprint
The last chapter left two of an agent’s eight parts open: limits, how far an action may go, and escalation, where a case goes when it passes them. Both depend on how much the agent may do alone. The ladder answers that in five levels, set on each agent by name, with a date.
The ladder converts 'how much AI' from an open-ended technology question into a per-agent governance setting the client controls, agent by agent.
Unclear limits were one of the four reasons earlier AI stalled; a level with an owner and a date is that limit made explicit, one agent at a time.
Five blueprint roles across finance, purchasing and planning, so the range shows on work you recognise.
Credit hold / release decision · Order-to-Cash · A0 Human-led J. Harrison, finance lead, has Helvetia Retail AG on her list. She asks ChatLima for the overdue balance, the open orders a hold would stop and the payment history. The answer arrives in seconds from three systems, with the query on show: $312,000 overdue at 31 days, a promise broken last Tuesday, three open orders worth $448,000, 47 of the last 48 months paid on time.
She decides that the Thursday shipment holds until the customer’s payment run clears, and records it in SAP S/4HANA under her name. A released hold is a credit decision with a signature, so the step sits at A0; the platform’s part is the facts.
Shortage & allocation negotiation · Procure-to-Pay · A1 Assisted As designed, the shortage agent reads the 1,240 exception messages L. Tan opened at 07:40, finds the 14 shortages that bite this week and ranks them by revenue at risk, $1.1M in all, showing the sales orders each one hits. First is material 7741-X at plant 1210: 600 units short against Helvetia Retail AG’s order, with Acme Components GmbH confirming 400 for Wednesday.
L. Tan decides who gets the parts: Helvetia Retail AG takes the 400, Northbay Logistics’ smaller line moves a week, and D. Okafor calls the supplier about the rest. She makes the allocation change in the planning suite herself. Her screen is the ranked list, one row per shortage; the agent’s work ends there.
PO change & cancellation · Procure-to-Pay · A2 Supervised At 06:00 the cancellation agent ran on policy version 3, the sentence L. Tan wrote on the Friday: excess above eight weeks of demand, inside the cancellation window, under $25,000, supplier class standard; at $25,000 and above, ask the buyer. 38 lines matched, worth $412,000.
29 drafts worth $187,300 reached D. Okafor’s approval queue, each with its basis and a confidence; the 9 lines of $25,000 and above reached him flagged for his judgement, with the reason. By 09:12 he had cleared the queue: 22 minutes, approve, edit, or reject with a reason, line by line. The ERP confirmed each write-back in 9 minutes. The blueprint designs this role at A3; the showcase estate started it at A2.
Statistical baseline forecasting · Plan-to-Produce · A3 Delegated As designed, the forecasting agent scores 4,800 item-locations overnight against version 2 of its rules. For 4,737 the refreshed statistical line sits inside the error band versioned with the rule, so the agent writes the new baseline to the planning suite and keeps each job status. 63 breach the band and go to L. Tan’s exception queue.
For material 7741-X at plant 1210 the last three overrides raised the line by 18% and actuals came in below it each time, so the agent proposes to withdraw the October override. L. Tan works the 63: 58 accepted, 3 edited, 2 rejected with a reason. Her screen is the exception queue, one row per breach: the band, the miss, the proposed correction.
Cash application & matching · Order-to-Cash · A4 Autonomous As designed, the cash application agent takes the overnight remittance: Northbay Logistics has paid $184,300 against 14 invoices and the remittance arrives as a PDF. On the first pass the agent matches 12 invoices, applies a 2% discount inside terms and posts the receipt in SAP S/4HANA; the document number goes on the record.
On the second pass it re-reads the PDF against the customer’s payables portal: the $6,200 line carries a freight claim number, so it becomes a case on the deductions desk; the $410 line sits inside the write-off tolerance and goes to J. Harrison for the write-off decision. On Friday she audits a sample, 20 of the week’s 340 postings, from their records. ‘Self-corrects’ means the second pass and the re-route; the audit stays hers.
Showcase estate throughout. The A2 scene ran on the Monday and is the running example of chapter 1. The A1, A3 and A4 scenes are told as designed, on the same estate and people, for roles yet to be built; the A0 scene is a human decision helped by ChatLima.
At A0 the platform helps by answering, and the decision stays human on purpose. At A4 ‘self-corrects’ means a second pass and a re-route, and the person still audits. Between them the handoff changes shape at every step; the record underneath stays the same.
The map proposes a starting level for every role; the setting on a built agent is yours.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was. The five scenes above are roles on that map.
One of the five runs: the PO cancellation agent is in production at a high-tech manufacturer, where planners author the policy in plain language, the rules engine executes it on federated ERP data, write-back waits for human approval, 100% of actions trace to a rule and run time costs zero tokens. The other four are designed, yet to be built. production
The blueprint’s proposed start for its 960 designed roles: 866, or 90%, keep a person in or on the loop at A1 to A3. Your settings replace these agent by agent. blueprint
Evidence first, then a name, then the route for the cases the agent hands back.
Raising a level takes three things together: a passing test on recorded cases, a named owner’s approval and a live escalation route. The test runs the agent again over cases that already happened and sets its drafts beside what the person did.
After six weeks the record read 212 drafted, 203 as written, 9 edited: 96%. The line J. Ridley had set for a move to A3 was 95% approved as written, held for four consecutive weeks, and weeks 3 to 6 held it. Lines under $25,000 moved to A3, where D. Okafor handles the exceptions only; lines of $25,000 and above stay at A2.
The quick way down is what makes the way up safe to take.
Lowering is deliberately lighter. The owner or a manager sets the lower level in one step, it applies from the next run, and the reason is recorded with the change. The agent keeps working at the lower level while the cause is looked at.
| What prompts it | Who acts | What happens next |
|---|---|---|
| A run of edits or rejections | The owner, L. Tan | Down one step; each action waits for an approver again. |
| A source change or a new policy | The data lead with the owner | Down one step while the rule is re-simulated and released as a new version. |
| A period close or an audit | The manager | The agent informs for the period; the level returns when it ends. |
The level moves the decision; the controls around the decision stay in place.
These six hold at A1 as firmly as at A4. The level changes who acts on a finding; the controls around the finding stay in place, so an agent at A4 leaves the same record a buyer would have approved at A2.
One row per level, so an analyst can place Juno on the ladder they already use.
| Juno level | Knight Institute user role | AWS agency scope | Driving automation analogy |
|---|---|---|---|
| A0 · Human-led | The role list starts above this rung | The scope list starts above this rung | The driver does all of it. |
| A1 · Assisted | Operator and collaborator | Scope 1 · the person keeps the agency | Driver assistance: the car warns, the driver steers. |
| A2 · Supervised | Consultant, moving to approver | Scope 2 · prescribed agency | Partial automation: hands ready on the wheel. |
| A3 · Delegated | Approver | Scope 3 · supervised agency | Conditional automation: the car drives and asks the driver to take over. |
| A4 · Autonomous | Observer | Scope 4 · full agency | High automation: the car drives, and the trip is reviewed afterwards. |
Crosswalk checked 19 September 2026; published level numbers are written out in words.
Four things are Lima’s own: a rung for the work that stays with people, so coverage is reported honestly; a named approver at A2; versioned rules at A3; and a setting that sits on the agent, in your hands. The rest is deliberately familiar.
Lima’s earlier data-quality pages describe autonomy in four short steps: the first lines up with A1, the second and third with A2, the fourth with A3. A4 adds self-correction, with the audit after the fact.
Most first agents start at A2, where the agent drafts and a named person approves each action. Those approvals build the record that supports a later move to A3.
Yes. The level sits on the agent. One company can run credit decisions at A0, cancellations at A2 and cash matching at A4 on the same day, each with its own owner.
A place on the map for work people keep on purpose, so coverage is reported honestly. The platform still helps there: ChatLima answers the questions the decision needs, in seconds.
At every level a person is in the picture. What exactly does that person see, decide and set?
The four ways people and agents work together, the screens each person sees, and the nine settings that shape every agent.
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.