V1 Web PWA · Surface walkthrough

Isis Outputs

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/outputs · 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/outputs/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: Output Registry, Output Manifest, Collection Management, Retention Policies, and Integration Events. Each child retains its own exact contract and state. The composition has no Outputs endpoint, retained artifact or publication state, provenance/evidence authority, parity run, governance record, or release decision.

Entry points#

  • Quick-action card from embedded-lane routes
  • Studio index (/studio)
  • Direct URL / bookmark (AAA-gated)

Layout regions#

  • Breadcrumb panel (data-isis-outputs-breadcrumbs): Studio → Isis Output Registry → (current)
  • Workspace panel (data-isis-outputs-workspace):
    • <h1> "Isis Outputs Workspace"
    • Honest summary and exact ui_only_non_authoritative_embedded_lane_composition disposition
    • Composition Boundary with four cards: independent lane authority, no Outputs endpoint, no publication/provenance authority, and no governance/release authority
    • Five embedded lanes: Output Registry, Output Manifest, Collection Management, Retention Policies, and Integration Events
  • Route map panel (data-isis-outputs-route-map): one mounted-composition and five documented-contract entries
  • Quick-actions panel: links to Output Manifest, Output Registry, Retention Policies, 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#

  • Output Registry / Output Manifest / Collection Management / Retention Policies / 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 Manifest workspace → /studio/isis/output-manifest
  • Open Isis Output Registry workspace → /studio/isis/output-registry
  • Open Isis Retention Policies workspace → /studio/isis/retention-policies
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads / writes: none from this composition directly; delegated to child lanes under their own exact contracts
  • Outputs state: no aggregate artifact, publication, provenance, diagnostic, parity, or governance record
  • Operations: no publish, release, provenance certification, remediation, permission, audit, approval, or release action
  • Static fixture: the former source-defined generated-artifact provenance panel was removed because it was neither live nor durable evidence
  • 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/StudioIsisOutputsWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisOutputsRouteMap.ts

Cross-references#

Open questions / known gaps#

  • Artifact, release, diagnostics, parity, and governance paths are documented shapes only, with no pages or corresponding aggregator authority
  • There is no standalone Outputs control plane, aggregate artifact or publication store, provenance/evidence record, parity certification, governance, approval, or release authority here
  • The Output Registry child itself composes further lanes, producing a deep page whose desktop E2E proof requires an explicit 120-second test budget