Eve library

OSHUN V1 Surface Redesign Ranking

Spec

Revision 1

On this page

Status: Accepted v1.0
Owner: OSHUN Design + Product + Engineering
Last Updated: March 26, 2026
Implements: V1-UX-048
Related:

  • docs/releases/v1/reports/current-state-redesign-inventory.md
  • docs/releases/v1/design/customer-visual-thesis.md
  • docs/releases/v1/design/admin-visual-thesis.md
  • docs/releases/v1/specs/web-app-admin-v1-prd.md
  • docs/releases/v1/specs/todos.md

1. Purpose#

This document ranks each major current OSHUN surface as keep, refine, redesign, or replace, and assigns a launch priority.

It exists to turn the surface inventory into an execution order.

2. Ranking Rubric#

2.1 Disposition#

  • keep: the current surface is structurally sound and should remain largely intact, with only routine polish outside this task
  • refine: the current surface is directionally correct but needs meaningful improvements in hierarchy, ergonomics, or cohesion
  • redesign: the current surface exists, but the current interaction or visual model is not good enough for V1
  • replace: the current state is either absent, the wrong product shape, or so mismatched to the V1 target that a net-new surface should replace it

2.2 Launch Priority#

  • P0: launch-blocking and must be resolved before GA
  • P1: should land during V1 execution before broad rollout confidence
  • P2: important, but can follow after the launch-critical layer is stable
  • P3: later-depth or specialist follow-on work

3. Customer Web and PWA Ranking#

Surface Disposition Priority Rationale
Shared shell chrome and persistent overlays refine P0 The shell frame already exists and carries the cross-domain product, but it needs stronger thesis alignment and calmer hierarchy.
Home dashboard redesign P0 Home is launch-critical and currently too dashboard-heavy for the Tara-led customer posture.
Explore and discovery redesign P0 Discovery breadth exists, but the current surface reads broad and busy rather than intentionally navigable.
Dedicated search results refine P1 Search has the right product role and route shape, but needs stronger scan-first polish.
Activity timeline and inbox refine P1 The activity surface is structurally useful, but it should feel lighter and more cohesive with the rest of the shell.
Library and continuity refine P1 The preserve/continuity model is good, but the visual experience still needs stronger premium focus.
Profile, settings, and operator access handoff refine P1 The handoff model is correct, but the surface still needs better hierarchy and clearer governance posture.
Onboarding redesign P0 Beta-critical and first-impression critical; current standalone wizard shape exists, but the full V1 experience bar is higher.
Domain route experience redesign P0 This route is a major cross-domain cohesion surface and needs a clearer, less generic shared model.
Assistant, continuity, and disclosure surfaces refine P0 These are core trust surfaces that already exist, but the bar for calm, disclosed, premium behavior is higher than the current baseline.
Public welcome landing redesign P0 Public web is launch-blocking and the current welcome surface should be treated as a full redesign target, not light polish.
Public domain marketing pages redesign P1 Domain marketing exists but should be pulled into a more unified public-web experience system.
Public download and install page refine P1 The route shape is correct, but it needs stronger conversion, hierarchy, and store-readiness polish.
Global loading, error, degraded, and not-found states refine P0 Recovery surfaces exist and are critical, but they need calm, premium, and low-noise treatment to match the V1 experience standard.

4. Customer Mobile Ranking#

Surface Disposition Priority Rationale
Mobile shell, tab layout, and persistent helpers refine P0 The shell foundation exists and should be improved, not replaced.
Home tab redesign P0 Like web home, the current mobile home is too dense for the target V1 emotional posture.
Explore tab redesign P1 Discovery breadth exists, but the current mobile composition needs a clearer task flow and density reset.
Activity tab / notification inbox refine P1 The model is directionally right and can be improved without full replacement.
Library tab refine P1 The preserve metaphor is strong, but the visual and ergonomic quality still need work.
Profile tab refine P1 Strong scope already exists, but the information architecture and calmness need refinement.
Domain detail route redesign P0 This route is too important to leave as a large generic shared surface without stronger domain-specific choreography.
Notification and alert settings components refine P2 Supporting infrastructure exists and mainly needs productization and polish.
Offline and degraded-state surfaces keep P1 The foundation is already meaningful and should be preserved while adjacent surfaces are redesigned.
Specialized capture workflow keep P3 It is a specialized production workflow, not a primary V1 customer redesign target.
Dedicated mobile onboarding route replace P0 A beta-critical mobile onboarding product surface is missing and needs to replace the current absence.

5. Admin Web and Studio Ranking#

Surface Disposition Priority Rationale
Explicit admin shell boundary and operator chrome refine P0 The shell boundary is correct and valuable, but the cockpit chrome still needs a more finished operator-grade system.
Studio root cockpit directory redesign P0 The route exists, but it behaves like a launcher rather than a finished operator home.
Design system governance cluster refine P2 Useful specialist workspaces already exist; they need coherence and polish more than replacement.
Navigation, discovery, and context-governance cluster refine P2 Structurally important, but not the first operator-cockpit redesign wave.
Identity, access, and policy cluster redesign P0 These are high-trust operator surfaces and need a clearer finished operator model before launch confidence.
Review, audit, notification, and retention cluster redesign P0 This cluster is closest to the canonical admin cockpit and must be raised to first-class product quality.
Reliability, incident, and launch-readiness cluster redesign P0 Incident, observability, and launch-governance surfaces are operator-critical and currently read as workspaces more than finished cockpits.
Integration and composition cluster refine P1 These are important operator surfaces, but they can follow the first cockpit wave.
Aja operator family refine P3 Large specialist family exists; not the first V1 admin-facing redesign target.
Bellona operator family refine P3 Large specialist family exists; important, but later than the core admin cockpit.
Hathor operator family refine P3 Large specialist family exists; later-depth relative to launch-critical shell/admin surfaces.
Isis operator family refine P2 More launch-relevant than the other subsystem families because of generation/control-plane responsibilities, but still secondary to the main admin shell.
Yemaya operator family refine P3 Important specialist family, but not the first launch-critical admin redesign target.

6. Admin Mobile Ranking#

Surface Disposition Priority Rationale
Dedicated admin mobile app shell replace P0 The product is missing entirely even though the PRD treats it as launch-critical.
Queue triage and urgent approvals replace P0 This is the defining admin-mobile job and no dedicated surface exists today.
Incident and on-call companion replace P0 Admin mobile is explicitly supposed to support incidents and escalations; the current state does not.
Operator-adjacent field tooling keep P3 The capture workflow should remain as specialized tooling, but it is not the admin-mobile answer.

7. Summary#

7.1 Keep#

  • mobile offline/degraded-state surfaces
  • specialized mobile capture workflow
  • operator-adjacent field tooling

7.2 Refine#

  • shared shells and persistent navigation on web and mobile
  • search, activity, library, profile, and many specialist Studio families
  • specialist governance and integration clusters that already have credible structural foundations

7.3 Redesign#

  • customer home, explore, onboarding, and domain-route experiences
  • public welcome surface
  • Studio root cockpit and core operator clusters for review, audit, identity, incident, and launch governance

7.4 Replace#

  • dedicated mobile onboarding absence
  • dedicated admin mobile shell
  • admin-mobile queue, approval, and incident surfaces that do not yet exist

This ranking is the baseline for the next task: before/after experience scorecards for the highest-impact surfaces.