Start the day with the signal, not the overnight noise.
Review overnight incidents, group recurring signals, check the approved runbook, and deliver a source-linked morning handover.

A source-linked morning brief with owners, open risks, and recommended follow-up.
Human sign-off requiredA source-linked morning brief with owners, open risks, and recommended follow-up. Prepared for review, never posted.
How this composition works.
This workflow wakes before the team, gathers overnight operational evidence, separates repeated patterns from isolated alerts, and prepares a concise brief. Routine reporting can run automatically, while paging an owner or proposing a production change remains a human decision.
Collect overnight evidence
Read new incidents, errors, and service signals since the previous handover.
Check service context
Compare the signal with edge and availability context before drawing a conclusion.
Ground the response
Link recommendations to the approved operational runbook.
Deliver or escalate
Post the routine brief and pause for approval when an owner must be paged.
A human signs off
Paging an owner or changing a production system always requires explicit approval.

A source-linked morning brief with owners, open risks, and recommended follow-up.
Human sign-off requiredA source-linked morning brief with owners, open risks, and recommended follow-up. Prepared for review, never posted.
Composed from the tools operations already uses.
Sentry. Investigate errors, traces, releases, and project health in Sentry.
Cloudflare Developer Platform. Manage Cloudflare accounts and KV storage namespaces, and list Workers.
Slack. Read channels and messages, post messages, and upload files as your Slack bot.
Notion. Read, search, and update Notion pages and databases.
Optional skills add method and verification.
Put your operations workflow under policy. Tell us what your team repeats today.
More for operations.
Vendor SLA review
Collect service evidence, compare it with documented commitments, and prepare a review packet that clearly separates facts from assumptions.
See the workflowAccess review
Read current access across approved systems, compare it against the recorded roster, and prepare a review list of accounts that no longer match.
See the workflowRunbook drift check
Compare approved runbooks against the systems they describe, flag steps that reference something that has since changed, and prepare a correction list.
See the workflow


