Skip to main content

Governance Studio

Governance Studio is the primary browser authoring and review surface for Vesanor.

If you open /dashboard, Vesanor redirects to /dashboard/studio. The older /dashboard/agents browser authoring routes also redirect there.

What Studio is for​

Studio is where you review governed workflow behavior without hand-authoring contract packs.

Studio brings together:

  • observed tool and workflow evidence
  • the current draft operating model
  • unresolved judgments that still need a decision
  • approval preview and approval submission
  • conformance findings after approval

For most users, Studio is the main product surface. You do not need to manage local YAML packs to use it.

Studio routes​

/dashboard/studio​

This is the Studio index. It lists tenant-scoped workspaces and shows whether each workspace currently has:

  • an active draft
  • an active approval
  • a current environment/status

/dashboard/studio/workspaces/<workspace_id>​

This is the Studio workbench for one workspace.

The workbench is organized around the current operating model:

  • Atlas: high-level map of the workspace, signals, and approval posture
  • Policy clusters: grouped policy and rule clusters from the active draft
  • Control unit: operational summary for the workspace
  • Open judgments: unresolved questions that still need a decision
  • Impact preview: read-only simulation of a judgment outcome before applying it
  • Approval preview: blockers, advisories, and enforced consequences before approval
  • Approval submit: the Studio approval flow for the active draft
  • Conformance findings: findings that challenge or support the current draft or approval state

Authority model​

Studio is not just a visualization layer. It is the primary browser-side authority surface for governance review and approval.

Important boundaries:

  • Studio approval happens through the Studio /approve route for a workspace.
  • Legacy dashboard governance proxy write routes are retired product surfaces.
  • v1 governance APIs still exist for SDK/runtime/internal flows, but they are not the main browser authoring surface.

In practice:

  • Browser authoring: Studio
  • Runtime attachment: replay() with zero-config governance
  • Operational drilldown: Runs, References, Models, and other dashboard pages

How Studio fits with zero-config governance​

Zero-config governance and Studio are the intended product pair.

Typical flow:

  1. Wrap your client with replay(client, { apiKey })
  2. Run your app
  3. Open Governance Studio
  4. Review the workspace draft, judgments, and approval preview
  5. Approve the draft
  6. Let the SDK attach to the approved runtime artifact by environment

This is the recommended path for new users.

How Studio fits with local contracts​

Local YAML contracts are a separate path.

They can still be enforced locally with replay(client, { contractsDir, ... }), but they are not the main Studio-first workflow, and promoting a local pack does not automatically make that pack the Studio authority.

If you need that path, see the archived docs under docs/legacy/advanced-local/ in the repo.

What Studio is not​

Studio is not:

  • the old /dashboard/agents governance browser flow
  • a first-class YAML pack editor
  • a direct mirror of your local filesystem packs

It is a workspace-based governance review and approval surface backed by tenant-scoped server state.