Sign inStart

Alerts

The model tells you before you ask

Everything in the governance layer used to be a screen somebody had to open. A drifting forecast, a decision past its review date, a stress score that fell into the red, a runway shorter than a hiring cycle: each of them sat there until a person happened to look. Alerts are the rules that look on the person's behalf.

Build a twinMonitoring and drift

A rule is a question with a yes or no answer, asked of the twin as it stands. Yes opens an alert, once. No closes it.

eight rules, asked every few hoursthe inboxActuals drift from the forecastnoA decision is past its review dateyesRunway is shortyesResilience below the linenoA proposal is waitingyesOutcome outside the bandyesMostly defaultsnoNothing uploadednoPast review: raise list price 12 percentact · raised once, closes when it clearsRunway is 5.2 monthsact · raised once, closes when it clearsWaiting 4 days: monthly customer churnwatch · raised once, closes when it clearsOutside the band: second warehousewatch · raised once, closes when it clears4 of 8 rules answered yes; the rest stayed quiet

The rules

Eight questions, asked every few hours

Rules
8drift, review dates, runway, resilience, band misses, waiting proposals, readiness, stale uploads
Severities
3act, watch and info, so the inbox reads in the right order
Thresholds
yoursthe runway line, the resilience line, the days a proposal may wait
Raised twice
0every condition has a fingerprint, so one thing wrong is one alert

What each rule reads

The questions, and where each answer comes from

RuleReadsLoud
Actuals drift from the forecastthe monitor: which metrics left the band, by how much, over how many monthsact
A decision is past its review datethe register: approved or enacted decisions whose review date has passed with no outcomeact
Runway is shortthe model: twelve months from the ledger as it stands, the same glance the book readsact
The stress test fell below the linethe latest resilience score and the weakest shockwatch
An outcome landed outside the banda closed decision in the last thirty days whose actual missed the bandwatch
A proposal is waiting on a reviewerthe queue: proposals older than the days you setwatch
The model stands mostly on defaultsreadiness against the line you setinfo
Nothing new has been uploadedthe last file and the last month of actualsinfo

The life of an alert

Opened by a rule, closed by the world

01

It opens once, with what it read

Every alert carries the rule that raised it, the plain sentence, the numbers it read with their origins, and the screen to open. The same condition never raises twice: it has a fingerprint, and a sweep that finds it already open updates the row instead.

  • The rule's own explanation of why it asks
  • The numbers, as chips, each with an origin
  • One button to the screen that fixes it
02

A person acknowledges, snoozes or resolves

Acknowledged means seen and working on it. Snoozed means ask me again in a week; if the condition is still true then, it reopens. Resolved means done. Nothing is deleted, because a closed alert is part of the record, and the record is what an auditor reads.

eight rules, asked every few hoursthe inboxActuals drift from the forecastnoA decision is past its review dateyesRunway is shortnoResilience below the lineyesA proposal is waitingyesOutcome outside the bandnoMostly defaultsnoNothing uploadedyesPast review: raise list price 12 percentact · raised once, closes when it clearsResilience scored 48 of 100watch · raised once, closes when it clearsWaiting 4 days: monthly customer churnwatch · raised once, closes when it clearsNothing uploaded for 96 daysinfo · raised once, closes when it clears4 of 8 rules answered yes; the rest stayed quiet
03

It closes itself when the answer turns to no

Record the outcome and the past review alert closes. Upload the month and the stale upload alert closes. Switch a rule off and its alerts close. The inbox is a picture of the twin as it stands, not a to do list that grows.

  • Rules are asked when the inbox opens, after anything they read changes, and on a timer
  • Every raise and every close is on the record

Delivery

In the application, by email, in a digest, to your systems

A new alert goes to the owner and every reviewer by email, if you want it to. The digest is one plain page a week or a day: what needs a person, where the model stands, and everything that happened on the record since the last one.

And any hook that asked for the alert.raised event is called, signed, with the rule and the plain sentence in the payload.

  • Email on a new alert, on or off per twin
  • A daily or weekly digest, previewed in the application before it is sent
  • The alert.raised event on hooks, signed like every other
Finance exportCRM extractMonthly actualsposted with a keythe twinreads, runs, signsanalysis.completeddecision.approvedstress.completeddrift.flaggedsigned, delivered, loggedkeys in, hooks out

Eight questions, asked so you do not have to.

Alerts are on the Operator plan and above. The rules are on the moment a twin is built.

Build a twinSee the plans