Aglet

What to learn from a workspace context checklist

The lasting lesson from switching confusion is a context contract that stays visible from workspace selection through project, Signal, Work Item, and create routes. Preserve two-workspace fixtures with distinct records so future navigation changes are tested for both comprehension and tenant isolation.

Keep the lesson for the next incident

  1. Write the context contract

    Define how active workspace is shown, selected, carried through routes, and handled when a link is stale or membership is missing. State that reads and writes must remain scoped. Keep role-specific actions and fallback rules explicit rather than relying on a default context.

  2. Keep switching fixtures

    Save synthetic traces for normal switch, similar names, project deep link, unavailable workspace, back navigation, refresh, restricted role, and authorized create. Assert heading, route, record scope, action destination, and safe failure without storing session secrets.

  3. Define recurrence signals

    Reopen review when a page hides active context, an old link selects a default workspace, a record crosses scope, or a write lands in the wrong tenant. Record role, parallel-tab, and narrow-layout limits and assign owners for isolation and navigation findings.

What to carry forward

Close learning with visible context rules, tenant-scoped fixtures, stale-link recovery, and recurrence triggers. Treat navigation as healthy only when the rendered context and durable record scope continue to agree after interruption with test evidence attached.

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