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 PDF-to-Word conversions
Starter kit A01

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
Files: source.pdf, converted.docx, converted-render.pdf; intended-changes.csv columns change_id, source_locator, expected_change. Each file uses the same document_alias.

RECIPE-SPECIFIC SETUP
Required native files are not supplied as fake PDFs or DOCX files. Use document_alias SYNTHETIC-DOC-1 throughout. Create source.pdf and converted.docx from the two synthetic text fixtures, then render the converted DOCX to converted-render.pdf in Word. Keep the originals. The CSV only records an intended heading change. Visual page checks remain required.

PREREQUISITES
- Word desktop; Acrobat Pro or approved PDF/text comparison; source PDF, converted DOCX, document ID, an explicit list of intended changes; approved AI only for explaining detected differences.
- 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
Staff inspect every unexplained text difference and visually check all pages; attorney signs off on substantive differences. A planted dropped clause and changed number must both be caught.

EXPECTED OUTPUT
Approved assistant workspace for difference explanation; Acrobat/Word desktop for native comparisons and rendering. Export qa-findings.csv with document_alias, source_locator, converted_locator, difference_type, expected_change_id, reviewer_status.

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