V1 Web PWA · Surface walkthrough

Isis Generation API

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 isis · route /studio/isis/generation-api · auth signed-in + studio entitlement; Studio Isis production boundary hard-blocks this route. Automated lane verification uses the explicit localhost-only E2E bypass. · source apps/oshun/web/src/app/studio/isis/generation-api/page.tsx

Last walked. 2026-07-23 automated desktop Chromium + Pixel 7 mobile walk — production hard-block, localhost-only lane entry, explicit composition boundary, five child lanes, absence of an aggregator request and synthetic operations, route status, touch targets, responsive containment, and applicable axe verified

Purpose#

UI-only, non-authoritative composition of five independent Isis workspaces: client SDK, CLI, integration events, content safety, and resource recommendations. Each child retains its own exact contract and state. The composition has no Generation API aggregator endpoint, shared operational state, synthetic workflow/parity run, governance record, or release authority.

Entry points#

  • Breadcrumb / quick-action card from /studio/isis/client-sdk
  • Embedded as a "Generation API Lane" in several Isis aggregators
  • Studio index (/studio)
  • Direct URL / bookmark

Layout regions#

page.tsx mounts ShellLayout active="studio" with a breadcrumb panel.

  • Breadcrumb panel (data-isis-generation-api-breadcrumbs): Studio → Isis Client SDK → (current)
  • Workspace panel (data-isis-generation-api-workspace):
    • <h1> "Isis Generation API Workspace" (WorkspaceHeading) + summary (data-isis-generation-api-summary) and exact ui_only_non_authoritative_embedded_lane_composition disposition (data-isis-generation-api-disposition)
    • Composition Boundary panel (data-isis-generation-api-capability-summary, <h2>) with four honest cards
    • Five embedded lanes, each an <h2> panel wrapping a sibling workspace via WorkspaceSection:
      • Client SDK Lane (data-isis-generation-api-client-sdk-lane)
      • CLI Lane (data-isis-generation-api-cli-lane)
      • Integration Events Lane (data-isis-generation-api-integration-events-lane)
      • Content Safety Lane (data-isis-generation-api-content-safety-lane)
      • Resource Recommendations Lane (data-isis-generation-api-resource-recommendations-lane)
  • Route map panel (data-isis-generation-api-route-map): <h2> "Route Map" over one mounted-composition entry and five documented-contract entries
  • Quick-actions panel: quickAction links to /studio/isis/client-sdk, /studio/isis/cli, /studio/isis/integration-events, /studio/isis/content-safety, and "Back to Studio workspace index" → /studio

States#

No fetch at the aggregator; each embedded lane drives its own Loading / Unauthorized (admin-scope 401/403) / Error / Ready / Result states.

Interactions#

Embedded lanes#

  • Client SDK Lane
  • CLI Lane
  • Integration Events Lane
  • Content Safety Lane
  • Resource Recommendations Lane

Composition boundary#

  • Boundary cards ×4 — non-interactive and authority-limiting

Route map#

  • Mounted composition ×1
  • Documented route shapes without pages or authority ×5

Quick-actions#

  • Open Isis Client SDK workspace → /studio/isis/client-sdk
  • Open Isis CLI workspace → /studio/isis/cli
  • Open Isis Integration Events workspace → /studio/isis/integration-events
  • Open Isis Content Safety workspace → /studio/isis/content-safety
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads / writes: none from this composition directly — delegated to the embedded sibling lanes, each calling its own /v1 endpoint
  • Synthetic controls: none; no local workflow runs, forced failures, endpoint actors, parity certification, telemetry destinations, or runbook links remain
  • Realtime: None
  • Caching: delegated to embedded lanes (client fetch on mount, no-store)
  • Auth: admin-scoped fail-closed per embedded lane; the web route is signed-in and then production-hard-blocked by the Studio Isis boundary
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsisGenerationApiWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisGenerationApiRouteMap.ts

Cross-references#

Open questions / known gaps#

  • Request, job, evidence, parity, and governance paths are documented shapes only, with no pages or corresponding aggregator authority
  • The composition does not create credentials, run jobs, join traces, attest parity, publish policies, approve evidence, or sign off releases