Form field reduction analysis

You are auditing a form for unnecessary friction.

FORM PURPOSE: {{FORM_PURPOSE}}
FIELDS (name, type, required or optional): {{FIELD_LIST}}
WHAT HAPPENS AFTER SUBMISSION: {{POST_SUBMIT_PROCESS}}
WHO USES THE DATA INTERNALLY: {{INTERNAL_CONSUMERS}}

For each field, decide one of: KEEP (needed to fulfil the action), DEFER (collect later in onboarding or by enrichment), MAKE OPTIONAL, or CUT.

OUTPUT a table: Field | Verdict | Reason | What breaks if removed | Who to check with before removing.

Then output:
- A recommended minimum viable version of the form, listed in the order the fields should appear.
- Any field that should be split or combined, and why.
- Fields where an inferred or enriched value could replace user input.

Constraints: do not recommend removing a field that is legally or operationally required if I have said it is used internally - instead recommend deferring it. Do not suggest progressive profiling as a blanket answer without saying which specific fields move to which later step. If you cannot tell whether a field is needed, ask the question rather than assuming. No em dashes in the output.