Schema Preferences

Every key in design_constraints, ai_constraints, and startup_constraints (when present) MUST be an object with:

Do not write null values. Omit keys that produce no constraint.

prompt by chosen_by

design_consequence

Use the Recommendation Impact row for the selected answer from the category file when the user answered. For extracted/default/derived, use the catalog below or synthesize one sentence tied to the actual value.

Top-level shape

ai_constraints omitted when no AI artifacts. startup_constraints optional (Q27).

Constraint catalog (prompt + consequence templates)

Use when assembling Step 5. Replace [value] with the interpreted constraint.

Report consumption (appendix-config)

Generate phase reads every constraint object and renders:

Sort rows: user-answered first, then extracted, then default, then derived. Include startup_constraints when present. Rows where source starts with "default:" are unverified assumptions — render in a visually distinct style.

If legacy preferences.json lacks prompt / design_consequence (pre-schema-extension runs), fall back to the catalog table above keyed by constraint name — do not leave the appendix empty.

Validation (Clarify Step 5 self-check)

Before marking Clarify complete:

1. Every written constraint has value, chosen_by, prompt, and design_consequence.
2. No empty strings for prompt or design_consequence.
3. question_id present when the constraint maps to a catalog question.
4. source present on every constraint where chosen_by is "extracted" or "default". Omit for "user" and "derived".