Decide where the work belongs
Classify context harm
Elevate cross-workspace record or write evidence above a duplicated workspace label. Treat a blocked member, stale link, missing membership, and similar-name confusion as different queue types. Record whether the user can confirm context before an irreversible or consequential action.
Bound the affected route
List workspace count, membership role, route, link age, browser, and action attempted. Use synthetic fixtures or identified reports only. Do not infer tenant-wide exposure from a single display issue; state the exact records and routes observed.
Choose safe recovery
Prefer an explicit workspace heading, selected context, and a safe unavailable or reselect action for stale links. Avoid silently switching to a default workspace. Assign isolation findings to the existing authority owner and navigation findings to onboarding or shell ownership.
What to carry forward
Queue any wrong-context read or write first, followed by blocked access, then label and navigation confusion. Include route, membership, workspace fixture, safe recovery, owner, and the test evidence required to reduce the queue risk before closing.
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