V1 Web PWA · Surface walkthrough

Isis Workflow Registry

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/workflow-registry · auth signed-in + studio entitlement; Studio Isis production boundary hard-blocks this AAA-only route. Automated lane verification uses the explicit localhost-only E2E bypass. · source apps/oshun/web/src/app/studio/isis/workflow-registry/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, route status, touch targets, responsive containment, and applicable axe verified

Purpose#

UI-only, non-authoritative composition of five independent Isis workspaces: Generation API, GPU Worker, Output Registry, Web, and Integration Events. Each child retains its own exact contract and state. The composition has no Workflow Registry aggregator endpoint, retained workflow or version state, orchestration or migration action, diagnostic/evidence authority, parity run, governance record, or release decision.

Entry points#

  • Breadcrumb / quick-action card from /studio/isis/output-registry
  • Embedded as a "Workflow Registry Lane" in several Isis aggregators
  • Studio index (/studio)
  • Direct URL / bookmark (AAA-gated)

Layout regions#

  • Breadcrumb panel (data-isis-workflow-registry-breadcrumbs): Studio → Isis Output Registry → (current)
  • Workspace panel (data-isis-workflow-registry-workspace):
    • <h1> "Isis Workflow Registry Workspace"
    • Honest summary and exact ui_only_non_authoritative_embedded_lane_composition disposition
    • Composition Boundary with four cards: independent lane authority, no registry endpoint, no orchestration/evidence authority, and no governance/release authority
    • Five embedded lanes: Generation API, GPU Worker, Output Registry, Web, and Integration Events
  • Route map panel (data-isis-workflow-registry-route-map): one mounted-composition and five documented-contract entries
  • Quick-actions panel: links to Output Registry, Web, GPU Worker, Generation API, and Studio

States#

No fetch at the composition level. Each child lane manages its own loading, unauthorized, error, ready, and result states.

Interactions#

Composition boundary#

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

Embedded lanes#

  • Generation API / GPU Worker / Output Registry / Web / Integration Events — walk each in its own doc

Route Map#

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

Quick-actions#

  • Open Isis Output Registry workspace → /studio/isis/output-registry
  • Open Isis Web workspace → /studio/isis/web
  • Open Isis GPU Worker workspace → /studio/isis/gpu-worker
  • Open Isis Generation API workspace → /studio/isis/generation-api
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads / writes: none from this composition directly; delegated to child lanes under their own exact contracts
  • Registry state: no workflow, version, migration, evidence, parity, or governance record
  • Operations: no registration, versioning, orchestration, migration, diagnostic trace, remediation, permission, audit, certification, approval, or release action
  • Realtime: none
  • Auth: AAA-gated Studio route behind the signed-in + studio proxy gate; embedded lanes are individually admin-scoped and fail closed
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsisWorkflowRegistryWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisWorkflowRegistryRouteMap.ts

Cross-references#

Open questions / known gaps#

  • Workflow, version, evidence, parity, and governance paths are documented shapes only, with no pages or corresponding aggregator authority
  • There is no standalone Workflow Registry, retained workflow/version store, orchestration/migration workflow, evidence record, parity certification, governance, approval, or release authority here
  • The Web and Output Registry children are themselves nested compositions; retain focused performance monitoring for this deeply nested route