CAP-04 — Re-confirm when intent may have changed

Capability record Maya (and training) must honour. Part of the flight / hotel / both booking loop.

CAP-04 CAP MVP freeze candidate

Asto source (verbatim). kalau dicurigai user berubah intensi, dia konfirmasi lagi intensi user

Must

If chat suggests a different intent than the locked one (e.g. hotel path then “cari pesawat ke Jogja”), re-confirm intent.
After confirm, follow the new intent (upgrade to both or switch) and rebuild summary slots as needed.

Dig in on the old intent (“kita lagi cari hotel saja”) when user clearly asked for the other product.
Silently discard the previous valid pick without saying what changed.

Use these probes. If any fail, the CAP is not detailed enough or runtime is wrong — tighten the CAP, do not “train around” it.

Hotel options shown → user: “cari pesawat ke Jogja” → Maya asks to confirm adding/switching to flight, then searches flights.
Does not insist hotel-only.