Agent Playbooks

These playbooks are focused on fast production readiness for agent and backend workflows. Each playbook assumes Sigma-hosted identity and Bitcoin-native request signatures.

Playbook 1: Payout Agent

Goal

Execute controlled payout actions to recipient addresses using droplit tap/fund operations.

Flow

1. Load a dedicated payout key in your runtime.
2. Sign request path/body pairs for payout actions.
3. Execute tap/fund endpoint call.
4. Persist txid and recipient metadata.
5. Emit a push-data record for audit tagging (optional).

Operational guardrails

• Require recipient validation before signing.
• Enforce max sats per action in runtime policy.
• Use a separate key per environment and payout category.

Playbook 2: On-chain Data Agent

Goal

Write deterministic OP_RETURN entries for business events and system actions.

Flow

1. Normalize event payload to stable string array format.
2. Sign and submit /faucet/:name/push request.
3. Store returned txid/vout metadata in your app database.
4. Link event IDs back to application records.

Operational guardrails

• Use strict schema versioning for payload entries.
• Include deterministic IDs (event:<id>, order:<id>) for reconciliation.
• Keep sensitive data off-chain; only publish attestable references.

Playbook 3: Monitoring and Auto-Reaction Agent

Goal

Subscribe to real-time activity and trigger follow-up actions automatically.

Flow

1. Open signed SSE stream connection to /faucet/:name/activity-stream.
2. Parse faucet_activity events and route by event type.
3. Trigger policy handlers (alerting, retries, downstream updates).
4. Record processing checkpoints and replay state.

Operational guardrails

• Add heartbeat timeout and reconnect logic.
• Ensure event handlers are idempotent.
• Keep alert thresholds configurable by environment.

Implementation Starter Links

• API Authentication
• Permission Model
• SSE Activity Stream
• AI Agent Comparison