What problem does it solve? Analysts working in a Seshat workspace need to see readiness by stage, tables, turns, and pending human approvals without reading raw state files or terminal output, and without any tool that could silently grant approvals or fabricate evidence. ## Core Features & Use Cases - Read-only workspace rendering: Displays recorded readiness statuses, tables, turns, and outstanding approvals for exactly one pinned workspace per process, on loopback only. - Strict refusal boundaries: Never grants approvals, advances stages, writes passes, invents evidence, or emits numeric readiness scores; credentials are redacted before anything reaches the browser. - Named diagnostics: Missing optional studio extra, broken web-stack imports, and missing frontend assets each surface as named refusals with remedies rather than tracebacks. - Use Case: A data analyst standing in a Seshat workspace says "open Studio" to review which governance gates still need human sign-off before a Power BI delivery, viewing the readiness board in a browser while stage transitions remain owned by the readiness verbs. ## Quick Start Ask the assistant to open Studio for the current Seshat workspace, for example by saying "open Studio and show me this workspace's readiness board in the browser".
