V1 Web PWA · Surface walkthrough

Studio · Yemaya · Storyboard Creation

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

walked
8sections2 minread

On this page

Context. surface studio · domain yemaya · route /studio/yemaya/storyboard-creation · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/storyboard-creation/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/pre-production Fountain screenplay engine — parse a Fountain script into structured scenes, characters, dialogue and statistics (the backbone of a storyboard), and export it to industry formats. Wired over /v1/admin/yemaya/storyboard-creation; access is admin-scoped and fail-closed.

Entry points#

  • No breadcrumb panel on this page.
  • Reachable from sibling Yemaya routes that quick-action here (e.g., screenplay-tools).
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

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

  • Workspace panel (StudioYemayaStoryboardCreationWorkspace, data-yemaya-storyboard-creation-workspace):
    • <h1> (WorkspaceHeading) "Yemaya Storyboard Creation Workspace".
    • Summary paragraph (data-yemaya-storyboard-creation-summary).
    • Screenplay Operations Lane (data-yemaya-sc-lane-heading, <h2>): the catalog-loaded form (data-yemaya-sc-form) with parse + export controls.
  • Route Map panel (data-yemaya-storyboard-creation-route-map): <h2> "Route Map" + five entries from STUDIO_YEMAYA_STORYBOARD_CREATION_ROUTE_MAP.
  • Quick-action panel: two quickAction links.

States#

  • Loadingdata-yemaya-sc-loading "Loading screenplay engine…" until the GET catalog resolves.
  • Unauthorizeddata-yemaya-sc-unauthorized "Access restricted." on a 401/403 (Yemaya admin scope required).
  • Errordata-yemaya-sc-error "Could not load the screenplay engine." on a non-OK / malformed catalog response.
  • Ready (form) — engine summary (data-yemaya-sc-engine-summary) + the script + export-format form render once the catalog loads.
  • Resultdata-yemaya-sc-result with a parse headline (data-yemaya-sc-headline); the export result renders in data-yemaya-sc-export-result. Submit-side validation surfaces in data-yemaya-sc-parse-error (parse) and data-yemaya-sc-export-error (export).

Interactions#

Screenplay Operations Lane#

  • "Fountain screenplay"<textarea data-yemaya-sc-script> (aria-label "screenplay").
  • "Parse screenplay"<button data-yemaya-sc-parse-submit>; submitting POSTs the script to /v1/admin/yemaya/storyboard-creation/parse and renders the structured scenes/characters/dialogue + statistics.
  • "Export format"<select data-yemaya-sc-format> populated from the catalog's export formats.
  • "Export"<button data-yemaya-sc-export-submit>; clicking POSTs the script + chosen format to /v1/admin/yemaya/storyboard-creation/export and renders the exported artifact.

Route map#

data-yemaya-storyboard-creation-route-map — five non-interactive entries:

  • /studio/yemaya/storyboard-creation — primary workspace
  • /studio/yemaya/storyboard-creation/boards/[boardId]
  • /studio/yemaya/storyboard-creation/scenes/[sceneId]
  • /studio/yemaya/storyboard-creation/revisions/[revisionId]
  • /studio/yemaya/storyboard-creation/governance/[policyId]

Quick actions#

  • "Open Yemaya Screenplay Tools workspace"/studio/yemaya/screenplay-tools.
  • "Back to Studio workspace index"/studio.

Data & contracts#

  • Reads: GET /v1/admin/yemaya/storyboard-creation (catalog: summary + export formats) on mount.
  • Writes: POST /v1/admin/yemaya/storyboard-creation/parse (script → structured scenes + statistics); POST /v1/admin/yemaya/storyboard-creation/export (script + format → exported artifact).
  • 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 (boards / scenes / revisions / governance) are sitemap-only — confirm whether any are backed by page.tsx files yet.