Establish what is happening
Capture result provenance
Record query, route, index, result type, visibility context, rank, label, and destination for representative rows. Include one result from each intended index and a record that should remain outside the surface. Keep access context explicit.
Compare result promises
Ask what each index helps a person do and whether one ranking model can explain the combined order. Compare product, help, project, and account meanings. A shared keyword does not make records interchangeable.
Set a scope boundary
State which indexes belong in each entry context, how result types are grouped, and what broadening action is available. Preserve an out-of-scope control. Stop when another reviewer can explain inclusion, exclusion, and destination from the route contract.
What to carry forward
The triage output is an index scope decision with result types, context, visibility, and broadening rules. Stop when intended and out-of-scope records are distinguishable. If access or relevance evidence is incomplete, keep the mixed result provisional instead of blending by default.
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