V1 Web PWA · Surface walkthrough

Studio · Yemaya · Pipeline Configuration

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/pipeline-configuration · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/pipeline-configuration/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#

Admin lane console wired to the @yemaya/orchestration pipeline Zod schemas — it lists the pipeline + step lifecycle statuses and the cross-domain step-type catalogue, then validates a create-pipeline payload against the real CreatePipelineSchema before creation. Wired over /v1/admin/yemaya/pipeline-configuration; access is admin-scoped and fail-closed.

Entry points#

  • No breadcrumb panel on this page.
  • Reachable from sibling Yemaya routes that quick-action here, and from the cli / orchestration aggregators that embed this lane.
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

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

  • Workspace panel (StudioYemayaPipelineConfigurationWorkspace, data-yemaya-pipeline-configuration-workspace):
    • <h1> (WorkspaceHeading) "Yemaya Pipeline Configuration Workspace".
    • Summary paragraph (data-yemaya-pipeline-configuration-summary).
    • Pipeline Configuration Operations Lane (data-yemaya-pipeline-configuration-operations-lane, <h2>): a catalog panel (data-yemaya-pc-catalog, pipeline statuses + step-type count across isis/sophia/hathor/bellona/mcp/yemaya + control-flow) and the validation form (data-yemaya-pc-form).
  • Route Map panel (data-yemaya-pipeline-configuration-route-map): <h2> "Route Map" + five entries from STUDIO_YEMAYA_PIPELINE_CONFIGURATION_ROUTE_MAP.
  • Quick-action panel: two quickAction links.

States#

  • Loading — data-yemaya-pc-loading "Loading pipeline configuration…" until the GET catalog resolves.
  • Unauthorized — data-yemaya-pc-unauthorized "Access restricted." on a 401/403 (Yemaya admin scope required).
  • Error — data-yemaya-pc-error "Could not load the pipeline configuration." on a non-OK / malformed catalog response.
  • Ready (form) — the catalog panel + create-pipeline form render once the catalog loads.
  • Result — data-yemaya-pc-result with a verdict (data-yemaya-pc-verdict) and the per-path issue list (data-yemaya-pc-issue-row); submit-side validation surfaces in data-yemaya-pc-validate-error.

Interactions#

Pipeline Configuration Operations Lane#

  • "Create-pipeline payload (JSON)" — <textarea data-yemaya-pc-pipeline> (aria-label "create pipeline json").
  • "Validate payload" — <button data-yemaya-pc-submit>; submitting POSTs the payload to /v1/admin/yemaya/pipeline-configuration/validate and renders the valid/invalid verdict + CreatePipelineSchema issues.

Route map#

data-yemaya-pipeline-configuration-route-map — five non-interactive entries:

  • /studio/yemaya/pipeline-configuration — primary workspace
  • /studio/yemaya/pipeline-configuration/scenes/[sceneId]
  • /studio/yemaya/pipeline-configuration/exports/[exportId]
  • /studio/yemaya/pipeline-configuration/revisions/[revisionId]
  • /studio/yemaya/pipeline-configuration/governance/[policyId]

Quick actions#

  • "Open Yemaya Autonomous Game Pipeline workspace" → /studio/yemaya/autonomous-game-pipeline.
  • "Back to Studio workspace index" → /studio.

Data & contracts#

  • Reads: GET /v1/admin/yemaya/pipeline-configuration (catalog: pipeline statuses + step-type catalogue) on mount.
  • Writes: POST /v1/admin/yemaya/pipeline-configuration/validate (create-pipeline payload → CreatePipelineSchema validation result).
  • Realtime: none.
  • Caching: client fetch on mount with cache: 'no-store'; buildBffAuthHeaders().
  • Auth/role check: admin-scoped, fail-closed (401/403 → unauthorized state); signed-in + studio entitlement enforced by the proxy/middleware.

Cross-references#

Open questions / known gaps#

  • The route-map dynamic children (scenes / exports / revisions / governance) are sitemap-only — confirm whether any are backed by page.tsx files yet.