Not just a screen list anymore. A reviewable wireframe map.
Each screen now includes a real structural prototype: what appears on it, in what order, what is authoritative, which states must exist, and what the team should review before high-fidelity design.
A decision prototype before final UI
Structural decision prototype: section order, hierarchy, content responsibility and key states are mapped from the approved blueprint. It is not the final visual UI.
Every Screen Blueprint answers the questions we need before implementation
What is this screen for? Which sections appear, and in what order? What is configuration-driven? Which states must be designed? Which domain/API owns the final truth? The library becomes an approval tool, not a passive inventory.
Structure
Visual order of the sections inside the screen.
Responsibility
The domain or source that owns the final decision.
States
Loading, empty, full, race, failure and other screen-specific states.
Discussion
Clear points to review and approve before high fidelity.