The Exception Scout watches every load on a freight desk and speaks up before the customer asks. This console opens it up, layer by layer. Every checkpoint is a click, and nothing moves until you do.
active loads on the board. The last tick ran at 17:27Z and alerted once. Tick #2,847 is due. Six layers sit between the raw feed and one alert worth a person’s attention. You advance every one of them.
For the engineer: webhooks where a carrier offers them, polling where they do not. Every source speaks a different dialect, so the first job is normalizing to one canonical event. This layer interprets nothing. Shape only.
| Load | Lane | Last ping | Dwell | Promised | Drift |
|---|---|---|---|---|---|
| LD-2214 | LAX → PHX | 17:42:01Z | 0m | 19:45Z | -0h20m |
| LD-3302 | CHI → DEN | 17:42:02Z | 74m stopped | 18:30Z | +3h10m |
| LD-4088 | ATL → BNA | 16:51:44Z | silent 51m | 20:15Z | unknown |
| LD-4917 | DAV → MSP | 17:42:02Z | 82m at pickup | 22:00Z | +0h45m |
| LD-5120 | SEA → PDX | 17:42:01Z | 0m | 21:15Z | +0h06m |
| LD-1893 | DFW → OKC | 17:42:02Z | 0m | 20:40Z | -0h05m |
+ 41 more, all inside their windows
For the engineer: a small store keyed by load carries what a single ping cannot: computed dwell, the promised window from the order record, and what was already alerted on. Ticks are stateless runs over durable state. A crashed run loses nothing, a restarted one double-alerts nothing.
For the engineer: this is the cost gate. Three thresholds in ordinary code drop 44 healthy loads at zero tokens, which is why watching every load costs almost nothing. On a typical tick roughly 95 percent of the board stops here.
2 confirmed · 1 dismissed · 3,184 tokens in · 402 out · $0.014 of a $0.50 per-run cap. The dismissal came from context the rules could never see.
For the engineer: only candidates ever reach the model, one call each, full context attached. The contract is schema-enforced JSON: exception or not, severity, cause, new ETA, and a customer-safe draft. The model judges and writes. It does not fetch, post, or decide policy.
For the engineer: none of this is language. Read-only credentials in the runner, a hard spend cap in the request path, an idempotency key, an append-only audit log. The model never sees these controls and cannot talk its way past them.
For the engineer: one structured message, evidence attached, then the agent stops. The customer call, the carrier escalation, the judgment: human. The agent’s job ends at “you knew first.”
You clicked this one through. The other ninety-five run themselves, exactly this way, while the desk does the work only people can do.
Simulated loads, real anatomy. The freight is invented for the demo; the layer boundaries, the cost gate, and where the guardrails sit are exactly how the production build is wired.
The anatomy transfers to any stack: swap the feed, the order system, and the channel, and the boundaries hold. What matters is what each layer is allowed to do.
A read-only poll of the track-and-trace feed on a 15 minute cron. Webhooks where a carrier offers them, polling where they do not. Every source speaks a different dialect, so the first job is normalizing to one canonical event: load, timestamp, position, speed, status, source. This layer interprets nothing.
A small store keyed by load: latest ping, computed dwell, the promised window from the order record, and every alert already sent. Ticks are stateless runs over durable state, so a crashed run loses nothing and a restarted one double-alerts nothing.
Deterministic thresholds in ordinary code: dwell at a stop, projected ETA drift against the window buffer, trackers gone silent. This is the cost gate. A healthy load never reaches the model, and on a typical tick that is roughly 95 percent of the board.
Candidates go to the model one at a time, each call carrying the load’s full context: route plan, recent pings, dwell history, order terms, road status. The contract is schema-enforced JSON: exception or not, severity, cause, new ETA, and a customer-safe draft. The model judges and writes. It does not act.
Enforced by the harness, never the prompt: read-only credentials in the runner, a hard per-run spend cap in the request path, an idempotency key so one exception alerts exactly once, and an append-only audit log of every input, call, and post.
One structured message to the ops channel with the evidence attached: pings, route, window. A named human owns everything outward, the customer call and the carrier escalation. The agent’s job ends at “you knew first.”