Check whether the outcome improved
Check category entry
Open a category path, use its search field, and compare results with the breadcrumb and category filter. Confirm expected inclusions and exclusions. Record how an empty phrase behaves and whether the route explains what will be searched.
Check global expansion
Run the same phrase globally and use any broaden action from category results. Verify the URL, scope label, facets, and result types change together. Ensure a global result does not appear while the interface still claims strict category scope.
Review direct and narrow paths
Open category and global URLs directly, paginate, sort, and inspect narrow layout. State tested categories and omitted route rules in the closure. Leave one path partial if the product has not defined its scope contract.
What to carry forward
Verification passes when category and global routes return understandable scopes, labels agree with results, and broadening is intentional. If empty phrases, direct links, or one device layout remain untested, document that boundary rather than claiming every route is consistent.
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