---
path: /studio/isis/gpu-worker
surface: studio
domain: isis
auth:
  signed-in + studio entitlement; Studio Isis production boundary hard-blocks
  this AAA-only route. Automated lane verification uses the explicit
  localhost-only E2E bypass.
source: apps/oshun/web/src/app/studio/isis/gpu-worker/page.tsx
status: walked
last_walked:
  '2026-07-23 automated desktop Chromium + Pixel 7 mobile walk — production
  hard-block, localhost-only lane entry, explicit composition boundary, five
  child lanes, absence of an aggregator request and worker authority, route
  status, touch targets, responsive containment, and applicable axe verified'
---

# Isis GPU Worker

## Purpose

UI-only, non-authoritative composition of five independent Isis workspaces:
generation API, CLI, integration events, resource recommendations, and
suspicious activity detection. Each child retains its own exact contract and
state. The composition has no GPU Worker aggregator endpoint, fleet, pool,
queue, job, scheduling/execution control, parity run, governance record, or
release authority.

## Entry points

- Breadcrumb / quick-action card from `/studio/isis/generation-api`
- Embedded as a "GPU Worker Lane" in several Isis aggregators
- Studio index (`/studio`)
- Direct URL / bookmark (AAA-gated)

## Layout regions

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

- **Breadcrumb panel** (`data-isis-gpu-worker-breadcrumbs`): Studio → Isis
  Generation API → (current)
- **Workspace panel** (`data-isis-gpu-worker-workspace`):
  - `<h1>` "Isis GPU Worker Workspace" (`WorkspaceHeading`) + summary
    (`data-isis-gpu-worker-summary`) and exact
    `ui_only_non_authoritative_embedded_lane_composition` disposition
    (`data-isis-gpu-worker-disposition`)
  - Composition Boundary panel (`data-isis-gpu-worker-capability-summary`,
    `<h2>`) with four honest cards
  - Five embedded lanes, each an `<h2>` panel wrapping a sibling workspace via
    `WorkspaceSection`:
    - Generation API Lane (`data-isis-gpu-worker-generation-api-lane`)
    - CLI Lane (`data-isis-gpu-worker-cli-lane`)
    - Integration Events Lane (`data-isis-gpu-worker-integration-events-lane`)
    - Resource Recommendations Lane
      (`data-isis-gpu-worker-resource-recommendations-lane`)
    - Suspicious Activity Detection Lane
      (`data-isis-gpu-worker-suspicious-activity-detection-lane`)
- **Route map panel** (`data-isis-gpu-worker-route-map`): `<h2>` "Route Map"
  over one `mounted-composition` entry and five `documented-contract` entries
- **Quick-actions panel**: `quickAction` links to `/studio/isis/generation-api`,
  `/studio/isis/cli`, `/studio/isis/integration-events`,
  `/studio/isis/resource-recommendations`, and "Back to Studio workspace index"
  → `/studio`

## States

No fetch at the aggregator; each embedded lane drives its own Loading /
Unauthorized (admin-scope 401/403) / Error / Ready / Result states.

- [ ] **Generation API Lane** — walk via
      [`studio-isis-generation-api.md`](./studio-isis-generation-api.md)
- [ ] **CLI Lane** — walk via [`studio-isis-cli.md`](./studio-isis-cli.md)
- [ ] **Integration Events Lane** — walk via
      [`studio-isis-integration-events.md`](./studio-isis-integration-events.md)
- [ ] **Resource Recommendations Lane** — walk via
      [`studio-isis-resource-recommendations.md`](./studio-isis-resource-recommendations.md)
- [ ] **Suspicious Activity Detection Lane** — walk via
      [`studio-isis-suspicious-activity-detection.md`](./studio-isis-suspicious-activity-detection.md)

## Interactions

### Embedded lanes

- [ ] **Generation API Lane**
- [ ] **CLI Lane**
- [ ] **Integration Events Lane**
- [ ] **Resource Recommendations Lane**
- [ ] **Suspicious Activity Detection Lane**

### Composition boundary

- [ ] **Boundary cards** ×4 — non-interactive and authority-limiting

### Route map

- [ ] **Mounted composition** ×1
- [ ] **Documented route shapes without pages or authority** ×5

### Quick-actions

- [ ] **Open Isis Generation API workspace** → `/studio/isis/generation-api`
- [ ] **Open Isis CLI workspace** → `/studio/isis/cli`
- [ ] **Open Isis Integration Events workspace** →
      `/studio/isis/integration-events`
- [ ] **Open Isis Resource Recommendations workspace** →
      `/studio/isis/resource-recommendations`
- [ ] **Back to Studio workspace index** → `/studio`

## Data & contracts

- **Reads / writes**: none from this composition directly — delegated to the
  embedded sibling lanes, each calling its own `/v1` endpoint
- **Worker controls**: none; no fleet/pool inventory, queue/job state,
  scheduling, execution, retry/cancellation, utilization, throughput, logs,
  traces, parity certification, governance, or release action is bound here
- **Realtime**: None
- **Caching**: delegated to embedded lanes (client fetch on mount, no-store)
- **Auth**: admin-scoped fail-closed per embedded lane; AAA-gated studio route
  behind the signed-in + studio proxy gate
- **Component sources**:
  - `apps/oshun/web/src/components/studio/StudioIsisGpuWorkerWorkspace.tsx`
  - `apps/oshun/web/src/components/studio/StudioIsisGpuWorkerRouteMap.ts`

## Cross-references

- Studio overview: [`../../studio-overview.md`](../../studio-overview.md)
- Embedded lanes:
  - [`studio-isis-generation-api.md`](./studio-isis-generation-api.md)
  - [`studio-isis-cli.md`](./studio-isis-cli.md)
  - [`studio-isis-integration-events.md`](./studio-isis-integration-events.md)
  - [`studio-isis-resource-recommendations.md`](./studio-isis-resource-recommendations.md)
  - [`studio-isis-suspicious-activity-detection.md`](./studio-isis-suspicious-activity-detection.md)

## Open questions / known gaps

- [ ] Job, pool, evidence, parity, and governance paths are documented shapes
      only, with no pages or corresponding aggregator authority
- [ ] There is no GPU-worker fleet/queue dashboard, scheduling/execution
      service, evidence record, parity certification, or release authority here