Agentic AI Capability

Policies, plans and scope that Juno can rely on.

Some questions are about your data. Others are about your rules, your agents, or how far Juno’s knowledge reaches.

Policy questionread from the policy registerABC and XYZ classesSafety stock cover by classService levels by customerPlan questionread from the plan registerPO cancellation, rule version 3Expedite and de-expedite plansStock rebalance planScope questionread from what Juno knows23 registered tablesFive source systemsData territories in trainingData questionread from your systems in placeOpen purchase order linesStock and days of supplySupplier on-time deliveryA question arrivessorted in one stepshowcase estate · the plans beside PO cancellation belong to designed blueprint roles, shown as they would be registered
Four kinds of question, four places to answer them from. The entries shown are the showcase estate’s.
4
registers a question may be answered from
product
37
named policies in the showcase estate’s policy register
showcase estate
9
plans in the showcase plan register, shown as they would appear: one from the agent in production, the rest from designed roles
showcase estate
23
registered tables listed under what Juno knows
showcase estate
Where this sits

Stage 4 of six: teach

Step by step

How a question finds the register that answers it

The sort takes one step and decides which of four places holds the answer.

FROM A QUESTION TO THE ENTRY THAT ANSWERS IT01Read the questionthe words, the objects and theperiod02Sort itpolicy, plan, scope or data03Open the registerthe entry, its owner and itsversion04Answer and name theentrythe reader sees which entry wasusedan approved policy or a released plan joins its register at once
Sorting happens before any query is written, so a question about a rule is answered from the rule, and a question about data is answered from the data.

The first step of every answer is a sort. Juno reads the question and places it in one of four kinds. A question about what your company has decided is a policy question. A question about what an agent will do is a plan question. A question about coverage, sources or scope is a scope question. Everything else is a data question.

The sort matters because the four kinds have four different right answers. A question about your safety stock rule is answered by quoting the rule and its version, and a query over stock tables would give a number that misses the point.

Each register entry carries a name, a plain-language statement, an owner and a version. The answer quotes the entry and names it, so the reader can go to the owner and check. Entries stay in the append-only version history, so an answer given last month stays explainable.

Data questions leave the registers and go to your systems. The registers still shape the answer, because the policy and the plan supply the thresholds, the classes and the windows the query uses.

The four registers

What each register holds, and who owns it

Four registers, one shape: a name, a plain sentence, an owner and a version.

Policies

Your named business policies in plain language: classes, cover, service levels, approval limits.

Plans

The published planning tables of your agents, each with the rule version it runs today.

What Juno knows

The registered sources, tables and mapped columns, and how far the mapping reaches.

Data territories

The subject areas training has covered, so a reader can see where answers are strongest.

RegisterEntryWhat the entry statesOwnerVersion
PoliciesABC and XYZ classesA items carry the top 80% of annual value; X items have steady demandJ. Ridleyv2 · 12 Aug
PoliciesSafety stock coverAX items hold three weeks of cover at plant 1210; CZ items hold one weekL. Tanv5 · 2 Sep
PoliciesService levelsNorthbay Logistics holds a 98% line fill; Helvetia Retail AG holds 95%J. Ridleyv1 · 4 Jul
PlansPO cancellationCancel lines with excess above eight weeks, inside the window, under $25,000L. Tanv3 · 18 Sep
PlansExpeditePull in lines where the shortage lands inside the lead-time fenceL. Tanv2 · 11 Sep
What Juno knowsRegistered scope23 tables from five systems, 412 columns mapped: 371 proposed, 338 confirmedA. Novakv7 · 19 Sep
Data territoriesPurchasingPurchase orders, schedule lines, suppliers and supplier confirmationsA. Novakv3 · 18 Sep

Seven entries of the showcase estate’s registers. The expedite plan belongs to a designed role from the agent blueprint, shown as it would be registered. Showcase estate. blueprint

Which register answers which question

Six questions from the showcase estate, sorted

Each answer states the place it came from, so a disagreement has an address.

Policy
What is our safety stock rule for A items at plant 1210?policy register · safety stock cover v5 · owner L. Tan
Plan
What will the cancellation agent do with a line worth $40,000?plan register · PO cancellation v3 · drafts it and asks D. Okafor as buyer
Scope
Which systems do you read for supplier information?what Juno knows · SAP, Oracle Fusion and the supplier portal
Data
How many open PO lines can we still cancel this week?your systems, read in place · 38 lines · $412,000 on Monday 21 September
Policy
Which customers hold a 98% line fill?policy register · service levels v1 · owner J. Ridley
Data
What is the excess above eight weeks of demand at plant 1210?your systems, read in place · grouped by material

The sort is shown to the reader. An answer from a register says which entry it quotes and who owns it; an answer from your data shows the terms, the systems and the query. A reader who disagrees with an answer therefore knows exactly where to go: to the owner of an entry, or to the mapping behind a column.

Where the entries come from

Each register fills from the work your team already does

The registers hold statements; your systems hold the rows.

Policies are written by their ownersA planner or a director states the policy in plain language and publishes it with a version.
Plans arrive on releaseWhen an agent is released, its planning table joins the plan register with the rule version it runs.
Scope fills from registrationEach registered source, table and confirmed mapping updates what Juno knows about your estate.
Territories fill from trainingEach training run records the subject areas it covered, so coverage is visible.
Versions accumulateEvery entry keeps an append-only history; restoring an earlier entry creates a new version.

A register entry is therefore a by-product of work that already happens: writing a policy, releasing an agent, registering a source, running training. The registers turn that work into something a question can reach.

When a question falls outside the entries a register holds, Juno says which register it read and who owns it, and offers the nearest entry it has. Those questions collect in a list your owners review, so the gap is visible and someone can close it.

Analysts ask about this directly, because it is the difference between an answer that rests on an approved statement and an answer assembled on the spot.

Why grounding raises accuracy

Gartner, 17 June 2025: organisations that prioritise semantics in AI-ready data will raise the accuracy of generative AI models by up to 80% and cut cost by up to 60% by 2027.

The running example

Friday 11:20: a question about the rule, answered from the rule

Showcase estate.

The running example

With the cancellation policy released at supervised level, D. Okafor asked what the agent would do with a line worth $40,000. That is a plan question. Juno quoted the published planning table of rule version 4: lines of $25,000 and above are drafted and passed to the buyer.

J. Harrison then asked which customers hold a 98% line fill. That is a policy question, answered from service levels v1 with J. Ridley named as its owner. A third question, about excess above eight weeks of demand, went to the data and came back in 4.2 s with the query on show.

Next capability

Question paths and walkthroughs

Save a line of questions as a walkthrough, share it with the team, and schedule it as a weekly digest.

Terms on this page
Grounding registerA named list Juno reads before answering, so the answer rests on an approved entry.
Policy registerYour named business policies in plain language, each with an owner and a version.
Plan registerThe published planning tables of your released agents, with the rule version each one runs.
What Juno knowsThe record of your registered sources, tables, mapped columns and their scope.
Data territoryA subject area training has covered, listed so readers can see where answers are strongest.
Question classificationThe first step of an answer, which sorts a question into policy, plan, scope or data.
Questions
Where do register entries come from?

Policies are written by their owners. Plans arrive from the rules engine when an agent is released. Registration and sync scans fill what Juno knows, and each training run updates the data territories.

What happens when a question falls outside the registers?

Juno states which register it read and who owns it, and offers the nearest entry it holds. The question joins a list your owners review, so the gap stays visible.

Can a policy in the register drive an agent?

A policy states intent in plain language. The Planner Agent turns it into a reviewable planning table, and the rules engine executes that table. The planner agent page shows the step.

Who approves a register entry?

The named owner of the entry. Every version keeps the owner, the date and the change, and restoring an earlier version creates a new version on top.

Do the registers hold our data?

The registers hold statements and scope: policies, plans, sources and subject areas. Your rows stay in your systems and are read in place when a data question arrives.

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.