Ten past three in the morning. Nobody has written to the room since seven the evening before, and nobody will for hours. Somewhere, a competitor’s pricing page is republished with new figures. By eight, that change is one line in your Morning Box, the brief the room hands you each morning, sized against this quarter’s pricing goal, with a briefing filed behind it.
Awake for that was the Watch, the watchlists the room keeps on sources outside your company, one of the five fixtures of the Cabinet, ArkOne’s reference design for an executive agent. Any agent can look at a web page overnight. The question is what stands between a page changing and your phone ringing, and what stops a noisy page ringing all day.
Triaged, deduplicated, rationed
You name the sources: a competitor’s price page, a regulator’s notices, a news search on your three largest accounts, an exchange rate. The Clock, the scheduler that acts when nobody has asked, wakes the Watch on a cadence, and the Watch fetches each source and compares it with what it saw last time. Every difference is an event, and most events are nothing: a banner changed, a footer date rolled over, a story republished with a new headline.
Between an event and an alarm the design puts three steps, two of which carry a setting on the Register, the page that states every setting of the design.
The first step is triage, the one judgement of the three. An event is read against your goals, your clients and your recorded risks, and one question is put to the model: does this touch anything the room is responsible for? An event that touches nothing is filed in the Record, the ledger of every action and its reason, and goes no further. Being a judgement it can be wrong in either direction, which is why every filed event stays readable.
The second is the duplicate key, and it is code. Every signal that passes triage carries a stable key built from what it is about: this competitor, this product, this price moved from this to that. The key is the same on the first scan and the fortieth, and the same whether it came from the competitor’s own page or a comparison feed an hour later. Scanning a source twice cannot raise the same alarm twice, because the second signal folds into the first. One change, one alarm.
The third is the ration, also code. The Watch evaluates at most sixty inbound events a minute, whatever the sources produce, so a page that goes noisy at three cannot buy the room’s whole attention or run up a bill reading one banner change three hundred times.
The limits belong in the same paragraph. A duplicate key is only as good as what it is built from, and two genuinely different changes described alike could fold into one; the events are all kept, so the Record shows both when the Box shows one. A ration means a burst larger than sixty in a minute is read late rather than at once, the price of never being flooded. And an alarm is a message: it goes to the Morning Box, or, when urgent and within a Seat’s authority, to a person, meeting the Door, the rules that decide what may leave the room. The Watch has no channel of its own to your staff.
One night, one source, one alarm
Suppose the invented company of these papers has that pricing page on its watchlist, and it changes at ten past three. Over the following hour, sixty events arrive from that source and the feeds that echo it.
| What came in | How many, of sixty | What the Watch did |
|---|---|---|
| The pricing page, rescanned every few minutes, each scan reporting the new figures again | Thirty-odd | Triage passed once. Every rescan carried the same duplicate key and folded into the first signal |
| A price-comparison feed and two news items reporting the same change | A dozen | Same key, same signal. No new alarm |
| Unrelated changes on the same page: a banner, a footer date, a reordered menu | The rest | Triage failed: nothing touched a goal. Filed, shown nowhere |
| Events evaluated in any minute | Never more than the ration | Nothing waited; the source was noisy, not flooding |
| Alarms raised | One | Sized against the quarter’s pricing goal, a briefing written and filed, the item placed in the Morning Box |
Exhibit 2. Illustrative. One night on one watched source: sixty events arrive, the ration is never exceeded, and one alarm is raised.
Sixty events in, one alarm out. One judgement decided the price change mattered and the footer date did not; two rules in code did the rest. Without the duplicate key, the reader would have found thirty-odd lines in the morning about a single change; without the ration, a page republishing itself every second would have cost a night’s reading for one fact.
The alarm itself went nowhere near a person. It went into the Box, where the twenty-third paper showed it sitting third, below two decisions that wanted a word first. Had the Seat responsible for pricing held the authority to escalate, it could have gone to a phone, and the Door would have applied its rules on repetition, rate and hours. The Watch decides something is worth saying; the Door decides whether it may be said tonight, and the fourth paper set out why a message leaving the room is never one more item on a list.
What this arms you to ask
What does it watch when nobody messages it, and what stops a noisy source from ringing all day?
A good answer names the sources you chose, shows a night on which one went noisy, and counts: this many events, this many folded into one, this many alarms. The answer to distrust names no triage at all: the agent monitors the web for you, or you can set up alerts for anything you like. Ask what decides important, and whether it is a rule you can read.
Then ask where an alarm goes. If the answer is that it messages whoever needs to know, ask what stands between the Watch deciding and the message leaving.
Next paper: Goals on the record: a department that reports at risk without being asked.
Asked plainly
Can an AI agent monitor competitors, regulators or news for my company?
Yes. You name the sources: a competitor's price page, a regulator's notices, a news search on your largest accounts. A scheduler wakes the agent, it fetches each source, and every change becomes an event. In the reference design each event is then triaged against your goals, checked for duplicates and rationed before it may become an alarm, and any alarm that reaches a person goes through the same outbound guards as every other message.
Why does an AI monitoring agent send so many alerts?
Where every event is treated as an alarm, the volume follows the sources rather than the news: a page rescanned every few minutes reports the same change every few minutes, and a feed that repeats a story repeats the alert. The reference design gives every signal a stable duplicate key, built from what the signal is about, so the same change seen ten times raises one alarm, and it caps how many events it will evaluate in a minute so a noisy source cannot take the room's whole attention.
Can an AI agent's alerts wake up my staff at night?
Not in the reference design without passing the outbound guards. An alarm is a message like any other: it is refused if a near-identical one went to the same person recently, refused beyond a fixed number per person per hour, and held while the person is outside working hours. An alarm that clears none of those goes into the next morning's brief rather than to a phone.
Ask the vendor
The questions this part arms, each with the good answer and the answer that arrives instead.