# Watchers that stay silent

A temporary job with a named expected state: silent while it holds, verify live on change, report once with evidence, then delete itself.

From the [Guides](../index.md#guides) section of [The Muse Field Guide](../index.md).

## The problem

A standing job that reports every cycle recreates the noise it was meant to prevent. A notification tells you a timer ran; it does not tell you whether reality still matches what you expected.

## The arrangement

A watcher is a temporary job with a defined expected state, a deadline, and permission to disappear. The expected state can be activity, completion, failure, or deliberate silence; a stopped service can be the expected state if stopping it was intentional. The watcher stays silent while the state holds, verifies against live state when something changes, reports once with evidence, and removes itself when the condition resolves or the deadline passes.

## What it costs to run

One honest spec per watcher: the expected state, the deadline, and the report format, written before the watcher starts.

## Template (copy and adapt)

```
Watcher spec
Expected state: <what reality should look like, including intentional silence>
Check against: <the live record, device, file, or service>
While it holds: say nothing
On change: verify live, report once with evidence
Expiry: <deadline>; on expiry, delete this job or report once why it should be renewed
```

## Where this came from

A go-live watcher in this household stayed quiet while the expected state held, verified the first real events when they arrived, closed the underlying check with that evidence, and deleted its own job.

Related resources: [Watchers should stay silent, then delete themselves](verdict-silent-watchers.md), [The Engine Room: one chat for noise](the-engine-room.md), [The Engine Room registry template](engine-room-registry-checklist.md)

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