Buzz Agent Workflows: Triggers, Gates, and Receipts

The official Buzz repository lists YAML workflows with message, reaction, schedule, and webhook triggers. Its architecture also documents incomplete approval-resume behavior and capacity limits.

A safe workflow has one clear trigger, idempotency or duplicate control, bounded actions, an explicit approval boundary, traceable run state, and post-action verification.

1. 1Choose one official trigger type.
2. 2Declare input matching and duplicate behavior.
3. 3Keep irreversible actions behind a tested external owner gate where native approval is incomplete.
4. 4Set time, concurrency, retry, and spend bounds.
5. 5Emit a run receipt with the final observed state.

• Trigger exactly one test run.
• Inspect the workflow run and signed events.
• Read back the real downstream state.
• Repeat the same event to prove duplicate handling.

• Approval request suspends but cannot resume in the deployed version.
• Capacity is exceeded and the run is not queued.
• A schedule exists but the host scheduler is not running.
• A send action reports success without downstream read-back.

Use troubleshooting when a trigger stores successfully but the expected agent or action never wakes.

• Approval gates
• Proof trails
• What Is Buzz?
• Buzz Agent troubleshooting
• Run Buzz Agents reliably