HivemindOS UI Rules

These are the short rules. For the full rationale and screen guidance, see UI/UX Philosophy.

1. Simple first. Depth on demand.
2. Every screen answers: what is happening, what needs attention, what is the next safe action?
3. One card = one main job.
4. Primary UI uses plain language.
5. Advanced settings stay behind disclosure.
6. Keep logs, raw JSON, keys, endpoints, and runtime internals out of default views.
7. Money-moving actions are separated from read-only status.
8. Show machine context before agent details.
9. Show swarm coordination with attribution.
10. First-time users should understand the screen in ten seconds.