V1 Web PWA · Surface walkthrough

Isis Output 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/output-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/output-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 and static provenance fixture, 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, Client SDK, CLI, and Integration Events. Each child retains its own exact contract and state. The composition has no Output Registry aggregator endpoint, retained entry/package state, provenance or publication authority, parity run, governance record, or release decision.

The former "Registry artifact provenance" panel was a hard-coded GENERATED_ARTIFACT_PROVENANCE_RECORDS demonstration, not registry data. It is no longer mounted here.

Entry points#

  • Breadcrumb / quick-action card from /studio/isis/generation-api
  • Embedded as an "Output Registry Lane" in several Isis aggregators
  • Studio index (/studio)
  • Direct URL / bookmark (AAA-gated)

Layout regions#

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

  • Breadcrumb panel (data-isis-output-registry-breadcrumbs): Studio → Isis Generation API → (current)
  • Workspace panel (data-isis-output-registry-workspace):
    • <h1> "Isis Output Registry Workspace" (WorkspaceHeading) + honest summary and exact ui_only_non_authoritative_embedded_lane_composition disposition
    • Composition Boundary panel with four cards: independent lane authority, no registry endpoint, no provenance/publication authority, and no governance/release authority
    • Five embedded lanes:
      • Generation API Lane (data-isis-output-registry-generation-api-lane)
      • GPU Worker Lane (data-isis-output-registry-gpu-worker-lane)
      • Client SDK Lane (data-isis-output-registry-client-sdk-lane)
      • CLI Lane (data-isis-output-registry-cli-lane)
      • Integration Events Lane (data-isis-output-registry-integration-events-lane)
  • Route map panel (data-isis-output-registry-route-map): one mounted-composition and five documented-contract entries
  • Quick-actions panel: links to /studio/isis/generation-api, /studio/isis/gpu-worker, /studio/isis/client-sdk, /studio/isis/cli, and /studio

States#

No fetch at the aggregator; each embedded lane drives its own Loading / Unauthorized / Error / Ready / Result states.

Interactions#

Embedded lanes#

  • Generation API Lane
  • GPU Worker Lane
  • Client SDK Lane
  • CLI Lane
  • Integration Events 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 Generation API workspace → /studio/isis/generation-api
  • Open Isis GPU Worker workspace → /studio/isis/gpu-worker
  • Open Isis Client SDK workspace → /studio/isis/client-sdk
  • Open Isis CLI workspace → /studio/isis/cli
  • 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 entry, package, artifact, or publication record
  • Provenance: no live/durable provenance source or evidence authority; the former source-defined demonstration records are not mounted
  • Operations: no publication, delivery, diagnostics, parity, remediation, permission, audit, governance, approval, or release action
  • Realtime: None
  • Caching: delegated to embedded lanes
  • Auth: admin-scoped fail-closed per embedded lane; AAA-gated Studio route behind the signed-in + studio proxy gate
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsisOutputRegistryWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisOutputRegistryRouteMap.ts

Cross-references#

Open questions / known gaps#

  • Entry, package, evidence, parity, and governance paths are documented shapes only, with no pages or corresponding aggregator authority
  • There is no standalone output registry, durable provenance source, publication workflow, evidence record, parity certification, governance, or release authority here