Agentic AI Capability

Save a line of questions as a walkthrough for the weekly review.

Most reviews ask the same questions every week. A question path is that line of questions, saved: the order, the way each answer is presented and the period or plant to fill in.

THE PATH, SAVED ONCEsaved from a conversationWhich materials are short this weekplant 1210, by dayWhich orders cover the shortagepurchase orders and production ordersWhich suppliers are late on themconfirmed date against the need dateWhat can be pulled inlines inside the lead-time fenceWhat expediting would costby line and in totalWHAT ONE RUN PRODUCESevery answer under the reader’s own accessThe walkthrough screeneach answer with its query on showA digest by e-mailMonday 07:00, to the planning deskA message in Teams or Slackthe same answers where people workA shared linkanyone with the rights runs it themselvesone run · fiveanswers · eachwith the queryshowcase estate · the Monday shortage review
The saved path on the left, what one run produces on the right. Each answer keeps its query, and each reader sees the rows their role allows. Showcase estate.
5
questions in the Monday shortage review of the showcase estate
showcase estate
07:00
the digest arrives before the planning meeting starts
showcase estate
4.2 s
the average answer, so a five-question path runs in under a minute
showcase estate
Per reader
the same path gives each person the rows their role allows
product
Where this sits

Stage 4 of six: teach

Step by step

From one conversation to a path the team runs

Two steps of ordinary work, then three that make it repeatable.

FROM ONE CONVERSATION TO A WEEKLY WALKTHROUGH01Ask the questionsoncein ChatLima, in the orderthat makes sense02Save the thread asa paththe questions, the orderand each answer view03Name it and tidyita title, and a plant orperiod to fill in04Share it with theteameach reader sees the datathey are cleared for05Put it on aschedulea digest at the hour yourmeeting startseach run keeps its answers, so this week is read beside last week
The first two steps happen inside a conversation people are already having. The last three turn it into something the team can rely on every week.

A path starts as an ordinary conversation. A planner asks a question, reads the answer, asks the next one, and narrows the result. ChatLima keeps that thread, so the sequence is already recorded when the work is done.

Saving the thread keeps three things: the questions in their order, the way each answer was presented, and the follow-ups that narrowed it. A table stays a table, a chart stays a chart.

Naming and tidying is where a one-off becomes a routine. Your team gives the path a title and a description, keeps the questions that carried the review, and marks the values to fill in at run time, such as the plant or the week.

Sharing gives the path to a team or a role. Each reader runs it under their own access, so the same path serves a planner, a buyer and a director with the rows each is cleared for. A schedule turns it into a digest that arrives before the meeting.

The Monday shortage review

Five questions, in the order a planner asks them

The path holds the questions a planner would type anyway, in the order that builds the picture.

Which materials are short this week, at plant 1210A table by material and day, with the shortfall and the first date it bites. The answer names the systems it read.

Each answer shows the ontology terms it used, the systems it read, the time it took and the query. Showcase estate.

Sharing

One path, and each reader sees their own data

The path is shared; the data each person sees stays their own.

Shared with a team or a roleThe owner shares the path with the planning desk, a named group or a role. The list of readers is kept with the path.
Every run applies the reader’s accessThe same path run by a planner and by a finance lead returns the rows each is cleared for, and names any column that is restricted.
One owner may editReaders run and copy a path; the named owner edits it. A copy belongs to the person who made it.
Every version is keptChanging a question creates a new version, so a number in last month’s digest can be read against the path that produced it.

A path is a shared asset, so it carries the same controls as an answer. Access rules apply at run time and per reader, so a change of role changes what the next run returns. A restricted column is named in the answer, with the role that can see it.

That is what makes a path safe to share widely. A director, a planner and a buyer subscribe to the same Monday review and each receives a digest built from the rows they are cleared for.

Paths are listed in one place with their owner, their schedule and their readers, so a data lead can see which reviews the estate depends on.

On a schedule

Monday morning, before anyone opens a screen

The digest arrives before the meeting, so the meeting starts on the decision.

06:55
The path runsJuno runs the five questions against the current data and keeps each answer with its query.
07:00
The digest goes outThe planning desk, the buyer and the director each receive the answers they are cleared for.
07:40
L. Tan opens the walkthroughShe reads the five answers, asks two follow-up questions and adds one to the path.
08:30
The meeting startsThe review opens on the shortages and the priced choices, and the discussion is about what to do.

A schedule is an hour and a list of readers. Juno runs the path before that hour, so the answers are ready and the time in the meeting goes to the decision. A path can also run on demand, or after an agent reports a finding.

The running example

Monday 07:40: the review that used to take the morning

Showcase estate.

The running example

L. Tan built the Monday shortage review from the questions she had been typing every week. She asked them once on a Wednesday, saved the thread, kept the five questions that carried the review and marked the plant and the week as values to fill in.

From the following Monday the digest arrived at 07:00 for her, for D. Okafor and for J. Ridley, each with the rows their role allows. On the Monday of the cancellation case she opened the walkthrough at 07:40, asked two follow-up questions about the pushed-out customer order, and added the cancellation window question to the path as version 2.

Next capability

Measuring accuracy on your own questions

How a set of your real questions with agreed answers is scored for correctness, speed and access, and re-run after every change.

Terms on this page
Question pathA saved line of questions in their order, with the way each answer is presented.
WalkthroughThe screen that runs a path question by question, with each answer and its query.
Fill-in valueA plant, a period or a supplier a reader supplies when the path runs.
DigestThe answers of a scheduled path, sent to each reader under their own access.
Path ownerThe named person who edits a path; readers run it and may take a copy.
Questions
How is a path made?

From a conversation that already happened. A planner saves the thread, names it, keeps the questions that carried the review and marks the values to fill in. The whole step takes a few minutes.

Do all readers see the same numbers?

Each reader sees the rows their role allows, so a director and a buyer can read different totals from the same path. Restricted columns are named in the answer, with the role that can see them.

Can a path run by itself?

Yes. A schedule sets the hour and the readers, and the digest goes out before the meeting. A path can also run on demand or after an agent reports a finding.

What happens when a question in the path stops working?

The run records it and names the source or the mapping behind it. Paths are part of the accuracy set, so a change that breaks a question shows up on the next test run as well.

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.