--- path: /studio/isis/database 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/database/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, route status, touch targets, responsive containment, and applicable axe verified' --- # Isis Database ## Purpose UI-only, non-authoritative composition of five independent Isis workspaces: Output Registry, Model Registry, Collection Management, Lineage Graph, and Retention Policies. Each child retains its own exact contract and state. The composition has no Isis Database aggregator endpoint, retained cluster or snapshot state, database operation, diagnostic or evidence authority, parity run, governance record, or release decision. The real `@isis/database` Prisma-backed library is a separate backend substrate. This wrapper does not import, query, migrate, back up, restore, or administer that library. ## Entry points - Sibling quick-actions from `/studio/isis/output-registry`, `/studio/isis/model-registry`, `/studio/isis/retention-policies` - Studio index (`/studio`) - Direct URL / bookmark (AAA-gated) ## Layout regions `page.tsx` mounts `` with a breadcrumb panel, the workspace, the Route Map, and sibling quick-actions. - **Header**: shell header - **Breadcrumb panel** (`data-isis-database-breadcrumbs`) - **Workspace panel** (`data-isis-database-workspace`): - `

` (`WorkspaceHeading`) "Isis Database Workspace" - Honest summary and exact `ui_only_non_authoritative_embedded_lane_composition` disposition - **Composition Boundary** (`data-isis-database-capability-summary`) with four cards: independent lane authority, no Isis Database endpoint, no database operations/evidence authority, and no governance/release authority - **Output Registry Lane** (`data-isis-database-output-registry-lane`) — `StudioIsisOutputRegistryWorkspace` - **Model Registry Lane** (`data-isis-database-model-registry-lane`) — `StudioIsisModelRegistryWorkspace` - **Collection Management Lane** (`data-isis-database-collection-management-lane`) — `StudioIsisCollectionManagementWorkspace` - **Lineage Graph Lane** (`data-isis-database-lineage-graph-lane`) — `StudioIsisLineageGraphWorkspace` - **Retention Policies Lane** (`data-isis-database-retention-policies-lane`) — `StudioIsisRetentionPoliciesWorkspace` - **Route Map panel** (`data-isis-database-route-map`): one `mounted-composition` and five `documented-contract` entries - **Sibling quick-actions panel**: `/studio/isis/output-registry`, `/studio/isis/model-registry`, `/studio/isis/retention-policies`, `/studio` ## States No fetch at the composition level. Each child lane manages its own loading, unauthorized, error, ready, and result states. - [ ] **Output Registry Lane** — see [`studio-isis-output-registry.md`](./studio-isis-output-registry.md) - [ ] **Model Registry Lane** — see [`studio-isis-model-registry.md`](./studio-isis-model-registry.md) - [ ] **Collection Management Lane** — see [`studio-isis-collection-management.md`](./studio-isis-collection-management.md) - [ ] **Lineage Graph Lane** — see [`studio-isis-lineage-graph.md`](./studio-isis-lineage-graph.md) - [ ] **Retention Policies Lane** — see [`studio-isis-retention-policies.md`](./studio-isis-retention-policies.md) - [ ] **Gated** — the Database route is production-hard-blocked ## Interactions ### Composition boundary - [ ] **Boundary cards** ×4 — non-interactive and authority-limiting ### Embedded lanes - [ ] Output Registry / Model Registry / Collection Management / Lineage Graph / Retention Policies — walk each in its own doc ### Route Map - [ ] **Mounted composition** ×1 - [ ] **Documented route shapes without pages or authority** ×5 ### Sibling quick-actions - [ ] **Open Isis Output Registry workspace** → `/studio/isis/output-registry` - [ ] **Open Isis Model Registry workspace** → `/studio/isis/model-registry` - [ ] **Open Isis Retention Policies workspace** → `/studio/isis/retention-policies` - [ ] **Back to Studio workspace index** → `/studio` ## Data & contracts - **Reads / writes**: none from this composition directly; delegated to child lanes under their own exact contracts - **Database state**: no cluster, snapshot, backup, restore, migration, diagnostic, parity, or governance record - **Operations**: no database query, migration, backup, restore, diagnostic trace, remediation, permission, audit, certification, approval, or release action - **Backend distinction**: `@isis/database` exists as a real Prisma-backed substrate but is not bound to this wrapper - **Realtime**: none - **Auth/role check**: AAA-gated Studio route behind the signed-in + studio proxy gate; embedded lanes are individually admin-scoped and fail closed - **Component sources**: - `apps/oshun/web/src/components/studio/StudioIsisDatabaseWorkspace.tsx` - `apps/oshun/web/src/components/studio/StudioIsisDatabaseRouteMap.ts` ## Cross-references - Studio overview: [`../../studio-overview.md`](../../studio-overview.md) - Embedded routes: - [`studio-isis-output-registry.md`](./studio-isis-output-registry.md) - [`studio-isis-model-registry.md`](./studio-isis-model-registry.md) - [`studio-isis-collection-management.md`](./studio-isis-collection-management.md) - [`studio-isis-lineage-graph.md`](./studio-isis-lineage-graph.md) - [`studio-isis-retention-policies.md`](./studio-isis-retention-policies.md) ## Open questions / known gaps - [ ] Cluster, snapshot, diagnostics, parity, and governance paths are documented shapes only, with no pages or corresponding aggregator authority - [ ] There is no standalone Database control plane, cluster/snapshot store, backup/restore workflow, diagnostic/evidence record, parity certification, governance, approval, or release authority here - [ ] This route does not provide a unified view over the real `@isis/database` substrate