Ops Route Shell

Public operations shell is route-ready, not action-ready

This shell keeps operations language in a review-first posture: visible handoff points, explicit fallback, and no unsupported control claims.

/ops/

Operations room with monitoring dashboards

Shell Readiness Checklist

/ops route family

  • Shell exists for `/ops` and `/ops/` with explicit legal-safe language.
  • Any nested `/ops/*` path returns the same shell shell snapshot for demo/handoff continuity.
  • Blocked states point users to support/docs/admin request path, not unsupported ops control claims.
  • Route claims are aligned to `requires-evidence` until Team 1 and Team 3 mark them release-ready.

Blocked-path handoff

For unresolved filing, legal drift, or connector state mismatch: route to /help/ and then to controlled escalation.

Evidence mode

Any operational claim stronger than review-first wording must remain in requires-evidence state.

Release posture

This shell is requires-deploy until production routing for `/ops` and `/app` has passed review-first review in Team 1 packet.