V1 Web PWA · Surface walkthrough

Studio · Yemaya · Workers

A per-surface walkthrough of the V1 Web PWA studio surface: layout, states, interactions, data, and cross-references.

walked
8sections2 minread
Markdown source
On this page

Context. surface studio · domain yemaya · route /studio/yemaya/workers · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/workers/page.tsx

Last walked. 2026-05-29 automated runtime walk (Playwright headless) — render, /v1 data (2xx), console/page-errors, expected content, screenshot verified; live screen-reader, touch, offline, and telemetry-delivery checks pending a manual AT pass. Evidence: WALKTHROUGH/results/runtime-sweep-2026-05-29.md; body re-derived 2026-06-03 from current source (lane-console architecture)

Purpose#

Aggregator workspace that composes the Yemaya worker-runtime admin lanes — multi-agent orchestration, pipeline configuration, and pipeline step types — under a four-card capability summary. It issues no /v1 fetch of its own; each embedded lane runs its own real-backed engine.

Entry points#

  • Breadcrumb chain on this page: Studio › Yemaya Pipeline Configuration › Workers.
  • Reachable from the Studio index and from sibling Yemaya routes; also embedded as the Workers Lane inside the Event Handlers and Core aggregators.
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

page.tsx renders ShellLayout active="studio" and:

  • Breadcrumbs panel (data-yemaya-workers-breadcrumbs): Studio › Yemaya Pipeline Configuration › Workers.
  • Workspace panel (StudioYemayaWorkersWorkspace, data-yemaya-workers-workspace):
    • <h1> "Yemaya Workers Workspace" (WorkspaceHeading).
    • Summary paragraph (data-yemaya-workers-summary).
    • Capability Summary (data-yemaya-workers-capability-summary): <h2> + four cards — Worker Control Plane Orchestration, Pipeline Execution Governance, Step Runtime and Scheduling, Security and Parity.
    • Multi-Agent Orchestration Lane (data-yemaya-workers-orchestration-lane) — embedded StudioYemayaMultiAgentOrchestrationWorkspace.
    • Pipeline Configuration Lane (data-yemaya-workers-pipeline-configuration-lane) — embedded StudioYemayaPipelineConfigurationWorkspace.
    • Pipeline Step Types Lane (data-yemaya-workers-pipeline-step-types-lane) — embedded StudioYemayaPipelineStepTypesWorkspace.
  • Route Map panel (data-yemaya-workers-route-map): <h2> "Route Map" + six STUDIO_YEMAYA_WORKERS_ROUTE_MAP entries.
  • Quick-action panel: four quickAction links.

States#

Per embedded lane (this page has no fetch of its own):

  • Multi-Agent Orchestration Lane — its own lane states.
  • Pipeline Configuration Lane — its own lane states.
  • Pipeline Step Types Lane — its own lane states.
  • Capability Summary — static four-card panel, always rendered.

Interactions#

  • "Studio" (link) → /studio
  • "Yemaya Pipeline Configuration" (link) → /studio/yemaya/pipeline-configuration
  • "Workers" (current page) — aria-current="page".

Embedded lanes#

  • Multi-Agent Orchestration Lane — StudioYemayaMultiAgentOrchestrationWorkspace.
  • Pipeline Configuration Lane — StudioYemayaPipelineConfigurationWorkspace.
  • Pipeline Step Types Lane — StudioYemayaPipelineStepTypesWorkspace.

Route map#

data-yemaya-workers-route-map — six entries:

  • /studio/yemaya/workers
  • /studio/yemaya/workers/control-plane/[workerPoolId]
  • /studio/yemaya/workers/queues/[queueId]
  • /studio/yemaya/workers/executions/[executionId]
  • /studio/yemaya/workers/parity/[parityId]
  • /studio/yemaya/workers/governance/[policyId]

Quick actions#

  • "Open Yemaya Multi-Agent Orchestration workspace" → /studio/yemaya/multi-agent-orchestration.
  • "Open Yemaya Pipeline Configuration workspace" → /studio/yemaya/pipeline-configuration.
  • "Open Yemaya Pipeline Step Types workspace" → /studio/yemaya/pipeline-step-types.
  • "Back to Studio workspace index" → /studio.

Data & contracts#

  • Reads / Writes: none at the aggregator boundary; each embedded lane issues its own admin GET catalog + POST verb.
  • Realtime: none.
  • Caching: delegated to the embedded lanes (client fetch on mount, cache: 'no-store').
  • Auth/role check: admin-scoped fail-closed inside each lane, behind the proxy studio gate.

Cross-references#

Open questions / known gaps#

  • The Workers and Orchestration aggregators share two of three embedded lanes; define the canonical execution-runtime vs. orchestration-planning entry.
  • The Route Map advertises control-plane / queues / executions / parity / governance sub-routes; confirm whether those dynamic children exist as page.tsx files yet.