A watch is a rule that describes a condition you want to hear about. You write it the way you would say it, Juno turns it into a rule the engine evaluates as often as you choose, and the finding reaches the person who can act on it.
Four steps: state the rule, alert the right person, resolve inside your limits, execute the agreed resolution.
A watch starts as a sentence. A planner writes “tell me when the forecast error for a material goes above 10% in a month”, and the Planner Agent turns it into a rule with a field, a test and the line you set.
You then choose how often Juno looks: at a set time, at an interval, when a row changes in a source, or when a person runs it. The watch reads the same fact base an agent run reads, under the same access.
When the condition is met, Juno records a finding: the facts at that moment, the rule version, the measure and the value at stake. The finding carries its reason in plain words, so the person who receives it can judge it in seconds.
The alert then follows the route the watch carries: a task in a queue, a message in a channel, a line in a digest, or the start of an agent run. Every route keeps the same evidence with it.
One screen holds every watch in the estate, with its line, its level, its route and what the last run found.
| Rule under watch | What it reads | How often | Level | Last run | What the last run found |
|---|---|---|---|---|---|
| Forecast error above 10% | Forecast error by material and month | Monthly | A1 | 01 Sep 06:00 | Watching |
| Cover below the policy floor | Weeks of cover per material at plant | Every 15 min | A2 | Mon 07:05 | 3 findings |
| Cancellation window closing | Open lines and the window on each one | Daily 06:00 | A2 | Mon 06:00 | 38 findings |
| Excess above eight weeks | Stock on hand and on order against demand | Daily 05:30 | A2 | Mon 05:30 | 14 findings |
| Supplier late rate above 5% | Confirmed dates against receipt dates | Weekly | A1 | Sun 22:00 | Watching |
| Lead time drift above 4 days | Planned delivery time against actual | Weekly | A1 | Sun 22:10 | 2 findings |
| An allocation-bound supplier changes | An event on the supplier record | On the event | A2 | Fri 16:20 | Paused by P. Sharma |
Seven of the twelve rules under watch. Showcase estate.
Each watch carries an owner, a level, a route and a version history. The owner edits the line, changes the route, pauses the watch or retires it, and each of those changes becomes a new version in the rule store.
The level decides what a finding may lead to. At A1 the watch reports and a person acts. At A2 it drafts an action and a named person approves it. At A3 it acts inside your limits and sends the rest to a person.
The route is part of the watch, so the finding reaches the desk that can act on it.
| Route | What arrives | Who usually receives it | When it suits |
|---|---|---|---|
| A task in an approval queue | The drafted action, its evidence and a clock | The buyer or planner who owns that decision | A finding that needs a decision today |
| A message in Teams or Slack | One line with the value at stake and a link to the finding | The desk that watches the channel | A finding people act on within the hour |
| A digest by e-mail | The findings of the period, grouped and ranked | Managers and the planning lead | A weekly or monthly review |
| An answer in ChatLima | The finding with the terms, the systems and the query behind it | Anyone asking about that material or supplier | A question that follows an alert |
| An agent run | The finding starts the agent that owns that decision | The agent, at the level you set for it | A case your published rules already cover |
A route is a setting on the watch, so the same finding can reach two places: a message for the person on duty and a task in the queue for the record. Each copy carries the finding reference, so a reply in one place is visible in the other.
Findings are grouped before they are sent. One material with 14 lines above the cover floor arrives as one alert with 14 lines inside it, ranked by value at stake. A clock on the queue and an escalation route to the next desk are set on the approvals page.
One sentence, five rows, a monthly run, and a proposal a planner can accept or set aside.
| Row | Field | Test | Value | Then |
|---|---|---|---|---|
| 01 | Forecast error | above | 10% in a month | carry on |
| 02 | Material class | equals | A or B | carry on |
| 03 | History held | at least | 6 months | carry on |
| 04 | Alert | goes to | the demand planner | send the alert |
| 05 | Other methods | tested on | the last 6 months | propose the better method |
The sentence is the whole watch; the table below it is what the engine evaluates. Showcase estate.
This watch sits at A1 assisted: it reports, and L. Tan decides. Juno still does the work of testing the alternatives, so the message arrives with a proposal and the evidence behind it.
Raising the watch to A2 would send the same proposal as a draft for a named approver. Raising it to A3 would let it apply a method inside your limits and send the rest to a person.
The limits are what make that safe. A method change applies where the tested error stays below your line across six months of history, and where the material sits in the classes the watch covers.
Every firing of the watch is on the audit trail: the facts read, the version evaluated, the alert sent, the person who acted and what happened afterwards.
Showcase estate.
The excess watch ran at 05:30 and found 14 materials above eight weeks of cover. At 06:00 the cancellation window watch found 38 open lines worth $412,000 whose windows close on Thursday. Both findings carried the material, the plant, the value at stake and the working.
By the time L. Tan opened the 1,240 exception messages at 07:40, both findings sat at the top of her list: the 212 messages that touch an open purchase order line, with the 38 cancellable lines marked. A shortage triage role, once built from the blueprint, would rank the rest of the morning the same way.
What a finding becomes when the evidence supports an action: a recommendation with its basis, its confidence and the value at stake.
The owner of each watch sets the route and the level. A manager can add a digest for the team, and anyone can ask ChatLima for the findings of a watch at any time.
Findings are grouped by material, supplier or order, ranked by value at stake, and sent once per period per line. Raising the line on a watch is a single edit, held as a new version.
Yes. A finding is one of the four ways an agent run begins, so a watch on stock cover could start a stock rebalance role at the level it carries, once that role is built from the blueprint.
Yes. Add the measure to the ontology, map the columns that feed it, and write the watch against it in the same plain language.
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.