Research consensus

What the research agrees on

The most useful signal is not any one company's styling. It is the overlap between Linear, Apple, Xbox, Vercel + Geist, Shopify Polaris, Cloudflare, Cursor, and the interaction designers we studied. When several strong systems arrive at the same constraint independently, that constraint deserves more weight in Thorbis.

• Clarity before decoration. Place, state, hierarchy, and next action must be understandable before visual flourish is added.
• Progressive disclosure. Keep complexity available, but do not make second- and third-read detail compete with the first read.
• Consistency creates speed. Stable shell geometry, object silhouettes, metadata order, controls, and interaction roles become muscle memory.
• Context beats global clutter. Related information belongs near the work that needs it. The global shell stays small and predictable.
• Behavior belongs to the system. Accessibility, loading geometry, focus, keyboard behavior, semantics, errors, and responsive behavior belong in primitives and patterns instead of page-local patches.
• Actions predict outcomes. Concrete verbs, visible commit state, and consequence-aware language beat vague enterprise labels.
• State is durable. Work must survive navigation, loading, refresh, partial failure, non-color presentation, and device changes when the workflow warrants continuity.
• Density is structured, not compressed. Alignment, grouping, repetition, hierarchy, and whitespace make dense information fast to scan.
• Motion explains change. Motion preserves orientation or communicates causality. It does not compete with operational work.
• Brand restraint increases signal. Accent, imagery, elevation, and special treatment become more useful when they are scarce.
• Curation and search solve different problems. Useful subsets reduce hunting; the complete explorer remains available for precision.
• The design system is governance. Tokens, primitives, patterns, ownership, documentation, and verification prevent drift better than screenshots do.

Conflict rule

Thorbis law wins over all references. When external sources disagree about operational product grammar—shell, hierarchy, density, navigation, surface roles, keyboard behavior, or information architecture—Linear is the external source of truth. Specialist systems may strengthen their own domain, but they do not create a second shell or visual language.

What the combined research says we were still under-specifying

• Orientation is a contract. Deep records keep identity, state, primary action, and local navigation understandable as depth grows.
• Interruption recovery is part of UX. Drafts, selection, filters, upload progress, and partially completed work recover predictably when the workflow warrants it.
• Undo when safe; confirm when consequential. Low-risk reversible actions prefer immediate execution plus undo. Financial, permission, irreversible, and destructive actions require explicit consequence-aware confirmation.
• Defaults carry the product. Personalization may improve efficiency, but the default view must be complete and useful without configuration.
• Bulk work is a mode. Multi-select exposes contextual actions and consequences instead of permanently adding controls to every row.
• Content has a failure budget. Long names, missing media, malformed files, partial data, permissions, and slow networks are ordinary inputs the component must absorb.
• Every collection needs a finding strategy. Define curation, local filtering, full search, saved views, and command access deliberately instead of duplicating search boxes.

Policy: sources are evidence; the translated rules live in Thorbis. The full intake and conflict policy is documented in content/design/reference-policy.md.