Recommendation: yes. Keep it as a read-only snapshot and avoid mixing live decision capture into it.
Research brief
What /state should do — and what it should not do
The route is useful when it explains the operating picture quickly and stays out of the way of the decision inbox.
Analysis
Why the separation matters
Derek benefits from a quick status surface, but that surface gets muddy if it also becomes the place where new decisions arrive.
Home can be optimized for action. /state can be optimized for passive understanding and health checks.
The top section clarifies what /state is for, why it exists, what the current operating posture is, and where to read the deeper design rationale.
If the route feels too dense even after the clarity pass, the right move is to remove blocks rather than collapsing the purpose back into home.
Options
What the choices mean
- A — Keep /state as the orientation page Preserve the route as the compact place to understand the operating picture.
- B — Keep it, but trim it harder The route is useful, but it should show fewer supporting blocks or even shorter copy.
- C — Hide it from main navigation Keep /state available, but do not surface it as a primary navigation destination.