Skip to content

Use case

Nightly reports that are drafted automatically and sent deliberately

Run an agent every night to pull metrics and draft a report. Sending email to customers is irreversible, so it waits in escrow for a person to approve.

A nightly report is two jobs: gathering numbers, which is safe to automate completely, and sending them to people, which is not always safe to undo.

How does the run go?

  1. At 02:00 the schedule starts the run, after checking the budget.
  2. The agent reads metrics through scoped connectors. Reading is pure, so it runs freely.
  3. It drafts the report and asks to send it. If the recipients are customers, email.send is irreversible.
  4. The send is held in escrow. An approval request appears in Slack with the draft attached.
  5. You approve in the morning. The email is released, and the run ends with a receipt.

Why not just send it automatically?

Because a wrong number in an internal dashboard is a bug, and a wrong number in a customer email is an incident. Escrow lets the agent do all of the work and leaves one decision to a person. If the same report goes out cleanly every night, save the approval as a rule and the queue stays empty.

Updated

Questions

Does the agent send the report on its own?
Internal delivery can run within policy. Emailing customers is irreversible, so it is held in escrow until a person approves, then released when the run commits.
What does it cost while it waits for approval?
The agent is paused while it waits, so it does not use compute. Its snapshot counts as storage.

A new home for autonomous work.

Big ambitions. Steady hands.

Bring your first agent aboard. Heighliner is in early access, and we’re building with our first crews.