Juno’s agent blueprint is a design of 960 agent roles across five end-to-end chains: the map of what Juno can be configured to do, built one role at a time, the way the PO cancellation agent was.
Five steps, the same for every role, so oversight is learned once.
An agent starts when something happens: the clock reaches a set time, an interval elapses, a row changes in a source, or a person runs it. It then gathers the facts it needs, reading the mapped tables through the federated query engine, so the rows stay in the systems that own them.
The Lima Rules Engine evaluates the published rules against those facts. The same facts and the same rule version give the same result on every run.
Where a rule matches, the agent records a finding. Where the evidence supports it, the finding carries a recommendation with a basis, a confidence and the value at stake.
What happens next follows the level you set. At A1 the agent informs a person; at A2 a named person approves its draft; at A3 it executes inside your limits and routes exceptions to a person. Every path ends in one record: rule, version, facts, decision and outcome.
Each card names the signal, the calculation and the action a role is designed for, so a reviewer can judge scope in one reading.
In production. Cancels purchase order lines that stand above the need, inside their cancellation window, under a named approver.
Designed role. It would keep the cover on each material in step with how demand and lead times behave.
Designed role. It would pull supply in where a requirement falls short and the supplier can hold the date.
Designed role. It would push supply out where it lands well ahead of the demand behind it.
Designed role. It would turn a morning of exception messages into a ranked list a planner works through.
Designed role. It would find stock and open supply that run ahead of forward demand.
Designed role. It would report where a planned delivery time has drifted away from real supplier behaviour.
Designed role. It would keep one scorecard of supplier delivery performance across every system.
Designed role. It would cover a shortage at one site from surplus at another, when it earns its cost.
Designed role. It would split constrained supply across customers and channels by your policy.
The PO cancellation card is the agent in production. The other nine cards are roles designed in the agent blueprint, yet to be built; each states what the role would watch, work out and do once it is built from the same parts. productionblueprint
The level travels with the agent and its version history, so an auditor sees what was allowed and when.
The blueprint designs eight of the ten roles to start at A2 supervised, and shortage triage, lead time drift and supplier on-time delivery to start at A1 assisted, where the agent reports and the person acts. These are designed starting levels. The level is a setting on the agent, and it is yours to move once a role is built.
Raising a level takes three things: a passing test on recorded cases, the named owner’s approval, and a live escalation route. Lowering a level takes one step and applies at once.
Market practice supports the cautious start. Capgemini found trust in fully autonomous agents fell from 43% to 27% in a year (Capgemini, 16 July 2025), and a KPMG pulse survey reports 61% of organisations requiring approval processes for agent actions (KPMG, Q2 2026).
The autonomy ladder explains all five levels, and the use cases chapter shows the whole blueprint of 960 designed roles in the same frame. blueprint
Showcase estate. The shortage triage and excess stock roles are designed, yet to be built.
L. Tan opens 1,240 exception messages; 212 of them touch an open purchase order line. The PO cancellation agent, the one role on this page that runs, takes those lines, applies the cancellation policy, and finds 38 lines worth $412,000 above the need with a window that closes on Thursday.
D. Okafor approves the drafts in the queue. After six weeks and 212 drafts, 203 approved as written and 9 edited, lines under $25,000 moved to A3 and D. Okafor sees exceptions only on those. A shortage triage role, once built from the blueprint, would rank the morning’s messages before she opened them; an excess stock role would confirm that the same materials carry more than eight weeks of cover.
How a policy stated in plain language becomes a planning table your team reviews, edits, simulates and publishes.
Yes. A role’s rules are yours to write and edit in plain language and in the rule builder. The blueprint’s design is the starting point, and every edit becomes a new version.
Yes, the same way: state the intent, review the plan the Planner Agent drafts, simulate it and publish it. The agent blueprint holds 960 designed roles to start from, and a role of your own is built from the same parts.
They are built one at a time. Start with the one that saves money on open orders, which is the agent that runs today, and add the role that ranks the morning work next; the rest follow at your pace.
Arbitration ranks the competing recommendations inside a band you set; beyond the band a named person decides. The arbitration page works a case through.
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.