Status: Accepted v1.0
Owner: OSHUN Design + Product + Engineering
Last Updated: March 26, 2026
Implements: V1-UX-047
Related:
docs/releases/v1/specs/todos.mddocs/releases/v1/specs/web-app-admin-v1-prd.mddocs/releases/v1/design/customer-visual-thesis.mddocs/releases/v1/design/admin-visual-thesis.mddocs/releases/v1/runbooks/beta-program.mddocs/releases/v1/reports/unified-product-gap-analysis-and-nisaba-integration-report-2026-03-22.mddocs/releases/v1/specs/public-web-and-app-distribution-tracking.mddocs/releases/v1/specs/readme.md
1. Purpose#
This document is the current-state redesign inventory for every major OSHUN V1 surface that materially affects customer or operator experience.
It is based on the current repository implementation on March 26, 2026. Its job is to answer one question clearly before redesign sequencing begins:
What major surfaces actually exist today, where are they implemented, and what experience posture do they currently present?
2. Coverage Rules#
The inventory includes:
- authenticated customer web and PWA shell surfaces
- public OSHUN web surfaces that shape first impression and app distribution
- authenticated customer mobile shell surfaces
- current admin web and Studio cockpit surfaces
- explicit admin mobile gaps where launch-critical product scope exists in the PRD but no dedicated product surface exists yet
- persistent overlays and shared shells when they materially shape the experience
The inventory does not treat the following as major redesign-driving surfaces:
- unit-test routes
- demo-only welcome test pages in
apps/oshun/web/src/app/welcome/test-* - legal pages, which are customer-facing but not primary redesign drivers for V1-UX-047
2.1 State Labels#
implemented: active route or persistent UI surface exists in product codeprototype: route exists and is substantial, but still reads as a workbench/workspace prototype rather than a launch-finished productmissing: PRD or program scope requires the surface, but no dedicated product route/app exists yet
3. Inputs Reviewed#
- authenticated web routes in
apps/oshun/web/src/app - mobile routes in
apps/oshun/mobile/app - Studio route families in
apps/oshun/web/src/app/studio - customer and operator shell primitives in
apps/oshun/web/src/componentsandapps/oshun/mobile/src docs/releases/v1/runbooks/beta-program.mdfor launch-critical customer journeysdocs/releases/v1/specs/web-app-admin-v1-prd.mdfor admin web/admin mobile target posturedocs/releases/v1/reports/unified-product-gap-analysis-and-nisaba-integration-report-2026-03-22.mdsection 16.4 for admin-surface gap framing
4. Customer Web and PWA Inventory#
| Surface | Entrypoints | State | Current posture |
|---|---|---|---|
| Shared shell chrome and persistent overlays | apps/oshun/web/src/components/ShellLayout.tsx, CommandPalette.tsx, KeyboardShortcutHelp.tsx, FocusModeToggle.tsx, PwaInstallPrompt.tsx, apps/oshun/web/src/offline/GlobalOfflineBanner.tsx |
implemented | Border-first dark shell with sidebar/top bar, assistant entry, command palette, scroll affordances, and install/offline support. This is the main visual frame for all authenticated web use. |
| Home dashboard | apps/oshun/web/src/app/page.tsx, apps/oshun/web/src/components/home/* |
implemented | Dense dashboard-like home with hero, KPI grid, activity, routine, wearable, domain-card, and notification layers. Strong breadth, but already heavy enough to warrant redesign review. |
| Explore and discovery | apps/oshun/web/src/app/explore/page.tsx, DomainSwitcherEntryPanel.tsx, UniversalSearchPanel.tsx, ExploreDashboard.tsx, QuickActionsTrayPanel.tsx |
implemented | Cross-domain discovery surface with search, filters, dashboard modules, and operator-access note. Reads as a broad discovery workspace rather than a minimal browse flow. |
| Dedicated search results | apps/oshun/web/src/app/search/page.tsx, SearchResultsView.tsx |
implemented | Dedicated search route exists and is clearly separated from Explore, supporting domain-grouped results and filters. |
| Activity timeline and inbox | apps/oshun/web/src/app/activity/page.tsx, ActivityDashboard.tsx |
implemented | Unified timeline shell with hero framing, achievements, streaks, progress, and notifications orientation. |
| Library and continuity | apps/oshun/web/src/app/library/page.tsx, LibraryDashboard.tsx |
implemented | Saved-item and continuity surface with domain/kind filters and explicit handoff guidance back into home, explore, activity, and profile. |
| Profile, settings, and operator access handoff | apps/oshun/web/src/app/profile/page.tsx, ProfileSettingsPanel.tsx, OperatorAccessPanel.tsx |
implemented | Account-governance surface that also acts as the explicit privileged handoff into the admin shell. |
| Onboarding | apps/oshun/web/src/app/onboarding/page.tsx, components/onboarding/* |
implemented | Dedicated onboarding flow exists as a standalone wizard and is beta-critical. |
| Domain route experience | apps/oshun/web/src/app/domains/[domainId]/page.tsx, DomainRouteExperience.tsx |
implemented | Shared domain-route scaffold exists for Tara, Veritas, Nyx, Arete, and Nisaba. This is a major cross-domain cohesion surface. |
| Assistant, continuity, and disclosure surfaces | apps/oshun/web/src/components/assistant/*, NotificationsCenterPanel.tsx, DomainLaunchFailureTelemetry.tsx |
implemented | Assistant is integrated as a persistent shell capability rather than a separate route. Continuity, memory, and disclosure are major experience surfaces even though they are not top-level pages. |
| Public welcome landing | apps/oshun/web/src/app/welcome/page.tsx, WelcomePageView.tsx, SmartAppBanner.tsx |
implemented | Public marketing/entry surface exists and is part of launch-critical distribution scope. |
| Public domain marketing pages | apps/oshun/web/src/app/welcome/domains/page.tsx |
implemented | Public domain-explainer surface exists for Tara, Veritas, Nyx, Arete, and Nisaba. |
| Public download and install page | apps/oshun/web/src/app/welcome/download/page.tsx |
implemented | Public distribution surface exists for iOS, Android, and PWA install guidance. |
| Global loading, error, degraded, and not-found states | apps/oshun/web/src/app/loading.tsx, error.tsx, global-error.tsx, not-found.tsx, components/EmptyState.tsx, components/DomainDegradation.tsx, components/DomainErrorBoundary.tsx |
implemented | Core state surfaces exist and are launch-critical because beta scripts explicitly test loading, offline, and recovery behavior. |
5. Customer Mobile Inventory#
| Surface | Entrypoints | State | Current posture |
|---|---|---|---|
| Mobile shell, tab layout, and persistent helpers | apps/oshun/mobile/app/_layout.tsx, apps/oshun/mobile/app/(tabs)/_layout.tsx, MobileAssistantLauncher.tsx, MobileAssistantSheet.tsx, QuickActionsTray.tsx, DomainSwitcherEntry.tsx |
implemented | Main mobile shell exists with tab navigation, assistant sheet, quick actions, and domain switching. |
| Home tab | apps/oshun/mobile/app/(tabs)/index.tsx |
implemented | High-density mobile home with cross-domain recommendations, continue items, metrics, domain cards, and a capture-studio callout. |
| Explore tab | apps/oshun/mobile/app/(tabs)/explore.tsx |
implemented | Discovery-heavy surface with quick actions, domain switching, recommendation flows, and library previews. |
| Activity tab / notification inbox | apps/oshun/mobile/app/(tabs)/activity.tsx |
implemented | Unified activity and inbox surface with optimistic mutations, filters, grouped timeline items, and offline queue integration. |
| Library tab | apps/oshun/mobile/app/(tabs)/library.tsx, UnifiedLibraryView.tsx |
implemented | Preserve-oriented library surface with stats, assistant entry, and explicit shell-relationship framing. |
| Profile tab | apps/oshun/mobile/app/(tabs)/profile.tsx |
implemented | Deep settings surface with billing, privacy, exports, accessibility, session management, and account controls. |
| Domain detail route | apps/oshun/mobile/app/domain/[domainId].tsx |
implemented | Large shared domain surface that resolves Tara, Veritas, Nyx, Arete, and Nisaba-specific content, telemetry, entitlements, and offline fallback behavior. |
| Notification and alert settings components | apps/oshun/mobile/src/notifications/NotificationCenter.tsx, NotificationSettings.tsx |
implemented | Supporting mobile notification surfaces exist in code even though they are not yet primary app routes. |
| Offline and degraded-state surfaces | apps/oshun/mobile/src/offline/offline-provider.tsx, GlobalOfflineBanner.tsx, apps/oshun/mobile/src/__tests__/nonfunctional/api-resilience.test.ts |
implemented | Connectivity and queued-action posture exists and is explicitly launch-critical in beta scripts. |
| Specialized capture workflow | apps/oshun/mobile/app/mocap.tsx |
implemented | A mobile capture-studio workflow exists, but it is a specialized production tool rather than a general admin-mobile companion. |
| Dedicated mobile onboarding route | no dedicated route under apps/oshun/mobile/app |
missing | Onboarding is beta-critical, but there is no dedicated mobile onboarding route parallel to web. |
6. Admin Web and Studio Inventory#
6.1 Shared Operator Shell and Top-Level Studio Workspaces#
| Surface | Entrypoints | State | Current posture |
|---|---|---|---|
| Explicit admin shell boundary and operator chrome | libs/oshun/navigation/src/platform-shells.ts, apps/oshun/web/src/components/ShellLayout.tsx, apps/oshun/web/src/components/studio/* |
implemented | The repo already models customer/admin shell separation and uses dedicated Studio workspaces rather than hiding operator tooling inside normal customer navigation. |
| Studio root cockpit directory | apps/oshun/web/src/app/studio/page.tsx, StudioInformationArchitectureWorkspace.tsx |
prototype | Acts as the operator entry directory and quick-link cockpit, but still reads as a workbench launcher more than a finished operator home. |
| Design system governance cluster | /studio/design-language, /studio/color-system, /studio/typography, /studio/spacing-layout, /studio/component-primitives, /studio/complex-interactions |
prototype | Major operator-facing design governance surfaces exist as full workspaces. |
| Navigation, discovery, and context-governance cluster | /studio/navigation-commands, /studio/search-discovery, /studio/cross-domain-entity-model, /studio/workspace-context-switching, /studio/multi-project-operations |
prototype | Core operator IA and cross-domain workflow surfaces exist and are substantial. |
| Identity, access, and policy cluster | /studio/authentication-architecture, /studio/session-device-management, /studio/rbac-permission-policy, /studio/enterprise-tenant-isolation, /studio/accessibility-governance, /studio/internationalization-localization, /studio/security-hardening-program |
prototype | Privileged governance surfaces exist, but they are still clearly workspace-style implementations. |
| Review, audit, notification, and retention cluster | /studio/review-approval-workflows, /studio/audit-compliance-surfaces, /studio/notification-center, /studio/activity-change-feeds, /studio/commenting-annotation-system, /studio/data-retention-lifecycle-controls |
prototype | Cross-domain review and governance paths already exist in Studio and are central to the eventual admin product. |
| Reliability, incident, and launch-readiness cluster | /studio/background-jobs-progress-ux, /studio/resilience-error-ux, /studio/observability-operational-dashboards, /studio/backup-disaster-recovery-ux, /studio/launch-readiness-governance, /studio/performance-budgets, /studio/metrics-analytics-instrumentation, /studio/quality-reliability, /studio/adoption-ops, /studio/project-obsidian |
prototype | Reliability and program-control surfaces are already represented as operator workspaces. |
| Integration and composition cluster | /studio/api-gateway-bff-composition, /studio/sdk-documentation-integration, /studio/webhooks-external-automation, /studio/file-media-ingestion, /studio/real-time-collaboration-substrate |
prototype | Platform-facing admin workspaces exist for integration, automation, ingestion, and collaboration control. |
6.2 Subsystem Route Families Already Living Under Studio#
| Surface family | Entrypoints | State | Current posture |
|---|---|---|---|
| Aja operator family | apps/oshun/web/src/app/studio/aja/* (98 routes) |
prototype | Large route family for motion, capture, QA, privacy, search, workers, and SDK workflows. |
| Bellona operator family | apps/oshun/web/src/app/studio/bellona/* (82 routes) |
prototype | Large route family for build, interchange, engine-bridge, XR, render, and packaging workflows. |
| Hathor operator family | apps/oshun/web/src/app/studio/hathor/* (74 routes) |
prototype | Large route family for narrative, world, culture, chronology, modeling, and simulation workflows. |
| Isis operator family | apps/oshun/web/src/app/studio/isis/* (86 routes) |
prototype | Large route family for model, generation, routing, quality, provider, compliance, and budget workflows. |
| Yemaya operator family | apps/oshun/web/src/app/studio/yemaya/* (78 routes) |
prototype | Large route family for collaboration, pipelines, marketplace, scheduling, SDKs, and studio-management workflows. |
7. Admin Mobile Inventory#
| Surface | Entrypoints | State | Current posture |
|---|---|---|---|
| Dedicated admin mobile app shell | no apps/oshun/admin-mobile or equivalent route set |
missing | The PRD requires admin mobile as a first-class urgent-actions companion, but no dedicated admin mobile product exists yet. |
| Queue triage and urgent approvals | no dedicated mobile queue/approval routes | missing | No dedicated admin-mobile review queue, approval, or escalation surface exists in the current OSHUN mobile app. |
| Incident and on-call companion | no dedicated mobile incident or SRE companion routes | missing | No dedicated incident, SLA, escalation, or executive-awareness mobile surface exists yet. |
| Operator-adjacent field tooling | apps/oshun/mobile/app/mocap.tsx |
implemented | Specialized mobile production tooling exists, but it does not satisfy the admin-mobile requirement from the PRD. |
8. Inventory Summary#
The current repo already contains substantial experience surface breadth:
- customer web and PWA: implemented major shell, discovery, continuity, onboarding, public web, and degraded-state surfaces
- customer mobile: implemented major shell tabs, domain detail routes, profile, offline posture, and a specialized capture workflow
- admin web: extensive Studio route coverage with one top-level cockpit entry,
42top-level operator routes, and418subsystem family routes across Aja, Bellona, Hathor, Isis, and Yemaya - admin mobile: still materially absent as a first-class product despite being explicitly required by the PRD and program charter
This inventory is the baseline for redesign ranking, sequencing, and experience-quality audit work in the next UX backlog items.