Studio · Yemaya · Pipeline Templates

Purpose#

Admin lane console for production-pipeline template expansion. It wires the real @yemaya/autonomous-pipelines template factories via /v1/admin/yemaya/pipeline-templates: pick a template (film / game / qc / curation) plus generation toggles and inspect the deterministic step graph it expands to — step names, types, and dependencies — before instantiating it.

Entry points#

• No breadcrumb panel on this page.
• 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:

• Workspace panel (StudioYemayaPipelineTemplatesWorkspace, data-yemaya-pipeline-templates-workspace):
  • <h1> "Yemaya Pipeline Templates Workspace" (WorkspaceHeading).
  • Summary paragraph (data-yemaya-pipeline-templates-summary).
  • The template-generation form lane (loading / unauthorized / error / ready-form / result, see States).
• Route Map panel (data-yemaya-pipeline-templates-route-map): <h2> "Route Map" + five STUDIO_YEMAYA_PIPELINE_TEMPLATES_ROUTE_MAP entries.
• Quick-action panel: two quickAction links.

States#

• Loading — data-yemaya-pt-loading "Loading templates…" while the GET catalog fetch is in flight.
• Unauthorized — data-yemaya-pt-unauthorized "Access restricted." on a 401/403 admin-scope failure (fail-closed).
• Error — data-yemaya-pt-error "Could not load pipeline templates." on a non-OK / malformed catalog response.
• Ready-form — data-yemaya-pt-generate-form once the catalog (templates) resolves.
• Result — data-yemaya-pt-result with data-yemaya-pt-count (template · step count) and a data-yemaya-pt-steps ordered list; or a validation message data-yemaya-pt-generate-error.

Interactions#

Generation form (data-yemaya-pt-generate-form)#

• Template — select data-yemaya-pt-field-template populated from catalog.templates.
• Generation toggles — four checkboxes data-yemaya-pt-flag={key} (generateCharacters, generateLocations, generateSoundEffects, generateMusic).
• Submit — button data-yemaya-pt-generate-submit "Generate pipeline" → POST /v1/admin/yemaya/pipeline-templates/generate with { template, config } (config carries the toggle flags).

Route map#

data-yemaya-pipeline-templates-route-map — five entries:

• /studio/yemaya/pipeline-templates
• /studio/yemaya/pipeline-templates/scenes/[sceneId]
• /studio/yemaya/pipeline-templates/exports/[exportId]
• /studio/yemaya/pipeline-templates/revisions/[revisionId]
• /studio/yemaya/pipeline-templates/governance/[policyId]

Quick actions#

• "Open Yemaya Pipeline Configuration workspace" → /studio/yemaya/pipeline-configuration.
• "Back to Studio workspace index" → /studio.

Data & contracts#

• Reads: GET /v1/admin/yemaya/pipeline-templates (catalog: templates) on mount.
• Writes: POST /v1/admin/yemaya/pipeline-templates/generate.
• Realtime: none.
• Caching: client fetch on mount, cache: 'no-store', buildBffAuthHeaders().
• Auth/role check: admin-scoped fail-closed (401/403 → unauthorized state) behind the proxy studio gate.

Cross-references#

• Studio overview: studio-overview.md
• Workspace source: apps/oshun/web/src/components/studio/StudioYemayaPipelineTemplatesWorkspace.tsx
• Route map source: apps/oshun/web/src/components/studio/StudioYemayaPipelineTemplatesRouteMap.ts
• Engine: @yemaya/autonomous-pipelines
• Sibling per-view doc: studio-yemaya-autonomous-pipelines.md
• Feature spec: V1/features.md

Open questions / known gaps#

• The Route Map advertises scenes / exports / revisions / governance sub-routes that the live generation lane does not expose.