Step 1: inspect the approved packet
The agent should begin by reading the template or packet definition. This confirms the document is approved, the variables are known, and the agent is not inventing terms inside a prompt.
In AgentContract, the CLI and API both support this operating style. The agent can inspect templates and show the human what packet it intends to use.
Step 2: dry-run the send
A dry run is the approval moment. It should return the resolved recipient, template, variables, metadata, and proposed send action without emailing the signer.
For agent workflows, this is more important than a confirmation modal. The dry-run output can be copied into the conversation, reviewed by a person, and approved explicitly.
- Recipient is correct.
- Template is correct.
- Variable values are correct.
- Webhook metadata is correct.
- The operator approves the real send.
Step 3: track until completion
After sending, the agent should report the agreement id and status. It should be able to remind, cancel, or download the signed PDF without asking the user to hunt through a dashboard.
The end state should be a signed record, not just an email that was sent. That record is what lets the next onboarding or compliance step continue.