Build a useful investigation brief
Build an empty-state matrix
List page, role, project, filters, data presence, processing state, lifecycle, and rendered heading, copy, and links. Mark branches that currently share a message despite different user decisions.
Trace the decision path
Follow query construction, policy result, record loading, view branch, and link target for each state. Identify where information is discarded or where a generic fallback replaces a known cause.
Test neighboring states
Compare one matching record, one filtered-out record, one pending record, and one unavailable scope where safe. Check whether clear filters, setup, wait, or access language matches the evidence.
What to carry forward
The brief should identify the empty branch that loses meaning, its query or policy boundary, affected contexts, and proposed copy decision. Conclude data absence, filter handling, setup state, delay, access, or unresolved. Trace query parameters, scoped associations, lifecycle flags, policy checks, and presenter branches, then compare one known record and one filtered-out record with the empty response.
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