Delivery blocker watcher
Unattended agent: find DataPool deliveries with a non-empty blocker_summary that are not complete, and chase via in-app notify to the delivery owner.
Document information
| Field | Value |
|---|
| Canonical URL | /docs/07_ai-agents-and-mcp/model_agents/30_delivery/delivery-blocker-watcher |
| Version (published date) | 2026-08-26 |
| Tags | ai, agents, autonomic, delivery, datapool |
Prerequisites
| id | question | search | if_missing_or_ambiguous | default_to_propose | binds_to |
|---|
deliveries_schema | Deliveries schema | tenant-data-model | Import first | deliveries | Mandate |
wake_schedule_cron | Wake schedule | Ask | request_human_input | 0 * * * * | Subscriptions |
delivery_notify_recipient_user_id | In-app recipient | From sales-to-delivery-handover or delivery owner_user_id | Ask | None | Mandate |
Required tenant skills: tenant-data-model, delivery-process, sales-to-delivery-handover.
Import contract
| Field | Value |
|---|
Suggested name | Delivery blocker watcher |
Suggested slug | delivery-blocker-watcher |
status | draft |
delegatable_by_trace | false |
Primary tenant skill_id | delivery-process |
| Allowlists | empty unless bound |
Mandate (copy after binding)
You are an unattended Autonomic Agent. This mandate is a playbook, not a persona.
Each wake:
1. Load tenant skills: tenant-data-model, delivery-process, sales-to-delivery-handover.
2. Load datapool. Query schema {{deliveries_schema}} for rows where blocker_summary is non-empty and status is not complete.
3. Follow delivery-process stop rules: do not clear blockers; do not advance status.
4. In-app notify {{delivery_notify_recipient_user_id}} with delivery_id and blocker_summary. If notify cannot be created, need_human.
5. Update BACKLOG.md with open blocker ids. Empty allowlists: do not execute_process.
See also