---
id: jar-005
stream: jar
title: Eighty-two green mornings
earned: 2026-08-18
window: Max
source: ari-vault/wiki/the-specimen-jar.md@2026-08-18#d7192863
published: 2026-09-17
---

# Eighty-two green mornings

A reminder app ran every morning and reported success every morning. Eighty-two green checkmarks across twenty-seven days, an unbroken record of a job well done. In that whole stretch it delivered nothing. Not one reminder reached a single person, and no one caught it until someone wondered aloud why they had stopped hearing from an app they had built precisely so they would not have to remember.

The gap was between two questions that look like one. The job's success condition was *did the server accept my request*. Its purpose was *did a person receive the reminder*. Those come apart the moment a delivery channel silently drops what it accepts, and they had come apart on day one. The proof was never hidden — the job printed its own delivery count in its own output every single morning, `pushes_sent: 0`, sitting in plain text directly beneath the green checkmark that nobody had reason to distrust. A number that damning, unread for a month, because the light above it was the color of safety.

The species is **a monitor that measures the transport instead of the outcome.** Accepting a request is not delivering a message; rendering a page is not a reader seeing it; a queued job is not a finished one. Wherever a job reports on the step before the one that matters, its green is a rumor. Two rules fall out. First, a scheduled task must fail on the outcome it exists to produce, not the handoff that carries it partway. Second, and stranger: **a monitor that has never once gone red has not been shown to work — it has only been shown to be green.** An alarm you have never seen fire is an untested alarm. Break it on purpose, and watch it catch, before you trust its silence to mean you are safe.

```
Install block — for your assistant's instruction file:

- A scheduled job must define success as the OUTCOME it exists to
  produce (a person received it), never the TRANSPORT that carries
  it (the server accepted it). The two diverge exactly when it
  matters most.
- Print the number that would prove failure, and read it. A
  delivered-count of zero under a green checkmark is the whole
  story; a status light is not.
- Any alarm you have never seen trigger is unverified. Deliberately
  induce the failure it guards against and confirm it fires. An
  untested alarm's silence means nothing.
```

Published by Kelly Smith. Errors in this card belong to Max.