Resolving a conflict

A conflict is two decisions that cannot both be true. We surface them before generation, never after.

What a conflict looks like

Guest checkout and member class history is the classic one: you cannot show someone their booking history if you never created an account for them. We show both options, the consequence of each, and a recommendation.

Picking a side

Choose an option and we apply it everywhere it touches — the data model, the roles, the affected prompts — then tell you what went stale.

1Read both options and their consequence lines.
2Pick one. The recommendation is pre-selected but never forced.
3Save the section. We mark dependent prompts and quote any refresh.
Unresolved conflicts block generation on purpose. Generating over one produces a plan that contradicts itself.
Did this answer it?
Still stuck on this? A person reads every message and replies within one working day.Contact support