AI Assistant: improve ability to operate off custom terminology in a workspace

What is the challenge?	The AI Assistant is able to recognize when custom terminology is used in a workspace, but becomes confused when an existing Aha! record name is used for another record type; for example, if Aha! epics are renamed to "features" or vice-versa. If epics are renamed to features, and the user asks the assistant to create a new feature, the assistant creates an Aha! feature instead of an epic as expected.
What is the impact?	This can be confusing to users who are unable to use their custom terminology reliably with the AI assistant
Describe your idea	Improve the AI Assistant's ability to recognize custom terminology when Aha! record names are re-purposed (or ask for clarification/confirmation from the user).

What is the challenge?

The AI Assistant is able to recognize when custom terminology is used in a workspace, but becomes confused when an existing Aha! record name is used for another record type; for example, if Aha! epics are renamed to "features" or vice-versa.

If epics are renamed to features, and the user asks the assistant to create a new feature, the assistant creates an Aha! feature instead of an epic as expected.

What is the impact?

This can be confusing to users who are unable to use their custom terminology reliably with the AI assistant

Describe your idea

Improve the AI Assistant's ability to recognize custom terminology when Aha! record names are re-purposed (or ask for clarification/confirmation from the user).