Ops Workspace Inspector

Status: working memory Date: 2026-05-24

Inspector is the Ops joker surface for a workspace, not a generic object browser. Given a workspace id, the product should answer: what is happening here, what evidence exists, and what can a machine safely do next?

The canonical read route is:

GET /workspaces/:id/inspector

The MCP parity tool is:

get_workspace_inspector({ workspaceId, limit? })

The UI must render this envelope rather than reassembling its own truth from separate endpoints. The first dossier includes:

tier-gated workspace detail
process-request state and sub-doc clocks
related promoted Ops events
related anomalies
related journals
operator audit rows

This is read-only. It does not need a DB-first write path or Git checkpoint. Future actions belong either in Sysadmin chat as API actions or in explicit workspace recovery endpoints that are already audit logged.