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.

G12 - Draft conditional forms from approved questions
Status: Proposed / not tested

WHAT THIS KIT DOES
Provides exact-header blank CSVs, separate fabricated examples, required text-input scaffolds, and expected output examples for one offline review. It does not configure an integration or run a workflow.

PREREQUISITES
1. Approved script by practice area, field dictionary, Lawmatics form editor, legal/data-minimization review and synthetic personas. The person selects a practice area; AI does not diagnose it.
2. Use synthetic inputs first. Real records require firm-approved access, processing terms, retention, and confidentiality controls. IDs alone do not anonymize a record.
3. Verify product plan, available exports, coverage, and the named reviewer. The prompt does not configure an integration.
Name a reviewer and keep actual prospect/client data within firm-approved systems. IDs alone are not anonymization.

INPUTS
- approved-script.csv: question_id, exact_wording, answer_type, required, approved_branch_rule, practice_area
- field-dictionary.csv: field_id, type, persist_in_crm, allowed_values; policy.txt: unknown handling, help route, approved disclaimer

OUTPUT SHAPE
form-spec.csv: question_id, exact_wording, field_id, field_type, required, branch_rule, persistence; branch-tests.csv: test_id, input_answer, expected_path, unresolved_rule

SETUP AND FIRST TRIAL
1. Keep the original exports unchanged. Copy this kit into an approved working folder.
2. Start with only the files ending -example. They contain fabricated data. CSV files without -example contain headers only; text inputs without -example contain empty preparation scaffolds.
3. For the synthetic trial, copy each example into a separate trial folder under its canonical input filename. Do not mix example rows with real exports. Supply the matching example policies too. Output examples are for comparison after drafting, not evidence inputs.
4. Import CSVs as UTF-8 comma-delimited data. Preserve identifiers as text and date/timestamp strings in their specified ISO format. Boolean examples use true/false. Empty cells mean unknown or not supplied, never automatic zero/no. Amounts are numeric; use the stated currency and do not combine currencies. No formulas or macros are included.
5. Paste starter-prompt.txt into the firm's approved assistant with only the input files. A staff member can also perform the comparison in a spreadsheet. No account connector is needed for this file-based trial.
6. Check the draft against fixture-expectations.txt and the matching output examples. Use exact arithmetic in native spreadsheet tools or code and inspect source IDs manually. An AI response has not been run or validated for this kit.
7. Resolve missing policies, uncertainty, permissions and coverage with the named reviewer. Live platform configuration, messages, uploads and other changes require their own approval and testing.

FIXTURE TARGET
Q1/Q2 wording is preserved. Yes shows Q2, no skips it, unknown remains an unresolved branch routed to human help, and skipped required Q1 requires assistance. Q2 stays form-only.

LIMITS
- Do not collect identification, health or financial details prematurely; avoid unknown-to-false coercion; provide a human assistance path and lawyer-reviewed relationship disclaimer.
- Only file/header and synthetic fixture consistency are checked. No workflow, connector, AI response, product feature or integration is tested.
- Every example is fabricated. IDs alone do not anonymize actual firm data. Use approved minimized data, access, processing terms and retention controls.
Source-policy text scaffolds are not legal advice or production configuration. No real review link, phone destination, contact address, API token or credential is included in examples. example.invalid and fixture: references are deliberate non-live placeholders.

SOURCES
Pain evidence: Public discussion: https://www.reddit.com/r/LawFirmMarketing/comments/1wub11m/comment/pd1q2lg/
Method: Lawmatics form objects and conditional blocks: https://help.lawmatics.com/en/articles/10699854-create-objects-from-custom-forms-advanced-options
Method: Lawmatics form objects and conditional blocks · supporting guide 2: https://help.lawmatics.com/en/articles/10699895-standard-blocks-vs-relationship-blocks

VALIDATION SCOPE
Header and fixture validation passed; workflow not tested. Read the exact checks and limits in fixture-expectations.txt.
