# Oshun V1 IA and Experience Quality

## Visual Thesis

Customer surfaces are quiet practice and reading workspaces with Tara as the
first signal, visible Sophia evidence whenever claims matter, and restrained
domain accents. Admin surfaces are dense operational workspaces with compact
queue states, hard audit trails, and scan-first hierarchy.

## Information Architecture

Customer shell: Home, Explore, Activity, Library, Assistant, Profile.

Admin shell: Queues, Review, Policy, Incidents, Privacy, Models, Personas,
Support.

Journey models:

- Morning: Tara continuation to Arete check-in.
- Midday: Veritas story to Sophia source inspection to notebook save.
- Evening: Nyx sky event to Nisaba passage reflection.
- Study: Metis lesson to tutor session to mastery update.
- Assistant-led: persona switch to grounded answer to memory control.

## Layout and Component Rules

- Tara appears first on home and continuity surfaces.
- Evidence UI includes confidence band, source count, citation trail, and
  provenance link.
- Components use stable dimensions, visible focus, reduced-motion parity, and
  high-contrast tokens.
- Cards are reserved for discrete repeated items and framed tools.
- Admin tables favor compact filters, fixed action rails, SLA timers, and
  explicit audit state.

## Eve Phase 8 Design Governance

The adopted interaction brief for contextual invocation, mobile transport,
steering, generated intents, voice, accessibility, and cross-client journeys is
[`EVE_SOTA_INTERACTION_DESIGN_BRIEF_2026-09.md`](../audits/EVE_SOTA_INTERACTION_DESIGN_BRIEF_2026-09.md).
It binds future Phase 8 UI work to the shipped admin/mobile surface inventory:
the active workspace stays primary, Eve stays in the existing drawer or sheet,
copy names actual state and fallback, chrome remains minimal, and motion is
allowed only when it communicates state or affordance with reduced-motion
parity. A generic card-grid redesign is outside the admitted direction.

## QA Checklist

Every shell, domain, admin, mobile, desktop, laptop, tablet, and narrow-mobile
signoff must capture:

- Keyboard-only path through primary actions.
- Reduced-motion path.
- Long-string and RTL viewport fit.
- Evidence and AI disclosure visibility.
- Offline, partial-outage, and retry state where applicable.
- Playwright screenshot or equivalent automated visual evidence.
