Skip to content

Skill Watch

Zach Stern edited this page Oct 20, 2026 · 9 revisions

Watch

Commission and prove a real observer that survives the session.

Watch defines the condition that matters, the external mechanism that checks it, who receives a useful alert, and how that mechanism can be stopped. The skill itself does not stay running after the conversation.

Use it when: A meaningful bound must be noticed between sessions and someone will act when it is crossed.

Use something simpler when: You need a current-state readout, diagnosis, automatic remediation, or a notification nobody has agreed to receive.

Illustrative request

Notify the designated operator if this service misses the agreed freshness bound. Prove the complete alert path with a safe test and verify the disable control.

What a useful result looks like: A commission record with DECLARED, BLOCKED, INERT, PROVEN, or SUSPECT state and supporting receipts. PROVEN requires a persistent enabled observer, a safe crossing through the real path, and delivery to the destination.

Boundary: A configuration file, dry run, or silent channel does not establish an active watch. Failed observation or delivery remains visible; noticing a problem does not authorize fixing it.

Health observes now; Triage investigates a reported failure.

Read the canonical v7.3.0 method · All methods

Clone this wiki locally