Control Studio
Make control capabilities, timing constraints and provenance visible before an operator admits a control action.
Federated operator panel · guarded hardware verbs · Source review: 2026-09-26
What it is for
Make control capabilities, timing constraints and provenance visible before an operator admits a control action.
Who it is for
Control researchers and engineers reviewing model results and hardware-admission boundaries.
Documented capabilities
- Inspect declared verbs, real-time deadlines and claim boundaries.
- Review a provenance feed and distinguish validated receipts from bundled demonstration samples.
- Integrate the ./Panel remote into the shared Hub with its identity and entitlement checks.
A typical workflow
Open a panel in an authorised environment → inspect the feed source and freshness → review the timing and claim boundary → check the applicable admission policy before requesting an action.
Scope and evidence
A feed receipt is not a live reactor measurement. Bundled fallback data are samples. Rendering a panel does not authorise hardware execution; regulate and mitigate are gated per tenant by the Hub and independent protection remains required.
Local setup and dependencies
Build the studio-web remote using the repository README and the shared SDK. The documented deployment base is /studios/scpn-control/ on the Hub, not on this presentation website.
Availability and access
The Hub registry lists a Pro integration with shared authentication and billing. This website describes it; current hosted availability is not confirmed here.
Read the project sources
Project overview · All Studios and their roles · Discuss a research or deployment workflow