V1 Web PWA · Surface walkthrough

Isis AI Providers

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/ai-providers · auth signed-in + studio entitlement (AAA-gated — segment ai-providers in AAA_ONLY_STUDIO_ROUTES) · source apps/oshun/web/src/app/studio/isis/ai-providers/page.tsx

Last walked. 2026-05-29 automated runtime walk (Playwright headless) — render, /v1 data (2xx), console/page-errors, expected content, screenshot verified; live screen-reader, touch, offline, and telemetry-delivery checks pending a manual AT pass. Evidence: WALKTHROUGH/results/runtime-sweep-2026-05-29.md; body re-derived 2026-06-03 from current source (lane-console architecture)

Purpose#

Aggregator console for the Isis provider control plane. It composes three sibling lane workspaces — Provider Factory, Provider Integration, and Unified Provider Architecture — under a single AI Providers heading and a Capability Summary. It owns no /v1 fetch of its own; each embedded lane runs its own admin-scoped, fail-closed backend call.

Entry points#

  • Breadcrumb in-page (data-isis-ai-providers-breadcrumbs)
  • Sibling quick-actions: /studio/isis/provider-factory, /studio/isis/provider-integration, /studio/isis/unified-provider-architecture
  • Studio index (/studio)
  • Direct URL / bookmark (AAA entitlement required)

Layout regions#

page.tsx mounts <ShellLayout active="studio"> plus a breadcrumb panel, the workspace, the Route Map, and sibling quick-actions.

  • Header: shell header
  • Breadcrumb panel (data-isis-ai-providers-breadcrumbs)
  • Workspace panel (data-isis-ai-providers-workspace):
    • <h1> (WorkspaceHeading) "Isis AI Providers Workspace"
    • Summary paragraph (data-isis-ai-providers-summary)
    • Capability Summary (data-isis-ai-providers-capability-summary, <h2>Capability Summary</h2>, 4 data-isis-ai-providers-capability=<id> articles: provider-control-plane, diagnostics-and-trace-observability, security-permission-audit-controls, api-parity-and-contract-assurance)
    • Provider Factory Lane (data-isis-ai-providers-provider-factory-lane, <h2>Provider Factory Lane</h2>) → StudioIsisProviderFactoryWorkspace
    • Provider Integration Lane (data-isis-ai-providers-provider-integration-lane) → StudioIsisProviderIntegrationWorkspace
    • Unified Provider Architecture Lane (data-isis-ai-providers-unified-provider-architecture-lane) → StudioIsisUnifiedProviderArchitectureWorkspace
  • Route Map panel (data-isis-ai-providers-route-map): <h2>Route Map</h2> over the route map (6 entries)
  • Sibling quick-actions panel: /studio/isis/provider-factory, /studio/isis/provider-integration, /studio/isis/unified-provider-architecture, /studio

States#

Per embedded lane (each manages its own loading / unauthorized / error / ready / result):

Interactions#

Capability Summary#

  • Capability article ×4 — non-interactive

Embedded lanes#

  • Provider Factory Lane — walk in its own doc
  • Provider Integration Lane — walk in its own doc
  • Unified Provider Architecture Lane — walk in its own doc

Route Map#

  • Route-map articles ×6

Sibling quick-actions#

  • Open Isis Provider Factory workspace → /studio/isis/provider-factory
  • Open Isis Provider Integration workspace → /studio/isis/provider-integration
  • Open Isis Unified Provider Architecture workspace → /studio/isis/unified-provider-architecture
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads / writes: none from this route directly; each embedded lane owns its own admin-scoped /v1/admin/isis/... reads and writes
  • Realtime: none
  • Auth/role check: route AAA-gated (ai-providers in AAA_ONLY_STUDIO_ROUTES); embedded lanes are individually admin-scoped and fail closed
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsisAiProvidersWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisAiProvidersRouteMap.ts

Cross-references#

Open questions / known gaps#

  • Aggregator owns no backend call; coverage depends on each embedded lane's own walkthrough
  • Route-map sub-paths are declared but not yet implemented as separate pages