Reservations

NAC v2.4 -- strict resolution + disambiguation

Three reservations. Two share the suffix __urgent (morning + evening) so the qualifier "urgent" is genuinely ambiguous. Under v2.4 the runtime refuses to guess; it throws with structured candidates so a chat / voice / screen-reader host can re-prompt. The "lenient simulation" button below shows what v2.3 would have done: silently dispatch to the first near-match.

Acme Co -- annual review

2026-05-24 08:30 -- 10:00 (URGENT)

Hoshi LLC -- contract review

2026-05-24 18:00 -- 19:30 (URGENT)

Kawa GmbH -- discovery

2026-05-26 14:00 -- 15:00 (standard)

Simulate an agent intent

Did you mean ...