START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

S05: Check that emails and attachments were filed
Starter kit
Status: Proposed / not tested

PURPOSE
Day-end or post-filing check → compare the selected-for-filing register with actual communication and attachment records → unfiled/pending/missing-attachment/wrong-matter exception queue.

PREREQUISITES
1. Existing authorized Clio/Outlook add-in or equivalent DMS; deidentified message IDs, approved matter IDs, attachment manifest and filing status. Manual check is enough. No new OAuth installation or actual client uploads are part of this recipe.
2. Synthetic files first. Real use requires firm-approved access, privacy, processing terms, retention controls, export coverage and a named reviewer.
3. Prepare any required original files or rendered evidence separately. This kit does not configure accounts, connectors or live actions.

FILES AND FORMATS
selected-emails.csv: message_id, approved_matter_alias, expected_attachment_ids, selection_time
filed-records.csv: message_id, matter_alias, attachment_id, filing_status, observed_at
scope.txt: approved sync interval and export cutoff

Files without .example are blank input worksheets; CSV templates contain headers only. .example files contain invented records for the dry run. Text input .txt files contain blank labeled fields. Use the original base filename when supplying an example to the prompt, or explicitly map the example filename to that input. CSV files are UTF-8 with comma delimiters, quoted fields where needed, and CRLF row endings. Preserve identifiers as text when importing into Excel. Blank means missing or unresolved, never a zero or a pass. Multi-value fields use a pipe only where the fixture scope says so.

SETUP AND DRY RUN
1. Copy this kit to an approved working folder. Keep examples separate from any real exports. Do not upload client, privileged, personal, credential or financial-account data to an unapproved service.
2. Read the .example text policy/scope files and all .example.csv inputs together. They define this fixture only. For a real pilot, fill the blank templates from approved exports without changing headers and obtain approved policy values.
3. Use native read-only exports, exact joins and arithmetic for deterministic checks. This kit includes no executable automation, OAuth setup, live-action instructions or importable Make blueprint.
4. Give only the approved prepared inputs to a firm-approved text assistant and use the recipe prompt below. Keep source IDs, source row numbers and unresolved evidence visible.
5. Compare the proposed result with expected-fixture-result.txt. Verify every listed issue and that the prompt invents no missing evidence. The expected file describes assertions, not a performed workflow run.
6. Have the named reviewer check source evidence and record remaining questions before any separately authorized action.

RECIPE PROMPT
Compare these deidentified selected-email and filed-record manifests. Verify matter ID, message ID and expected attachment IDs. Treat ‘Not yet filed’ as pending, never success. Flag missing attachments, mismatches and duplicates with source rows. Do not infer a matter from a name, refile, create time entries, delete originals or forward mail. Return an exceptions queue for staff.

INPUTS
selected-emails.csv: message_id, approved_matter_alias, expected_attachment_ids, selection_time
filed-records.csv: message_id, matter_alias, attachment_id, filing_status, observed_at; scope.txt: approved sync interval and export cutoff

OUTPUT
filing-review.csv: message_id, approved_matter_alias, observed_matter_alias, status, missing_attachment_ids, evidence_rows

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.

REVIEW CHECKLIST
[ ] Headers match the exact input schema and the export covers the stated scope
[ ] Synthetic example files were used alone for the first dry run
[ ] Every output finding retains its original source ID/row/page reference
[ ] Missing keys, contradictions, unavailable originals and ambiguous dates remain unresolved
[ ] Every expected fixture finding is present; no live action or unsupported result is claimed
[ ] Responsible reviewer checks the original records before a real deployment

RECIPE-SPECIFIC REVIEW
Staff confirm original records inside the secure systems. Turn off unintended automatic time-entry behavior during an approved pilot. Test delayed sync and a thread where only one of two attachments was selected.

VALIDATION
Exact CSV header order, field counts, serialized round-trip values and fixture semantics were checked during kit preparation. This does not test OCR, a vendor integration, a model response or end-to-end reliability. All data and identifiers are synthetic. Dates are fixed fixture dates, not current monitoring results.