Pick a scenario. Watch the agent handle it.
This is the primary conversion surface. Every blog post, every LinkedIn post, every Reddit thread ends with a link here. These are real workflows running on active projects.
Subcontractor emails a closeout document at 11pm
The Field Agent wakes on its 4-hour heartbeat, finds the email, classifies it as a closeout document, matches it to the correct project in Supabase, logs it, and sends a Telegram confirmation to the PM channel.
AHJ sends a permit revision with a 48hr deadline
The Permit Agent parses the revision, extracts the new requirements and deadline, updates the permit record, flags the 48-hour risk, and notifies the PM with the exact action needed.
Monday morning: 15 active projects, what does the supervisor report?
The Ops Supervisor queries Supabase for the past 7 days of agent activity, compiles a digest of completions, blockers, and at-risk items, and delivers it to the PM channel before 9am.
Inspection passes — is the milestone ready to invoice?
The Permit Agent receives the inspection pass notice, checks the project milestone map, confirms all prerequisite documents are logged, and flags the project as ready for invoice preparation.
Agent cards
Name, inbox, heartbeat, model, and what each one prevents.
Field Agent
field@ops.opsforenergy.comReceives field crew check-ins, closeout documents, and site photos. Classifies, matches to projects, logs to Supabase, and surfaces blockers to the PM channel.
Permit Agent
permits@ops.opsforenergy.comMonitors AHJ inboxes and permit portals, parses status updates, flags delays and expiry risks, and routes actionable items to the PM Telegram channel.
Ops Supervisor
supervisor@ops.opsforenergy.comAggregates signals from the other agents plus Supabase data to produce weekly status digests, flag at-risk projects, and brief stakeholders — automatically.
How the system is wired
MCP layer, Supabase, AgentMail, Telegram, and Claude Sonnet 4.