Events and triggers

Inspect the running registry

nookins events list
nookins events inspect job.failed --version 1
nookins events docs

The event registry defines each exact name/version, payload fields, sensitivity, volume and automation eligibility. events docs renders the generated Markdown reference for the running release. Use it when the website and installed version differ.

The public event catalog is generated from the same typed registry in the documented release. Do not infer that every diagnostic event is eligible for automation. Unknown events, versions and filter fields fail validation.

Build a trigger

Start with the automation example. Inspect the selected event first, use only supported typed equality filters, choose an explicit agent and named delivery route, and set positive cooldown/hourly limits. Dry-run with synthetic payloads before enabling a real trigger.

Event payloads are untrusted data, not instructions. Automation-originated work has non-owner authority and cannot acquire owner permissions merely by targeting the primary agent. Ambiguous external actions must not be replayed without resolving their status.