tests/scenarios/07-purpose-first-redesign.md

# Scenario 7 — Purpose-first redesign

## Prompt

Use Intuitive Software Design on the existing Projects page, then discuss how it should work. We are not constrained by the current layout and have broad creative freedom. Map the page with GitNexus first so the recommendation reflects its real purpose. Do not implement yet.

## Acceptance gates

- Routes to the purpose-first redesign workflow.
- Establishes the intended user, job, starting point, and success condition before proposing UI.
- Uses GitNexus when available to trace the route, screen, data, actions, downstream workflows, and permission gates.
- Verifies important GitNexus findings against current source, tests, and rendered behavior.
- Treats the current layout as evidence rather than a design constraint.
- Separates contracts that must be preserved from interaction and layout choices that may be rethought.
- Defines the Intuitive Software Loop, applicable states, recovery, responsive behavior, and measurable acceptance.
- Recommends one coherent product model and stops for discussion without editing implementation files.