V1 Web PWA · Surface walkthrough

Isis AI Video Generation

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 isis · route /studio/isis/ai-video-generation · auth signed-in + studio entitlement (segment not in AAA_ONLY_STUDIO_ROUTES — renders as-is) · source apps/oshun/web/src/app/studio/isis/ai-video-generation/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 for AI video frame interpolation: the embedded Frame Interpolation Planner is wired to the real planner via /v1/admin/isis/ai-video-generation, computing how many in-between frames a frame-interpolation model must synthesize between each keyframe pair to reach a target fps. It is admin-scoped and fails closed.

Entry points#

  • Sibling quick-action from /studio/isis/3d-result-management
  • Studio index (/studio)
  • Direct URL / bookmark

Layout regions#

page.tsx mounts <ShellLayout active="studio"> (no breadcrumb panel) and three panels: the workspace, the Route Map, and sibling quick-actions.

  • Header: shell header
  • Workspace panel (data-isis-ai-video-generation-workspace):
    • <h1> (WorkspaceHeading) "Isis AI Video Generation Workspace"
    • Summary paragraph (data-isis-ai-video-generation-summary)
    • Embedded FrameInterpolationLane with its own <h2> (data-fil-heading) "Live Frame Interpolation Planner" — keyframes form + plan result
  • Route Map panel (data-isis-ai-video-generation-route-map): <h2>Route Map</h2> over STUDIO_ISIS_AI_VIDEO_GENERATION_ROUTE_MAP (5 entries)
  • Sibling quick-actions panel: /studio/isis/3d-result-management, /studio

States#

  • Loading — outcome === null; data-fil-loading "Loading interpolation planner…"
  • Unauthorized — 401/403 admin-scope fail-closed; data-fil-unauthorized
  • Error — non-OK or malformed catalog; data-fil-error
  • Ready (form) — catalog present; data-fil-form renders the keyframes JSON textarea
  • Result — after a plan POST, data-fil-result; invalid JSON or a planner rejection surfaces in data-fil-plan-error ("Payload must be valid JSON." / planner detail)

Interactions#

Frame Interpolation Planner (data-fil-form)#

  • Keyframes payload (data-fil-payload, <textarea>, aria-label="keyframes json")
  • Plan interpolation (data-fil-submit, submit) — POST /v1/admin/isis/ai-video-generation/plan-interpolation

Route Map#

  • Route-map articles ×5

Sibling quick-actions#

  • Open Isis 3D Result Management workspace → /studio/isis/3d-result-management
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads: GET /v1/admin/isis/ai-video-generation (planner catalog)
  • Writes: POST /v1/admin/isis/ai-video-generation/plan-interpolation (returns the per-pair interpolated-frame plan)
  • Realtime: none
  • Caching: client fetch on mount, cache: 'no-store', buildBffAuthHeaders()
  • Auth/role check: admin-scoped (Isis scope), fail-closed (401/403); route gated on signed-in + studio entitlement
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsisAIVideoGenerationWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisAIVideoGenerationRouteMap.ts

Cross-references#

Open questions / known gaps#

  • No breadcrumb on this route — navigation is via sibling quick-actions
  • The lane overlaps conceptually with /studio/isis/rife-interpolation (frame-rate up-conversion); confirm whether they target distinct interpolation models or should be consolidated