Aglet

Learn from multi-index search scope confusion

A scope lesson should preserve which result type changed the search job and where the route failed to explain it. Compare later route and broad-search journeys with the original provenance table, then improve one review prompt about index meaning, visibility, or broadening.

Keep the lesson for the next incident

  1. Keep the route promise

    Record entry route, query, index, result type, label, visibility context, rank, and destination. State what a person expected to find. This keeps a scope decision from being reduced to “mixed results felt confusing.”

  2. Compare later contexts

    Review another route, explicit broadening action, and direct link after the change. Look for an index that remains unlabeled or a result that crosses contexts unexpectedly. Preserve a successful scoped path as a control.

  3. Refine one scope check

    Require future reviews to trace provenance, test a broadening choice, and inspect an excluded index. Assign ownership and revisit date. Define the observation that would show the check prevented a wrong-context result or an ambiguous destination.

What to carry forward

The learning record connects one mixed-index confusion to later route evidence and a reusable provenance check. Stop when another reviewer can apply it to a new surface. Carry forward uncertainty where access, ranking, or index ownership is not fully observable.

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