Watching production

A task that came from Signals does not end when it is merged. Merging is a claim, and the claim is checkable: the same runtime that reported the problem can say whether it stopped happening.

So a Signals card carries a runtime state, and that state keeps moving after the work is done.

The states

• Not verified yet. The card exists, the fix has not shipped, or nothing has been observed since it did.
• Watching production. The fix is out and Signals is watching the events that led to this card. This is the state a card sits in while the answer is still being earned.
• Quiet, not confirmed. Nothing has come back, but not enough has happened to call it fixed either. A low-traffic path can be quiet because it is fixed or because nobody has hit it, and those are not the same sentence.
• Verified fixed. Enough traffic has passed through the affected path without the issue returning.
• Issue returned. It came back. The card reopens with the evidence attached rather than a new card appearing with no memory of the first attempt.
• Archived after healthy coverage. The path has been healthy long enough that watching it further tells you nothing.

Why "quiet" is its own state

Most tools have two answers: fixed, or not fixed. That forces a guess whenever traffic is thin, and a guess in this position is always optimistic, because nothing arriving looks exactly like success.

Separating "nothing came back" from "enough went through" is what keeps the verified state worth something. When a card says Verified fixed, it means traffic went through the path, not that the room went silent.

Issue returned is the point

The state that justifies the whole loop is the one nobody wants to see. A fix that regresses two weeks later normally comes back as a fresh report, disconnected from the work that was supposed to have solved it, and the team relearns the problem from scratch.

Here the original card reopens. The attempt, the context it ran with, and the runtime evidence from both occurrences are in one place, so the second attempt starts from what the first one tried.

Where you see it

On the card, as a small state chip beside the Signals badge, with the time it last changed. Verified reads in the success tone, Issue returned in the alert tone, Watching production in the informational one, and the rest stay muted. It is a status, not a notification: the board does not interrupt you to say a card is still being watched.