V1 Web PWA · Surface walkthrough

Studio · Yemaya · Orchestration

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

walked
8sections3 minread
Markdown source
On this page

Context. surface studio · domain yemaya · route /studio/yemaya/orchestration · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/orchestration/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 four Yemaya orchestration lanes — Multi-Agent Orchestration, Autonomous Pipelines, Pipeline Configuration, and Pipeline Templates — under a single Yemaya Orchestration capability summary. It owns no /v1 fetch of its own; each embedded lane is its own admin-scoped console with independent data and states.

Entry points#

  • Breadcrumb chain on this page: Studio › Yemaya Multi-Agent Orchestration › Orchestration.
  • Reachable from sibling Yemaya routes that quick-action to /studio/yemaya/orchestration.
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

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

  • Breadcrumbs panel: Studio › Yemaya Multi-Agent Orchestration › Orchestration.
  • Workspace panel (StudioYemayaOrchestrationWorkspace, data-yemaya-orchestration-workspace):
    • <h1> (WorkspaceHeading) "Yemaya Orchestration Workspace".
    • Summary paragraph (data-yemaya-orchestration-summary).
    • Capability Summary (data-yemaya-orchestration-capability-summary, <h2>): four informational cards — Orchestration Control Plane, Autonomous and Multi-Agent Coordination, Pipeline Configuration Governance, Security and Parity.
    • Multi-Agent Orchestration Lane (data-yemaya-orchestration-multi-agent-lane, <h2>): embedded StudioYemayaMultiAgentOrchestrationWorkspace.
    • Autonomous Pipelines Lane (data-yemaya-orchestration-autonomous-lane, <h2>): embedded StudioYemayaAutonomousPipelinesWorkspace.
    • Pipeline Configuration Lane (data-yemaya-orchestration-configuration-lane, <h2>): embedded StudioYemayaPipelineConfigurationWorkspace.
    • Pipeline Templates Lane (data-yemaya-orchestration-templates-lane, <h2>): embedded StudioYemayaPipelineTemplatesWorkspace.
  • Route Map panel (data-yemaya-orchestration-route-map): <h2> "Route Map"
    • six entries from STUDIO_YEMAYA_ORCHESTRATION_ROUTE_MAP.
  • Quick-action panel: five quickAction links.

States#

The page renders the capability cards + four embedded lanes unconditionally; each lane owns its own Loading / Unauthorized (admin-scope 401/403) / Error / Ready / Result states.

  • Multi-Agent Orchestration Lane — states owned by /studio/yemaya/multi-agent-orchestration.
  • Autonomous Pipelines Lane — states owned by /studio/yemaya/autonomous-pipelines.
  • Pipeline Configuration Lane — states owned by /studio/yemaya/pipeline-configuration.
  • Pipeline Templates Lane — states owned by /studio/yemaya/pipeline-templates.

Interactions#

Capability cards#

data-yemaya-orchestration-capability — four informational <article> cards (Orchestration Control Plane, Autonomous and Multi-Agent Coordination, Pipeline Configuration Governance, Security and Parity); not interactive.

Embedded lanes#

  • Multi-Agent Orchestration Lane — see /studio/yemaya/multi-agent-orchestration.
  • Autonomous Pipelines Lane — see /studio/yemaya/autonomous-pipelines.
  • Pipeline Configuration Lane — see studio-yemaya-pipeline-configuration.md.
  • Pipeline Templates Lane — see /studio/yemaya/pipeline-templates.

Route map#

data-yemaya-orchestration-route-map — six non-interactive entries:

  • /studio/yemaya/orchestration — primary workspace
  • /studio/yemaya/orchestration/runs/[runId]
  • /studio/yemaya/orchestration/pipelines/[pipelineId]
  • /studio/yemaya/orchestration/templates/[templateId]
  • /studio/yemaya/orchestration/parity/[parityId]
  • /studio/yemaya/orchestration/governance/[policyId]

Quick actions#

  • "Open Yemaya Multi-Agent Orchestration workspace" → /studio/yemaya/multi-agent-orchestration.
  • "Open Yemaya Autonomous Pipelines workspace" → /studio/yemaya/autonomous-pipelines.
  • "Open Yemaya Pipeline Configuration workspace" → /studio/yemaya/pipeline-configuration.
  • "Open Yemaya Pipeline Templates workspace" → /studio/yemaya/pipeline-templates.
  • "Back to Studio workspace index" → /studio.

Data & contracts#

  • Reads: none at this aggregator boundary; each embedded lane issues its own GET /v1/admin/yemaya/... on mount.
  • Writes: none at this boundary; each embedded lane owns its own POST verb.
  • Realtime: none.
  • Caching: aggregator owns no fetch; embedded lanes fetch on mount with cache: 'no-store'.
  • Auth/role check: each embedded lane is admin-scoped and fail-closed; signed-in + studio entitlement enforced by the proxy/middleware.

Cross-references#

  • Studio overview: studio-overview.md
  • Workspace source: apps/oshun/web/src/components/studio/StudioYemayaOrchestrationWorkspace.tsx
  • Route map source: apps/oshun/web/src/components/studio/StudioYemayaOrchestrationRouteMap.ts
  • Embedded lanes: studio-yemaya-pipeline-configuration.md, /studio/yemaya/multi-agent-orchestration, /studio/yemaya/autonomous-pipelines, /studio/yemaya/pipeline-templates
  • Feature spec: V1/features.md

Open questions / known gaps#

  • The route-map dynamic children (runs / pipelines / templates / parity / governance) are sitemap-only — confirm whether any are backed by page.tsx files yet.