# Vecreal Operating Principles

Source: section 07 — Design system principles.

These principles are the compass for Vecreal product UI. They are calibrated for intelligent, premium, and approachable software: useful under pressure, restrained in tone, and clear without being simplistic (source: section 07 — Design system principles).

## The 10 Principles

1. Coordination layer, never replacement (source: section 07 — Design system principles)
2. Show your work (cite every synthesized claim) (source: section 07 — Design system principles)
3. Honest counts, honest confidence (source: section 07 — Design system principles)
4. Tools, not apps (density > impact) (source: section 07 — Design system principles)
5. Status describes the thing; trend describes change (source: section 07 — Design system principles)
6. Compose, don't invent (source: section 07 — Design system principles)
7. Order by priority, not by status (source: section 07 — Design system principles)
8. Tokens are the source of truth (source: section 07 — Design system principles)
9. The dot is sacred (brand mark consistency) (source: section 07 — Design system principles)
10. Quiet expert, not loud thought leader (source: section 07 — Design system principles)

## Rationale

The principles answer questions the component library does not answer directly. Tokens can be tuned and components can be extended, but principles stay stable unless the owner explicitly changes the direction (source: section 07 — Design system principles).

## Calibration Anchors

- Intelligent means the UI shows reasoning, cites sources, and calibrates confidence (source: section 07 — Design system principles).
- Premium means the UI feels restrained, precise, and like professional infrastructure (source: section 07 — Design system principles).
- Approachable means the UI uses direct microcopy, clear affordances, and no gatekeeping (source: section 07 — Design system principles).

## Conflict Resolution

Use this order when there is tension: principles first, then tokens, then components, then one-off judgment. A one-off surface does not get to override the principles. Escalate the principle itself if the system direction truly needs to change (source: section 07 — Design system principles).

## Things That Break The Feeling

Avoid heavy drop shadows, loud color everywhere, cluttered density, default browser button styles, inconsistent spacing, stock UI patterns, decorative animation, emoji in UI labels, gradient backgrounds, AI sparkle loaders, and broad settings panels that feel like every possible feature was added (source: section 07 — Design system principles).
