Design a monitor that knows when to stay quiet

Create a monitoring contract for [SYSTEM] and [EXPECTED NORMAL STATE]. Define meaningful change, failure, completion and user-action thresholds using only signals that can actually be observed. Specify polling interval, deduplication key, quiet-hours handling, one escalation path and what to do when an observation tool fails. Return a decision table with examples of 'notify' and 'remain quiet', plus a plain-language alert template. Do not claim background monitoring has been installed; this is a design unless deployment is separately authorised and verified. Avoid collecting more personal data than needed.