Agent Playbooks
Production-oriented integration playbooks for Droplit + Sigma.
Agent Playbooks
Start here: Agents — how an agent signs up, creates a droplit, and deposits.
These playbooks are focused on fast production readiness for agent and backend workflows. Each playbook assumes a BSV wallet and BRC-103/104 mutual authentication.
Playbook 1: Payout Agent
Goal
Execute controlled payout actions to recipient addresses using droplit tap/fund operations.
Flow
- Load a dedicated payout wallet in your runtime.
- Create one reusable SDK
AuthFetchclient for payout actions. - Execute tap/fund endpoint call.
- Persist txid and recipient metadata.
- Emit a push-data record for audit tagging (optional).
Operational guardrails
- Require recipient validation before sending.
- 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
- Normalize event payload to stable string array format.
- Submit
/faucet/:name/pushthrough the authenticated SDK client. - Store returned txid/vout metadata in your app database.
- 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
- Open a BRC-103/104-authenticated WebSocket connection to
/faucet/:name/activity-stream. - Parse
faucet_activityevents and route by event type. - Trigger policy handlers (alerting, retries, downstream updates).
- 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.