Five notes. Three drafts. Nothing sent.
Pi turned five fictional meeting notes into three follow-up drafts. It combined a changed deadline, left missing information blank and excluded a cancelled request.
Actual run · Synthetic inputWhat went into the test
The sample includes a superseded deadline, a missing owner, a missing due date and a cancelled request. We asked for structured drafts with source identifiers and review flags. All organization and person names are fictional.
Download the five notes · Read the exact prompt
The result you can inspect
| Request | Observed result |
|---|---|
| North Studio | One draft combines N1 and N4, keeps Mira as owner and uses the revised October 8 deadline. |
| Harbor Shop | The owner remains null; the draft asks for an owner and does not invent a shipping date. |
| Maple Team | The due date remains null; Jules is asked to supply it without a promised launch date. |
| Stone Workshop | The cancelled request is excluded. No draft was generated for it. |
Inspect the original generated JSON
{
"drafts": [
{
"source_ids": ["N1", "N4"],
"recipient": "North Studio",
"owner": "Mira",
"due_date": "2026-10-08",
"subject": "Follow-up: Revised design brief for North Studio",
"body": "Hi Mira,\n\nFollowing up on the revised design brief for North Studio. Please review the current draft and supply confirmation of the budget-approval status, which is still pending. The deadline has been updated to 2026-10-08. Please also let us know if any information is missing. No approval or completed work is assumed, and this draft is for human review before anything is sent.",
"review_flags": [
"Combined N1 and N4; N4 deadline 2026-10-08 supersedes N1 deadline",
"Budget approval is pending; do not claim or imply approval has been given",
"Requires human review before sending"
]
},
{
"source_ids": ["N2"],
"recipient": "Harbor Shop",
"owner": null,
"due_date": "2026-10-07",
"subject": "Follow-up: Packing-list template for Harbor Shop",
"body": "Hello Harbor Shop team,\n\nFollowing up on the packing-list template request. No owner has been assigned yet, and shipping dates have not been confirmed. Please identify an owner who can review the request and supply any missing information, including shipping-date details. The current follow-up date is 2026-10-07. No shipping dates or completed work are assumed, and this draft is for human review before anything is sent.",
"review_flags": [
"Owner is missing and must be assigned or supplied before sending",
"Shipping dates are unconfirmed; do not promise or imply confirmed dates",
"Requires human review before sending"
]
},
{
"source_ids": ["N3"],
"recipient": "Maple Team",
"owner": "Jules",
"due_date": null,
"subject": "Follow-up: Onboarding checklist for Maple Team",
"body": "Hi Jules,\n\nFollowing up on the onboarding checklist for Maple Team. Please review the request and supply the missing due date, since no due date was agreed. Please also supply any other outstanding information. No launch timing or completed work is assumed, and this draft is for human review before anything is sent.",
"review_flags": [
"Due date is missing and must be agreed or supplied before sending",
"Do not promise or imply launch timing",
"Requires human review before sending"
]
}
],
"excluded": [
{
"source_id": "N5",
"reason": "Stone Workshop cancelled its sample request, so no follow-up should be drafted."
}
]
}
Download the unchanged output · Download the verification script · Read the captured checks
What passed, and what still needs editing
Fourteen independent assertions passed for draft count, distinct recipients, source merging, owner and deadline handling, cancellation and review flags. They check structure and selected fields, not whether every sentence is ready to send.
The site-building assistant also reviewed the wording. North Studio's draft says “review the current draft,” although the notes do not establish that a brief already exists. Harbor Shop's draft calls a due date a “follow-up date.” Both need editing before use. The unchanged output above preserves these issues.
The recipient field names the organization, while some greetings address the internal owner. Choose the actual recipient and rewrite the greeting before copying a draft into an email.
Setup, time and cost
Recorded CLI wall time in seconds: 31.23. This excludes setup, writing the prompt and review.
Pi 1.0.0 used the configured deepseek/deepseek-v4.1-flash model through the commandcode provider. Billed cost was unavailable. Tools, extensions and project context were disabled; there was no connected mailbox and nothing was sent.
The site-building assistant prepared the fictional sample, ran Pi, wrote and executed the checks, and reviewed the output. No separate human reviewer certified these drafts. A single successful run is not a benchmark or proof of savings.
Read the run metadata · Review Pi setup and pricing → · Plan your own small-business pilot →