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.

Check the signed-client handoff
Starter kit G09

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
handoff.csv: intake_alias, firm_acceptance_approved, conflict_check_status_supplied_by_staff, required_field_values, source_status
field-map.csv: source_field, target_field, source_type, target_type, required, overwrite_rule
sync-results.csv: intake_alias, sync_run_id, destination_matter_id, destination_status, field_name, observed_value; use synthetic records only for first tests

RECIPE-SPECIFIC SETUP
required_field_values contains a JSON object encoded as one CSV cell. Import with CSV quoting intact, then parse that field as JSON. Every name and value is synthetic. Signed status alone is not firm acceptance or conflict clearance. No API calls or synchronization are included.

PREREQUISITES
- Lawmatics and Clio Manage subscriptions, administrator-approved integration, firm acceptance gate, field-type mapping, destination IDs and sandbox records. Optional document sync must be explicitly scoped.
- Start with synthetic data. Real firm data requires approved access, processing terms, retention, and confidentiality controls. Replacing names with IDs alone does not anonymize a record.
- Verify the current account, plan, export scope, and approved reviewer before trying the documented product feature. This prompt works on prepared files; it does not install or configure an integration.

REVIEW CHECK
Human acceptance/conflict clearance is required. Check overwrite behavior, relationship mapping, destination status and file permissions; resync behavior must be tested before production.

EXPECTED OUTPUT
handoff-review.csv: intake_alias, check, source_value, destination_value, status, evidence_rows, owner; plus a single-sync/resync test plan

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