Research brief

Operator surface model: decisions on home, orientation on /state

working model

model Home handles decisions. /state handles orientation.

This split reduces mixed-purpose clutter and lets each page optimize for one job instead of three.

recommended path Keep the split and keep the presentation compact.

The right improvement loop is clarity and trust, not adding more decorative surface area.

Why this exists

Underlying design logic

home route Best for requested action.

The home page is the natural place for Derek-facing asks because it is primary, shallow, and easy to revisit.

state route Best for passive understanding.

/state works when Derek wants a quick answer to “what's the current posture?” without being forced into a decision at the same time.

brief links Best for depth on demand.

Research briefs stop the cards from bloating while still making the relevant context obvious and one click away.

design constraint Keep it dashboard-like, not promotional.

The surface should feel like an operator console: compact, calm, and high-signal, with enough contrast and hierarchy to scan instantly.

Success criteria

Ask clarity Derek can tell what is being requested without reading the whole card.
Reason clarity Derek can tell why the decision matters without opening extra links.
Option clarity Buttons explain the practical meaning of each path.
Depth clarity If Derek needs more context, the brief link reads as obviously relevant and worth clicking.