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. S22: Build a closed-file archive manifest and retrieval-check queue Starter kit Status: Proposed / not tested PURPOSE Attorney approves administrative closeout or archive retrieval review → compare approved closeout inventory with archive metadata and staff-supplied sample retrieval evidence → searchable archive manifest and missing-item/retrieval-exception queue. PREREQUISITES 1. Pseudonymous matter ID, closeout approval reference, expected file/physical-original inventory, immutable file IDs, size/hash/location, physical box locator, attorney-supplied hold status and next review date, access owner and actual retrieval-check results. IT supplies hashes; staff performs any authorized retrieval. No retention periods inferred. 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 closeout-inventory.csv: matter_alias, closeout_approval_ref, item_id, item_type, expected_size_bytes, expected_sha256, hold_status, approved_next_review_date, access_owner archive-manifest.csv: matter_alias, item_id, size_bytes, sha256, archive_location, physical_box_locator, source_ref retrieval-checks.csv: matter_alias, item_id, checked_at, retrieval_result, observed_location, evidence_ref scope.txt: inventory cutoff and sampled retrieval coverage 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 an advanced local snapshot helper. It requires authorized IT review and a synthetic validation before use; it was statically reviewed but not runtime-tested. Follow START-HERE.txt for its fixed-drive, stable-snapshot and secret-exclusion limits. 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 this approved closeout inventory with archive manifests and actual retrieval-check records. Preserve file IDs, hashes, locations and physical-original locators. List missing expected items, count/hash discrepancies, failed sample retrievals and missing hold or review-date metadata. Do not declare an archive complete from hashes alone, change permissions, move or delete files, decide retention obligations or recommend destruction. Produce a human-review queue. INPUTS closeout-inventory.csv: matter_alias, closeout_approval_ref, item_id, item_type, expected_size_bytes, expected_sha256, hold_status, approved_next_review_date, access_owner archive-manifest.csv: matter_alias, item_id, size_bytes, sha256, archive_location, physical_box_locator, source_ref retrieval-checks.csv: matter_alias, item_id, checked_at, retrieval_result, observed_location, evidence_ref; scope.txt: inventory cutoff and sampled retrieval coverage OUTPUT archive-review.csv: matter_alias, item_id, expected_item, archived_location, hash_size_check, retrieval_result, physical_original_gap, hold_status, approved_next_review_date, source_ref, review_action. No deletion or retention decision. 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 Records owner checks originals and sampled retrieval; attorney determines hold/retention requirements. Test a readable archive missing an expected physical original and an index pointing to a moved location. Distinct from S13 infrastructure backup coverage: this is matter closeout inventory and later findability. 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.