Context. surface studio · domain isis · route /studio/isis/nvidia-rtx-processing · auth signed-in + studio entitlement (AAA-gated — nvidia-rtx-processing is in AAA_ONLY_STUDIO_ROUTES) · source apps/oshun/web/src/app/studio/isis/nvidia-rtx-processing/page.tsx
Last walked. 2026-07-23 exact-production-BFF Playwright (desktop Chromium + Pixel 7 mobile Chrome) — hard route boundary, signed-JWT exact/no-store contracts, adversarial authority rejection, 44px controls, responsive containment, and applicable axe checks passed; live screen-reader and telemetry-delivery checks remain manual.
Purpose#
Admin lane console for a request-local, non-authoritative 4× super-resolution plan preview. The operator supplies bounded frame metadata; the deterministic planner computes output dimensions, tiled inference arithmetic, model/backend selection, passes, scores, and warnings. It does not ingest media, execute NVIDIA RTX or another GPU/provider, create an artifact, persist history, record governance, or authorize release.
Entry points#
- Sibling quick-action from
/studio/isis/ai-video-generation - 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-nvidia-rtx-processing-workspace):<h1>(WorkspaceHeading) "Isis NVIDIA RTX Processing Workspace"- Summary paragraph (
data-isis-nvidia-rtx-processing-summary) - Plan form (
data-isis-rtx-plan-form) - Result (
data-isis-rtx-result) withdata-isis-rtx-output,data-isis-rtx-scale,data-isis-rtx-passes,data-isis-rtx-inference,data-isis-rtx-quality,data-isis-rtx-scores,data-isis-rtx-model,data-isis-rtx-warnings
- Route Map panel (
data-isis-nvidia-rtx-processing-route-map):<h2>Route Map</h2>over one mounted planner and four documented-contract-only shapes - Sibling quick-actions panel:
/studio/isis/ai-video-generation,/studio
States#
- Loading —
data-isis-rtx-loading"Loading 4x planner…" - Unauthorized — 401/403 admin-scope fail-closed;
data-isis-rtx-unauthorized - Error — non-OK / malformed;
data-isis-rtx-error - Ready (form) — exact disposition and plan form render
- Result —
data-isis-rtx-resultafter planning; plan failure →data-isis-rtx-plan-error
Interactions#
Plan form (data-isis-rtx-plan-form)#
- Width (
data-isis-rtx-field-width, input,aria-label="source width") - Height (
data-isis-rtx-field-height, input,aria-label="source height") - Content profile (
data-isis-rtx-field-profile,<select>) - Backend (
data-isis-rtx-field-backend,<select>) - Model (
data-isis-rtx-field-model,<select>) - Plan 4x pass (
data-isis-rtx-plan-submit, submit) —POST /v1/admin/isis/nvidia-rtx-processing/plan
Route Map#
- Route-map articles ×5 with mounted/documented-contract status
Sibling quick-actions#
- Open Isis AI Video Generation workspace →
/studio/isis/ai-video-generation - Back to Studio workspace index →
/studio
Data & contracts#
- Reads:
GET /v1/admin/isis/nvidia-rtx-processing, exactly{generatedAt, scale, models, backends, contentProfiles, inputBounds, disposition} - Writes:
POST /v1/admin/isis/nvidia-rtx-processing/plan, accepting only frames plus bounded optional backend/model/batch name and returning exactly{ok, input, result, disposition}on success - Disposition:
request_local_non_authoritative_four_x_super_resolution_plan_preview; persistencenone; retentionrequest_only; caller-supplied frame metadata; source-defined model catalog; deterministic planner; no asset ingest, GPU/provider execution, artifact output, governance record, release authority, or authoritative state - Bounds: 1–256 unique frames; trimmed ids of 1–128 characters; integer dimensions up to 1920×1080; six normalized metrics in [0,1]; exact source-defined profile/backend/model enums; optional trimmed batch name of 1–160 characters
- Validation: the browser requires exact catalog, disposition, normalized input echo, model plan, frame plan, tile plan, summary, and warnings shapes. It independently checks source/output dimensions, 4× pixel arithmetic, aggregate pixel totals, frame count, selected model/backend consistency, finite bounded scores, and positive estimates before rendering. Missing, extra, malformed, incorrectly echoed, arithmetically inconsistent, or authority-inflated successes fail closed.
- Realtime: none
- Caching: client fetches with
cache: 'no-store'; authenticated scoped BFF success and failure responses also emitcache-control: no-store - Auth/role check: admin-scoped, fail-closed (401/403); route AAA-gated
(
nvidia-rtx-processinginAAA_ONLY_STUDIO_ROUTES) - Component sources:
apps/oshun/web/src/components/studio/StudioIsisNvidiaRtxProcessingWorkspace.tsxapps/oshun/web/src/components/studio/StudioIsisNvidiaRtxProcessingRouteMap.ts
Automated coverage#
- The focused BFF route suite covers auth/scope denial, exact catalog and disposition, no-store behavior, normalized input echo, deterministic 4× arithmetic, envelope rejection, malformed enums, extra authority fields, duplicate ids, and all published bounds.
- The focused web component/integration suites cover exact catalog loading, visible disposition, unauthorized and authority-inflated catalog states, exact POST/render behavior, client-side bounds, and arithmetically inflated success suppression.
apps/oshun/web/e2e/studio-isis-nvidia-rtx-processing.spec.tspassed 4/4 with one worker and zero retries against the exact production BFF artifact, disposable PostgreSQL with all 32 migrations, isolated Redis, and signed production JWTs. Desktop Chromium covers the hard boundary, direct exact and no-store contracts, adversarial requests/responses, honest route status, 44-pixel controls, and applicable axe checks. Pixel 7 mobile Chrome covers touch targets, containment, and a live rendered result.
Cross-references#
- Studio overview:
../../studio-overview.md - AAA gating:
libs/isis/entitlements/src/studio-boundary.ts - Sibling routes:
Open questions / known gaps#
- No breadcrumb on this route — navigation via sibling quick-actions
- Frame-asset ingest, GPU/provider execution, generated artifacts, durable history, governance approval, and release remain unbound
- Four scene, export, revision, and governance shapes are documented-contract-only; no corresponding authority is mounted