V1 Web PWA · Surface walkthrough

Isis 3D Result Management

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/3d-result-management · auth signed-in + studio entitlement (AAA-gated — segment 3d-result-management in AAA_ONLY_STUDIO_ROUTES) · source apps/oshun/web/src/app/studio/isis/3d-result-management/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#

Admin lane console that wires the real @isis/3d-post-pipeline mesh-topology analyzer: the operator pastes an indexed mesh (vertex positions + triangle indices) and gets the acceptance verdict the post pipeline runs over a generated 3D result — closed / manifold / watertight, plus boundary-edge, non-manifold-edge, and degenerate-face counts. All reads and writes flow through /v1/admin/isis/3d-result-management; it is admin-scoped and fails closed.

Entry points#

  • Sibling quick-action from /studio/isis/reference-image-processing
  • Studio index (/studio)
  • Direct URL / bookmark (AAA entitlement required)

Layout regions#

page.tsx mounts <ShellLayout active="studio"> (no breadcrumb panel) and three panels: the workspace, the Route Map, and sibling quick-actions.

  • Header: shell header
  • Workspace panel (data-isis-3d-result-management-workspace):
    • <h1> (WorkspaceHeading) "Isis 3D Result Management Workspace"
    • Summary paragraph (data-isis-3d-result-management-summary)
    • Topology-analyzer form (data-isis-rm-analyze-form), seeded with a solid tetrahedron (closed + manifold + watertight)
  • Route Map panel (data-isis-3d-result-management-route-map): <h2>Route Map</h2> over STUDIO_ISIS_3D_RESULT_MANAGEMENT_ROUTE_MAP (5 entries)
  • Sibling quick-actions panel: /studio/isis/reference-image-processing, /studio

States#

  • Loading — outcome === null; data-isis-rm-loading "Loading topology analyzer…"
  • Unauthorized — 401/403 admin-scope fail-closed; data-isis-rm-unauthorized ("Isis workspace scope required to view 3D result management.")
  • Error — non-OK or malformed catalog; data-isis-rm-error
  • Ready (form) — catalog present; positions + indices inputs render
  • Result — after an analyze POST, data-isis-rm-result shows the manifold / watertight verdicts plus boundary edges, non-manifold edges and degenerate-face counts; analyze failures surface in data-isis-rm-analyze-error

Interactions#

Topology-analyzer form (data-isis-rm-analyze-form)#

  • Vertex positions (flat x,y,z list) (data-isis-rm-field-positions, text input, aria-label="vertex positions")
  • Triangle indices (flat list) (data-isis-rm-field-indices, text input, aria-label="triangle indices")
  • Submit (data-isis-rm-analyze-submit) — POST /v1/admin/isis/3d-result-management/analyze-topology

Route Map#

  • Route-map articles ×5

Sibling quick-actions#

  • Open Isis Reference Image Processing workspace → /studio/isis/reference-image-processing
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads: GET /v1/admin/isis/3d-result-management (analyzer catalog)
  • Writes: POST /v1/admin/isis/3d-result-management/analyze-topology (returns the topology verdict: isManifold, isWatertight, boundaryEdgeCount, nonManifoldEdgeCount, degenerateFaceCount)
  • Realtime: none
  • Caching: client fetch on mount, cache: 'no-store', buildBffAuthHeaders()
  • Auth/role check: admin-scoped, fail-closed (401/403); route gated on signed-in + studio entitlement (AAA segment)
  • Component sources:
    • apps/oshun/web/src/components/studio/StudioIsis3DResultManagementWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsis3DResultManagementRouteMap.ts

Cross-references#

Open questions / known gaps#

  • No breadcrumb on this route — navigation is via sibling quick-actions
  • This analyzer overlaps with /studio/isis/topology-verification (verifyTopology); confirm the division of responsibility between the post-pipeline acceptance check and standalone topology verification