Aglet

How to triage the empty state for a first project

An empty project can be healthy first use or a failed redirect, so triage must compare durable project state with the page’s next action. Record whether the workspace is new, whether a test key exists, and whether the built-in check is available. Keep an empty result separate from a missing project.

Establish what is happening

  1. Record the empty surface

    Capture the workspace and project names using synthetic fixtures, page heading, visible actions, setup progress, role, and any empty-state explanation. Note whether the project was just created or is an established project with no work. Avoid treating a blank chart or list as proof of missing data.

  2. Follow the first action

    From a new project, use the offered setup action, create a non-production test key, and reach the built-in check. Record each redirect and saved state. Compare owner and restricted-role views so hidden actions are not mistaken for a broken empty state.

  3. Compare expected evidence

    Check whether a completed built-in check creates the labeled sample Signal and linked Work Item described by setup. If the project remains empty, capture request, response, and status. Mark unknown external or producer behavior separately from the local sample path.

What to carry forward

Triage is complete when the blank surface is tied to a project state, role, setup step, and visible next action. Classify it as intentional empty, missing guidance, failed creation, or unknown only after comparing the page with authorized synthetic records.

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