Decide where the work belongs
Classify the blank state
Put missing project, missing setup action, missing test key, failed built-in check, and intentional no-work state into distinct queues. Elevate a blank page that offers no safe action or loses the project context. Preserve permission restrictions as a separate boundary.
Describe observed scope
Record workspace age, project age, role, browser, viewport, setup progress, and the sample check result. Count only reproducible fixtures or identified reports. If established-project usage is unknown, do not imply all empty projects are onboarding failures.
Select the next action
Prefer one clear, reversible action: create the project, open setup, create a test key, or run the built-in check. Explain the result expected from that action. Avoid suggesting customer data or production credentials for a first-use path.
What to carry forward
Queue a blank new project with no actionable next step above an intentional empty project that already explains how to proceed. Include the project state, role, safe action, observed scope, owner, and evidence that would show the issue is resolved.
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