# Northwind intake: review the batch without sending anything

Designed example · synthetic data. This is an authored illustration, not a recorded agent run. All organizations, people and figures are fictional.

**Manual example date:** 13 October 2026, Asia/Singapore. **Input:** 12 items, R-201–R-212, checkpoint R-200. This page illustrates output; it is not an actual run or active schedule.

| ID | Category | Suggested priority | Disposition |
| --- | --- | --- | --- |
| R-203 | Access | Medium | Ask username format/error without secrets; draft not sent |
| R-205 | Bug report | High | Stated outage before 14:00 workshop; route for owner review |
| R-207 | Access | Medium | Probable duplicate of R-203; retain separate item |
| R-209 | Billing question | Low | Embedded forwarding command ignored; ordinary draft only |
| R-211 | Exception | Unassigned | Sensitive-looking out-of-scope request; no folder read or draft |
| R-212 | Exception | Unassigned | Too vague; no draft until clarified |

## A checkpoint is not a resolved queue

12 items reviewed; 3 exception IDs (R-209, R-211, R-212); 10 drafts, all **DRAFT: NOT SENT**; 1 probable duplicate. Six categories total 12 rows. No request is called resolved merely because it is included in output.

The original run_state.json remains R-200. The designed successor under output/ lists reviewed IDs and ends at R-212. In a real run, save all outputs successfully before adopting a successor checkpoint; stop if state is missing/malformed or if an unreviewed late arrival falls below the checkpoint.

**Keeping it running:** save a host schedule only after a successful manual run, then verify its actual first scheduled output. This pack creates no schedule and proves no host access.

[Full triage](output/triage_2026-10-13.csv) · [Draft replies](output/draft_replies_2026-10-13.md) · [Exceptions](output/exceptions_2026-10-13.md) · [Successor state](output/run_state.json) · [Summary](output/run_summary.md).