Keep the lesson for the next incident
Keep the value path
Record the product example, source attribute, index response, facet label, and query scope that shaped the finding. Note where evidence was unavailable. This turns a one-off missing value into a traceable example for the next taxonomy review.
Compare later coverage
Recheck neighboring values and another category after the change. Look for a new omission caused by the same field, limit, or scope rule. Treat a single repaired value as local evidence, not proof the attribute is now complete everywhere.
Change one review prompt
Add a source-backed representative product, a null case, and a neighboring category to future facet reviews, or require scope notes before approval. Assign ownership and a review date so the adjustment can be evaluated instead of becoming a checklist slogan.
What to carry forward
The learning record should connect one facet gap to a repeatable source-to-render review adjustment. Stop when another reviewer knows which positive, null, and neighboring examples to test. Carry forward uncertainty where attribute coverage depends on category, locale, or index freshness.
Technical background: Adobe 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