Keep the lesson for the next incident
Record the term boundary
Keep the literal phrase, alternate phrase, scope, successful examples, and exclusions. Note whether the gap came from catalog naming, locale, abbreviation, or indexing. A clear boundary is more reusable than a list of accepted words.
Revisit later evidence
Compare new searches, reformulations, and false matches after the mapping or content change. Look for a product family that diverges from the original pattern. Treat a new match as a prompt to inspect context, not automatic proof the rule should expand.
Refine one review habit
Choose one durable improvement: collect negative controls, ask for locale, compare product-family overlap, or require a scoped example before approval. Assign a reviewer and revisit date. Keep the historical mapping visible so the adjustment can be judged fairly.
What to carry forward
The learning output ties a term pair to later evidence and one repeatable vocabulary-review change. Stop when the next reviewer knows which positive and negative examples to collect. Preserve uncertainty for aliases whose meaning still depends on category, locale, or product context.
Technical background: GOV.UK developer documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow