Honest states: loading, empty, error, success

A design principle we hold to: nothing is fire-and-forget. Loading, empty, error and success each say what actually happened.

Empty states teach the interface — they tell you what would appear here and how to make it appear. Error states name the failure and offer the next step. The tool disappears into the task instead of hiding its own state behind a friendly veneer.

Transparency is the product, not a feature.