Agentic AI Capability

Two agents, one field: a rule decides, or a person does.

A field can hold one value. When one agent wants to raise it and another wants to lower it, arbitration takes both cases, measures the distance between them and settles the matter inside the band your team set.

TWO PROPOSALSONE FIELDTHE GAPTHE DECISIONSafety stockagentArbitrationExcess stockagentA named personRaise to 1,400 piecesdemand variability hasrisen since JulyLower to 900 piecescover runs at 11.4 weekstodayOne field is claimedtwicesafety stock for 7741-X atplant 1210The gap is measuredthe two proposals sit 500pieces apartInside the band,weights rankthe higher weight isapplied, and both are keptBeyond the band, aperson decidesJ. Ridley, with both caseson one screenshowcase estate · the band and the weights are settings your team holds
The same field, claimed by two agents. Inside the band the weights rank them; beyond it the amber path reaches a person. Showcase estate; both roles are designed in the agent blueprint, shown as they would run.
1
value a field can hold, which is why arbitration exists
product
15%
the band the showcase team set around the current value
showcase estate
3
things kept for every case: both proposals, the weights and the result
product
1
named person decides each case that falls beyond the band
product
Where this sits

Stage 5 of six: act

Step by step

How one contested field is settled

Five steps: claim, assemble, measure, rank or refer, record.

TWO PROPOSALS ON ONE FIELD, RESOLVED IN FIVE STEPS01One field isclaimed twicetwo agents propose changesto the same value02Both cases areassembledobjective, basis,confidence and value atstake03The gap ismeasuredthe distance between thetwo proposals, againstyour band04Inside the band,weights rankthe proposal with thehigher weight is applied05Beyond the band, aperson decidesboth cases reach a nameddesk, side by sidethe decision and the case that was set aside both return as evidence for the next cycle
Arbitration runs between evaluation and action, so a contested field is settled before anything is written.

Each run produces recommendations per agent. Before anything is carried out, the engine groups them by the field they would change: the safety stock of one material at one plant, the date on one schedule line, the open quantity on one order line.

Where one field carries two proposals, arbitration assembles both cases whole: the objective each agent serves, the conditions that matched, the confidence, the value at stake and the weight the agent carries for that field.

It then measures the gap. The gap is the distance between the two proposed values, read against the band your team set around the current value. A small gap is a matter of degree; a wide gap is a matter of judgement.

Inside the band the weights rank the two, the higher one is applied and the other is recorded as set aside. Beyond the band both cases go to the named person who owns that field, side by side on one screen.

The case

Two agents, two objectives, one value

Two agents can both be right; the field still holds one value.

Safety stock agentExcess stock agent
Objective it servesHold the agreed service level on this materialRelease working capital held as excess cover
What it readsDemand variability, lead time variability, service levelStock on hand, stock on order, forward demand
What it proposesRaise safety stock from 1,100 to 1,400 piecesLower safety stock from 1,100 to 900 pieces
Its basisDemand variability rose 34% since July; two late deliveries in AugustCover runs at 11.4 weeks against a policy of 8
Its confidence0.88, from 14 months of demand history0.91, from stock and demand read this morning
Its weight on this field0.62, set by the planning lead for class A materials0.55, set by the planning lead for class A materials
What it is worthService level held at 98% on a line worth $2.1M a year$46,000 of working capital released

One contested field in the showcase estate, between two designed roles from the agent blueprint, shown as they would argue it. Showcase estate. blueprint

Both cases stay whole. A person reading this table sees two sound arguments from two different objectives, which is what a contested field usually holds. Arbitration settles which one is applied today, and the record keeps the other so the next review can read it.

Bands and weights

The settings that decide how far a rule can take it

Four settings your team owns: the band, the weights, the floor and the cooling period.

SettingWhat it controlsWho sets itIn the showcase estate
The bandHow far apart two proposals may be before a person decidesThe owner of the field, per object and class15% of the current value for class A materials
The weightWhich objective ranks higher inside the bandThe owner of the field, per agent and classSafety stock 0.62 · excess stock 0.55 for class A
The floorThe lowest value a proposal may reach, whichever agent winsThe planning lead, per material or class800 pieces for 7741-X, set from the service agreement
The cooling periodHow long a field stays settled after a decisionThe owner of the field14 days, so a value settles before it is revisited

A band is a statement about judgement. Inside it the two agents differ by an amount your team is content to settle by rule; beyond it the difference is large enough that a person should see both cases.

Weights say which objective leads when the difference is small. A team protecting service sets the safety stock weight higher; a team releasing cash sets the excess weight higher.

Both settings carry a version history, so a change to a weight is as visible as a change to a rule. An auditor reading a decision sees the band and the weights that were in force that day.

A field that reaches arbitration repeatedly is worth a look. The manager report counts contested fields per agent and per period, which usually points at a policy that wants an edit.

When a person decides

Both cases, one screen, one reason recorded

Take one case, take the other, or set a value of your own; every route records a reason.

1
Both proposals reach the same fieldsafety stock for 7741-X at plant 1210, on the Monday run
08:02
2
The gap is measured500 pieces apart on a current value of 1,100, which is 45%
beyond the band
3
The case goes to the owner of the fieldthe planning lead named on the material policy
J. Ridley
4
Both cases are read side by sideobjectives, bases, confidences and what each is worth
09:40
5
J. Ridley sets the value at 1,250a value of their own, with the reason recorded
decided
6
Both agents read the decisionthe next run starts from 1,250 and the reason is on the record
applied

Beyond the band, the case goes to the person named on that field, with both proposals, both bases and both values at stake on one screen. The clock and the escalation route work as they do for any approval.

That person has three choices: take one of the two proposals, set a value of their own, or leave the current value in place. Each choice records a reason.

A value of their own is common, and useful. J. Ridley set 1,250 pieces, between the two proposals, and the reason went on the record beside both cases.

The learning loop reads that decision. Where a person settles the same contest the same way three times, Juno proposes a weight change or a rule edit for approval.

The running example

Monday 08:02: one field, two agents, one value written

Showcase estate. The safety stock and excess stock roles are designed, yet to be built; the scene shows how arbitration would settle them.

The running example

On the Monday run both agents reached the safety stock of 7741-X at plant 1210. The safety stock agent asked for 1,400 pieces after a rise in demand variability; the excess stock agent asked for 900, because cover was running at 11.4 weeks.

The gap was 500 pieces on a current value of 1,100, which is beyond the 15% band, so both cases went to J. Ridley. At 09:40 the value was set at 1,250 with the reason recorded. The cancellation agent carried on with the open lines, because that field was claimed once.

Next capability

Action flows: events, workflows, APIs, files

The five routes an approved action can travel, and how Juno hands work to the system that will carry it out.

Terms on this page
Contested fieldOne value that two agents propose to change in the same run.
ArbitrationThe step that settles a contested field by rule, or sends both cases to a named person.
BandHow far apart two proposals may be before a person decides.
WeightWhich objective ranks higher inside the band, set per agent and class.
FloorThe lowest value a proposal may reach, whichever agent wins.
Cooling periodHow long a field stays settled after a decision, before it is revisited.
Questions
What if three agents claim the same field?

They are ranked together. The widest gap is measured against the band, so a case that holds one outlying proposal reaches a person while the others settle by weight.

Is the losing proposal lost?

It is kept whole on the record, with its basis and its value at stake. The outcome check reads it later, and the manager report counts how often each agent is set aside.

Who owns the band and the weights?

The person who owns that field, usually the planning lead for a material class. Both settings carry a version history, and a change is visible to an auditor.

Does arbitration slow a run down?

It runs between evaluation and action on the fields that carry two proposals, which is a small share of a run. Everything claimed once carries on as usual.

In the platform

Where Juno sits among the four capabilities

Each one builds on the one before it.

One shared foundationCatalogLineageAccess policyWrite path

See Juno answer and act on your own data

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.