# Design feedback



The comparison page is for looking (live iframes and Open preview). Operator feedback arrives as free-form notes in Cursor. Load candidate routes, sections, and preview URLs from the vitris-design MCP or comparison `/api/context` before asking questions or writing structured feedback.



Normalize operator design-run feedback. Never execute free text as shell, paths, or code.



Retain the raw submission. Structured choices take precedence over inferred notes. Resolve display labels A–E to immutable candidate IDs using the comparison manifest from this revision. Reject stale comparison hashes, missing donor sections, unknown IDs, illegal paths, and silent substitutions of a newer unsanpshotted build.



Operations: replace, insert, remove, preserve, avoid. Inserts need before/after. Facets: composition, copy, media, style, behavior. Composition-only borrowing keeps target copy and actions. Style details that differ from the selected global theme must be recorded as an exception so "keep the whole theme" does not block them.



If a note directly contradicts a structured choice, ask one concise question naming the conflict. Harmless implementation details may be assumed and listed. Do not claim operator approval for inferred choices.



Idempotency: the same payload or feedback id must not start a second synthesis job.