Skip to Content
OpenClaw GuidesOperational Checklist

Operational Checklist

Use this checklist when rolling out Chirpier for OpenClaw in a real environment.

  1. verify the same bearer token works for logs and control-plane APIs
  2. emit canonical OpenClaw events
  3. confirm Chirpier auto-registers the event definitions
  4. create at least one valid chart per key signal
  5. create one reliability policy and one latency policy
  6. test destination delivery before depending on it
  7. inspect delivery history for both test and alert
  8. review event names for drift or one-off naming mistakes
  9. verify rollup queries use canonical periods: minute, hour, day
  10. verify invalid aggregate and semantic-class combinations are rejected

This catches most early integration errors before the setup becomes operationally important.

Last updated on