When Ambiguous Intents Are Identified, Ask the User to Choose the Expected Intent

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Note

Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.

GitHub Issue Description (verbatim)

Issue #243 (no parent):

example: for change work location there are two transactions but by default it is considering permanent work location and it is happening same with adding a contact

No Acceptance Criteria, Expected Business Value, or further scope exists beyond this — stating that fact rather than inventing them.

Possible related PRD content (not confirmed as the same item)

This issue's example ("Work Location change" being ambiguous between two transactions) matches Feature 2 in scratch-pad/q3-prds/Nova_Core_HCM_known_Enhancements.docx, verbatim:

Feature 2 — Transaction granularity & disambiguation — Review the transaction catalog and refactor the ambiguous and overlapping entries into a crisp, mutually distinct set. "Work Location change" is the motivating example — the kind of definition that means different things in different contexts and leaves both the agent and the user guessing. The output is clear names, scopes, and required inputs per transaction, so routing and user choice are unambiguous.

Deliverable of this stage: a reviewed transaction taxonomy — the target set with the merge/split decisions and clear definitions — not the refactor itself.

Stated as a possible match, not a confirmed one — the GitHub issue itself doesn't link this PRD.

Sources

• GitHub issue #243
• Possible match: Nova_Core_HCM_known_Enhancements.docx, Feature 2 (not confirmed)