Studio UI

vyuh_studio_ui is the canonical Flutter design system and enterprise application UI for Vyuh products. It owns the reusable shell, workspace, collection, panel, editor, command, status, and regulated interaction compositions. It sits on top of the already-agnostic CDX engines and does not import Blueprint declarations or Entity System runtime types.

Package Role

cdx_panes + cdx_query + vyuh_cdx_ui + collection widgets
  -> vyuh_studio_ui
  -> vyuh_blueprint_ui
  -> apps

There is no separate Workspace UI package. Workspace composition is part of Studio UI. vyuh_entity_system_ui remains legacy source material and is not a Studio dependency or a vocabulary exposed by new Studio APIs.

Core Vocabulary

Concept	Classes
Workspace frame	Workspace, WorkspaceLayout, DockConfig, DockPlacement, DockMode
Header chrome	Workspace.headerControls for scope, account, and app-level controls
Collection runtime	CollectionDescriptor, CollectionController, CollectionView
Collection modes	CollectionLayoutMode, CollectionPresentation, CollectionColumn
Query state	CollectionQuery, FilterToken, SortToken
Saved views	SavedView, SavedViews
Actions and commands	UiAction, ActionPanel, Command, CommandPalette
Detail and panels	SectionCard, DetailView, PanelItem, FieldValue
Dashboards and reports	Metric, DashboardView, ReportView
Regulated posture	PolicyPanel, EvidencePanel, AuditTrail, VersionHistory, AuthorizationGate, ErrorPanel
Runtime surfaces	InboxPanel, NotificationPanel, ApprovalPanel, OfflineBanner, RealtimeStatus, SimulationPanel
Help	HelpFragment, HelpContext, HelpPanel
Icons	UiIcons backed by Fluent UI system icons

Boundary Rule

The package is record and descriptor based. A collection is a named CollectionDescriptor plus rows, controller state, and optional actions. Blueprint UI maps Blueprint collection surfaces into that shape.

That keeps the shared UI vocabulary useful for entity-backed screens, protocol-record explorers, dashboards, reports, simulator timelines, policy consoles, generated documents, and non-entity operational surfaces.