V1 Web PWA · Surface walkthrough

Studio · Yemaya · Core

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/core · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/core/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 core control-plane admin lanes — the API console, the CLI console, the Studio Web aggregator, and the Workers aggregator — 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 Studio Web › Core.
  • Reachable from the Studio index and from sibling Yemaya routes.
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

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

  • Breadcrumbs panel (data-yemaya-core-breadcrumbs): Studio › Yemaya Studio Web › Core.
  • Workspace panel (StudioYemayaCoreWorkspace, data-yemaya-core-workspace):
    • <h1> "Yemaya Core Workspace" (WorkspaceHeading).
    • Summary paragraph (data-yemaya-core-summary).
    • Capability Summary (data-yemaya-core-capability-summary): <h2> + four cards — Core Service Control Plane, API and CLI Execution Governance, Studio Runtime and Worker Operations, Security and Parity.
    • API Lane (data-yemaya-core-api-lane) — embedded StudioYemayaApiWorkspace.
    • CLI Lane (data-yemaya-core-cli-lane) — embedded StudioYemayaCliWorkspace.
    • Studio Web Lane (data-yemaya-core-studio-web-lane) — embedded StudioYemayaStudioWebWorkspace (itself an aggregator; see studio-yemaya-studio-web.md).
    • Workers Lane (data-yemaya-core-workers-lane) — embedded StudioYemayaWorkersWorkspace (itself an aggregator; see studio-yemaya-workers.md).
  • Route Map panel (data-yemaya-core-route-map): <h2> "Route Map" + six STUDIO_YEMAYA_CORE_ROUTE_MAP entries.
  • Quick-action panel: five quickAction links.

States#

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

  • API Lane — its own loading / unauthorized / error / ready / result states.
  • CLI Lane — its own lane states.
  • Studio Web Lane — nested aggregator; see studio-yemaya-studio-web.md.
  • Workers Lane — nested aggregator; see studio-yemaya-workers.md.
  • Capability Summary — static four-card panel, always rendered.

Interactions#

  • "Studio" (link) → /studio
  • "Yemaya Studio Web" (link) → /studio/yemaya/studio-web
  • "Core" (current page) — aria-current="page".

Embedded lanes#

Route map#

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

  • /studio/yemaya/core
  • /studio/yemaya/core/api/[serviceId]
  • /studio/yemaya/core/cli/[commandId]
  • /studio/yemaya/core/runtime/[runtimeId]
  • /studio/yemaya/core/parity/[parityId]
  • /studio/yemaya/core/governance/[policyId]

Quick actions#

  • "Open Yemaya API workspace" → /studio/yemaya/api.
  • "Open Yemaya CLI workspace" → /studio/yemaya/cli.
  • "Open Yemaya Studio Web workspace" → /studio/yemaya/studio-web.
  • "Open Yemaya Workers workspace" → /studio/yemaya/workers.
  • "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#

  • Core embeds two further aggregators (Studio Web, Workers), each of which embeds more lanes — verify the intended composition depth.
  • The Route Map advertises api / cli / runtime / parity / governance sub-routes; confirm whether those dynamic children exist as page.tsx files yet.