V1 Web PWA · Surface walkthrough

Isis Topology Verification

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/topology-verification · auth signed-in + studio entitlement (AAA-gated — topology-verification is in AAA_ONLY_STUDIO_ROUTES) · source apps/oshun/web/src/app/studio/isis/topology-verification/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 §24.9 lane console that verifies 3D mesh topology via the real three-d-pipelines verifyTopology (zero-faces / degenerate-faces / non-manifold-edges / not-watertight / zero-volume detection). It loads example meshes from GET /v1/admin/isis/topology/examples and verifies an arbitrary mesh via POST …/topology/verify. It is admin-scoped and fails closed.

Entry points#

  • Sibling quick-action from /studio/isis/3d-post-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-topology-verification-workspace):
    • <h1> (WorkspaceHeading) "Isis Topology Verification Workspace"
    • Summary paragraph (data-isis-topology-verification-summary)
    • Example-mesh list (data-topology-examples, each data-topology-example=<slug> — clicking loads the mesh into the form)
    • Verify form (data-topology-form)
  • Route Map panel (data-isis-topology-verification-route-map): <h2>Route Map</h2> over STUDIO_ISIS_TOPOLOGY_VERIFICATION_ROUTE_MAP (5 entries)
  • Sibling quick-actions panel: /studio/isis/3d-post-processing, /studio

States#

  • Loading — data-topology-loading
  • Unauthorized — 401/403 admin-scope fail-closed; data-topology-unauthorized
  • Error — non-OK or malformed examples; data-topology-error
  • Ready (form) — examples present; mesh fields + checkboxes render
  • Result — after a verify POST, data-topology-report (data-topology-report-valid=valid|invalid) listing each data-topology-issue; verify-time errors surface in data-topology-report-status="error"

Interactions#

Verify form (data-topology-form)#

  • Mesh fields (data-topology-field=<field>) — the mesh vertices/indices (populated by loading an example or pasted manually)
  • Watertight (data-topology-watertight, checkbox) — declared watertight flag on the mesh
  • Require watertight (data-topology-require-watertight, checkbox) — gate the verdict on watertightness
  • Verify topology (data-topology-verify, button; "Verifying…" while in flight) — POST /v1/admin/isis/topology/verify

Example meshes#

  • Load example (data-topology-example=<slug>) — loads the example mesh into the verify form

Route Map#

  • Route-map articles ×5

Sibling quick-actions#

  • Open Isis 3D Post-Processing workspace → /studio/isis/3d-post-processing
  • Back to Studio workspace index → /studio

Data & contracts#

  • Reads: GET /v1/admin/isis/topology/examples (example meshes)
  • Writes: POST /v1/admin/isis/topology/verify (verify a mesh; returns { valid, issues })
  • 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/StudioIsisTopologyVerificationWorkspace.tsx
    • apps/oshun/web/src/components/studio/StudioIsisTopologyVerificationRouteMap.ts

Cross-references#

Open questions / known gaps#

  • No breadcrumb on this route — navigation is via sibling quick-actions
  • Overlaps with /studio/isis/3d-result-management's post-pipeline analyzer; confirm the responsibility split between standalone verification and the acceptance gate