V1 Web PWA · Surface walkthrough

Isis Anomaly Detection

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/anomaly-detection · auth signed-in + Studio Isis production hard-block; localhost E2E lane bypass for focused workspace automation · source apps/oshun/web/src/app/studio/isis/anomaly-detection/page.tsx

Last walked. 2026-07-23 isolated Playwright desktop/mobile walk — localhost lane entry, composition disposition, absence of an aggregator API call, five embedded lanes, one mounted/five documented route statuses, responsive containment, 44-pixel navigation, and applicable axe coverage passed; production direct navigation remains hard-blocked and manual screen-reader/PWA checks remain open

Purpose#

UI-only, non-authoritative composition of five independent Isis detection and quality workspaces: suspicious activity, artifact detection, content safety, automated quality scoring, and model quality assessment. Each lane owns its own contract. The aggregator has no endpoint, cross-lane state, incident control, diagnostics, governance record, or release authority.

Entry points#

  • Breadcrumb / quick-action card from /studio/isis/content-safety
  • Sibling quick-actions from the embedded lanes' own routes
  • Studio index (/studio)
  • Direct URL / bookmark

Layout regions#

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

  • Breadcrumb panel (data-isis-anomaly-detection-breadcrumbs): Studio → Isis Content Safety → Anomaly Detection (aria-current="page")
  • Workspace panel (data-isis-anomaly-detection-workspace):
    • <h1> "Isis Anomaly Detection Workspace" (WorkspaceHeading)
    • Summary paragraph (data-isis-anomaly-detection-summary)
    • Composition Boundary panel (data-isis-anomaly-detection-capability-summary, <h2>) with the explicit disposition (data-isis-anomaly-detection-disposition) and 4 boundary cards (data-isis-anomaly-detection-capability)
    • Five embedded lanes, each an <h2> panel wrapping a sibling workspace via WorkspaceSection (headings demote to <h3>):
      • Suspicious Activity Detection Lane (data-isis-anomaly-detection-suspicious-activity-lane)
      • Artifact Detection Lane (data-isis-anomaly-detection-artifact-lane)
      • Content Safety Lane (data-isis-anomaly-detection-content-safety-lane)
      • Automated Quality Scoring Lane (data-isis-anomaly-detection-quality-scoring-lane)
      • Model Quality Assessment Lane (data-isis-anomaly-detection-model-quality-lane)
  • Route map panel (data-isis-anomaly-detection-route-map): <h2> "Route Map" enumerating one mounted-composition entry and five documented-contract route shapes
  • Quick-actions panel: quickAction links to /studio/isis/suspicious-activity-detection, /studio/isis/artifact-detection, /studio/isis/content-safety, and "Back to Studio workspace index" → /studio

States#

The aggregator has no fetch; each embedded lane drives its own Loading / Unauthorized (admin-scope 401/403) / Error / Ready / Result states — see the per-lane docs below.

Interactions#

Embedded lanes#

  • Suspicious Activity Detection Lane — transaction chargeback screening form + list
  • Artifact Detection Lane — artifact-detection lane
  • Content Safety Lane — content-safety lane
  • Automated Quality Scoring Lane — quality-scoring lane
  • Model Quality Assessment Lane — model-quality lane

Composition boundary#

  • Boundary cards ×4 — independent lane authority, no aggregator endpoint, no cross-lane operations, and no governance/release authority

Route map#

  • Mounted composition route ×1
  • Documented-contract-only route shapes ×5

Quick-actions#

  • Open Isis Suspicious Activity Detection workspace → /studio/isis/suspicious-activity-detection
  • Open Isis Artifact Detection workspace → /studio/isis/artifact-detection
  • Open Isis Content Safety workspace → /studio/isis/content-safety
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads / writes: none from this aggregator directly — delegated to the embedded sibling lanes, each of which calls its own admin /v1 endpoint
  • Realtime: None
  • Caching: delegated to embedded lanes (client fetch on mount, no-store)
  • Disposition: ui_only_non_authoritative_embedded_lane_composition; persistence delegated per lane, no aggregator endpoint or state, no cross-lane correlation/threshold/incident/diagnostics authority, no governance record, no release authority, and no authoritative state
  • Auth: admin-scoped fail-closed per embedded lane; route behind the signed-in + Studio Isis production hard-block. Focused automation uses the localhost-only lane bypass and separately observed the direct 404 boundary.
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsisAnomalyDetectionWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisAnomalyDetectionRouteMap.ts

Cross-references#

Open questions / known gaps#

  • No aggregator API, persistence, or cross-lane correlation
  • No signal inventory, thresholds, triage, incidents, diagnostics, parity runs, remediation, or escalation authority
  • No aggregator audit record, policy decision, approval, or release authority
  • /signals, /incidents, /diagnostics, /parity, and /governance remain documented shapes, not implemented pages
  • Manual live screen-reader, installed-PWA, and telemetry-delivery checks remain open