V1 Web PWA · Surface walkthrough

Isis Client

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/client · 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/client/page.tsx

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

Purpose#

UI-only, non-authoritative composition of four independent Isis workspaces: Client SDK, CLI, Generation API, and Integration Events. Each child retains its own exact contract and state. The composition has no Client endpoint, retained session or delivery state, diagnostics or audit record, 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-client-breadcrumbs): Studio → Isis Client SDK → (current)
  • Workspace panel (data-isis-client-workspace):
    • <h1> "Isis Client Workspace"
    • Honest summary and exact ui_only_non_authoritative_embedded_lane_composition disposition
    • Composition Boundary with four cards: independent lane authority, no Client endpoint, no session/delivery authority, and no governance/release authority
    • Four embedded lanes: Client SDK, CLI, Generation API, and Integration Events
  • Route map panel (data-isis-client-route-map): one mounted-composition and five documented-contract entries
  • Quick-actions panel: links to Client SDK, CLI, 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#

  • Client SDK / CLI / Generation API / 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 Client SDK workspace → /studio/isis/client-sdk
  • Open Isis CLI workspace → /studio/isis/cli
  • 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
  • Client state: no aggregate session, credential, delivery, diagnostic, parity, audit, or governance record
  • Operations: no session control, credential operation, delivery, parity certification, remediation, audit, 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/StudioIsisClientWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisClientRouteMap.ts

Cross-references#

Open questions / known gaps#

  • Session, release, diagnostics, parity, and governance paths are documented shapes only, with no pages or corresponding aggregator authority
  • There is no standalone Client control plane, retained session/credential store, delivery workflow, diagnostic/audit record, parity certification, governance, approval, or release authority here