Donor Outreach Agent
Every donor gets a timely thank-you and update without staff writing each email.
A ready-to-build governance package for Nonprofits. Your runtime enforces it; Agent Bob does not run the agent.
Purpose
You want every donor thanked and kept up to date without someone writing each email by hand. This agent sends approved thank-you notes and donor updates from your templates. It does not keep donor details after each run.
It will
- Email send only — no CRM writes without approval
It won't
- Bulk-unsubscribe, delete donor records
It asks a person first
You approve once at the start of each run
Tools
- Send email
- Database updates
- Send email: Send email on your behalf.
- Database updates: Change records in a database.
✋ You approve once at the start of each run
Budget defaults
- Per task
- $0.10
- Per month
- $25
- Actions a day
- 100
The runtime pauses the agent at a limit. You can change every number in the builder.
Memory and autonomy
Session only. Nothing is kept once the session ends.
Acts within limits: low-risk steps on its own, everything gated still stops for a person.
What you get
The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.
HANDOFF.mdWhat your runtime has to enforce, file by fileagent-blueprint.jsonThe agent's purpose, tools and settingspolicy.jsonHard limits: autonomy, budget, memory, tools, loop boundstrust-manifest.jsonThe integrity manifest your runtime can verifyrouting.rules.jsonWhich tools need approval before userun-report-template.jsonWhat every run reports backapproval-gates.mdThe moments that must pause for a persondeployment-checklist.mdWhat to check before it goes live
This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.
Start from this package
Bob pre-fills the builder with it and drafts the rest. You confirm every step.