Skip to main content

Dashboard Guide — Vesanor

The primary browser entry is Governance Studio. /dashboard redirects to /dashboard/studio, and the legacy /dashboard/agents authoring routes redirect there as well.

This guide follows the Phase 7 Studio direction:

Atlas -> Control -> Focus

The dashboard should be understood as a model-first governance workbench, not a collection of unrelated SaaS pages.

The primary experience: Studio​

Studio index​

At /dashboard/studio, you see a tenant-scoped workspace list.

Each workspace shows:

  • whether an active draft exists
  • whether an active approval exists
  • the environment/status context for that workspace

Workspace workbench​

At /dashboard/studio/workspaces/<workspace_id>, the workbench is organized around the current operating model:

  • Atlas — high-level model of signals, policy clusters, controls, and runtime posture
  • Control — one control path with stages, gates, proofs, field guards, and runtime overlay
  • Focus — one judgment with evidence and consequence preview
  • Approval preview — readiness, blockers, advisories, and consequence of approval
  • Conformance findings — post-approval findings that support or challenge the approved model

When signal is too thin for a full Atlas view, the workspace can fall back to a thinner signal summary state instead of inventing an operating model that does not exist.

What the workbench is for​

The workbench should help the user answer:

  • what is the current operating model?
  • what judgments block enforcement?
  • what happens if I approve now?
  • what runtime findings challenge the approved state?

The unit of work is judgment, not “review these forty fields.”

That is the main dashboard concept to preserve while the redesign is in motion.

Approval and conformance​

Two workbench areas matter operationally:

Approval preview​

Approval preview is the pre-approval surface.

It tells you:

  • whether blockers still exist
  • which advisories remain
  • what becomes enforceable after approval
  • whether the preview is still fresh relative to the active draft

Conformance findings​

Conformance findings are the post-approval surface.

They tell you how runtime behavior supports or challenges approved controls after approval.

That distinction matters:

  • approval preview = readiness to approve
  • conformance = runtime challenge/support after approval

Secondary operational surfaces​

The old dashboard pages still exist as supporting operational surfaces:

  • Runs — execution and evaluation history
  • References — trust posture over active/stale/retired references
  • Models — model comparison where available
  • Settings — account and key management

These are secondary. They support the Studio workbench; they are not the product center.

References​

The References page remains important even in a Studio-first product.

Use it to answer:

  • what is the current trusted reference?
  • which references are stale?
  • which candidates are ready to promote?
  • what got retired after a replacement was promoted?

References are part of trust posture, not part of Studio authoring.

Runs​

The Runs page is the execution history surface.

Use it when you want:

  • recent failures
  • fingerprints
  • provider/model context
  • baseline-key context
  • step-level inspection

Studio tells you the current operating model. Runs tell you what actually happened.

What not to treat as primary​

Per the Phase 7 direction, the primary dashboard experience should not feel like:

  • a page-first dashboard shell
  • a graph editor
  • a source library
  • a policy spreadsheet
  • a raw run list

Those may still exist as support surfaces, but the main product should remain:

Signals -> Operating Model -> Consequences
             ^
         Judgment