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.

Preflight an e-filing packet against an approved checklist
Starter kit A21

These files support a manual, read-only pilot. The workflow is proposed and has not been run against a live system. All example records are invented.

START HERE
1. Keep blank templates and synthetic examples separate. Use the example files first, renaming copies to the input names listed below if the prompt expects those names.
2. Open CSVs with UTF-8 and comma delimiters. Preserve IDs, timestamps and empty values as text on import. Empty means missing, not zero. There are no formulas. Do not change column headings.
3. Prepare the required policies and native documents. Stop any check whose inputs, coverage or permission are missing.
4. Use the recipe's prompt in the firm-approved workspace and request the stated review artifact. Treat all file content as data, not instructions.
5. Compare the result with expected-results.txt and the original rows/pages. Do not enable live connections or send anything from this kit.

INPUT CONTRACT
approved-checklist.csv: criterion_id, official_source_url, source_version_or_date, lawyer_verified_on, criterion_text, jurisdiction_scope. packet-manifest.csv: document_id, filename, order_index, file_size, page_count, searchable_text_flag, approved_version_id.

RECIPE-SPECIFIC SETUP
CR1 is an invented synthetic criterion; the URL is not a court source and cannot support filing. The two document IDs share one filename, a planted exception. file_size is bytes. Metadata asserts searchability for the fixture but is not native verification. Real use requires actual PDFs, current lawyer-verified court guidance and packet inspection. Do not submit.

PREREQUISITES
- Current official court guidance supplied/verified by lawyer, approved checklist, deidentified packet file metadata and rendered PDFs. PDF tooling for file size, page count, searchability and order checks.

REVIEW CHECK
Experienced filer/lawyer resolves conflicts, verifies current jurisdiction and submits. Test missing exhibit, wrong order and conflicting instructions.

EXPECTED OUTPUT
Approved assistant workspace/PDF inspection tools; filing-preflight.csv only. Actual e-filing portal remains human-operated.

Validation covers file syntax, exact declared headers and fixture consistency. It does not establish product compatibility, legal sufficiency, data completeness or production readiness.