Aglet

Verify multi-index search scope across entry contexts

Verification should prove that each search entry includes the intended indexes and explains any broader result set. Test product, help, project, and account examples from their own routes, then check broadening and direct links. Keep access and ranking claims bounded to observed contexts.

Check whether the outcome improved

  1. Check route-specific search

    Search from each intended entry point and confirm result types, labels, order, and destination fit its job. Record an excluded index and verify it stays out. Do not rely on a shared query alone to prove scope.

  2. Check explicit broadening

    Use the available all-content or broader search action and verify the URL, grouping, labels, and result context change together. Ensure a person can return to the original scope without losing the query or selected filters.

  3. Review visibility and recovery

    Test an inaccessible or unavailable record context without exposing private details. Inspect empty, error, narrow, and direct-link states. State tested indexes and roles; leave unverified contexts outside the closure claim.

What to carry forward

Verification passes when route scope, result labels, broadening, and destinations agree for tested indexes and contexts. If access or one result family is untested, document the boundary. A single blended list cannot prove that every index is appropriately scoped.

Technical background: Digital.gov guidance.

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