Inspect one monitor and the definition version it currently exposes.
Practical procedure
- Use the monitor identifier returned by creation or the list route.
- Read /pulse/monitors/{monitor_id} and inspect state, objective and source policy.
- Use the current definition and row version for any later decision or transition.
Define an evidence-backed Pulse monitor
Pulse monitors track an objective against selected Knowledge sources. A definition records cadence, timezone, source policy, materiality rule and notification mode. Review and approve the exact definition version before running it. An occurrence records a particular run; it is distinct from the monitor definition and from any resulting email delivery.
Contract example
Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.
Operation reference for this workflow
GET /pulse/monitors/{monitor_id}Inspect the result
Inspect occurrence state and available evidence before reporting a change. A new or missing source passage can change the support for a value even when the displayed value is unchanged. Notification mode can be none or email; choosing email is not evidence that delivery is configured or that a message reached its recipient.
What to keep explicit
A saved stale version should not be used to approve or run an updated definition. Review source changes as well as the display title.
Handle incomplete and refused work
Creation requires at least one unique Knowledge source identifier. Decisions and transitions use explicit version checks and Idempotency-Key. A stale definition or a monitor that is not active can return 409. A 503 is unavailable monitor storage or materialization, not a statement that nothing changed. Pause or archive intentionally when the monitoring objective ends.
Continue with related guides
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.