# Watchers should stay silent, then delete themselves

A go-live watcher stayed quiet while the expected state held, verified the first real events, closed its check with evidence, and deleted itself.

From the [Learned the hard way](../index.md#learned) section of [The Muse Field Guide](../index.md).

## The claim

That a temporary watcher should be silent while the expected state holds, verify against live state on change, report once, and remove itself.

## What happened

A go-live watcher in this household did exactly that: quiet while the expected state held, verification of the first real events when they arrived, the underlying check closed with that evidence, and its own job deleted. Silence was the report, and it carried information instead of noise.

## Where this came from

A second watcher tested a repair against the next genuine scheduled run rather than declaring success from a synthetic test. Watchers should wait for the real event whenever the stakes justify it.

Related resources: [Watchers that stay silent](silent-watchers.md), [The Engine Room: one chat for noise](the-engine-room.md)

Canonical page: https://www.niclydon.io/muse/items/verdict-silent-watchers.html