interface-architecturelisted

# Interface Architecture Use when information structure, navigation, or screen priority is the design problem. Navigation is one expression of IA; work from structure first. ## Separate The Decisions Analyze separately: 1. Conceptual model: user understanding of domain. 2. Content model: objects, attributes, states, relationships, lifecycle. 3. Taxonomy: categories and grouping logic. 4. Labels: user-facing terms. 5. Navigation: movement through structure. 6. Search/browse: recovery when navigation fails. 7. Screen hierarchy: primary, secondary, supporting, hidden. 8. Wayfinding: location, origin, next actions. ## Common UI Surface Checks - Forms and transactions: object lifecycle, question order, grouping, review step, confirmation, and where users recover from mistakes. - Search and browse: query intent, result metadata, filtering criteria, sorting, no-results recovery, saved state, and reset behavior. - Lists, tables, and dashboards: comparison model, row/card identity, summary versus detail, density, grouping, and decision threshold. - Settings and admin: scope, ownership, defaults, inheritance, permission boundaries, and reversible versus irreversible change. - Content-heavy screens: purpose, source, freshness, reading order, summaries, help placement, and next action. - Onboarding and setup: prerequisite knowledge, progressive disclosure, permission timing, skip/retry paths, and handoff to the first real task. ## Diagnostic Questions - Does the structure match u