Eve library

OSHUN Personas and JTBD

Spec

Revision 1

On this page

Status: Draft v1.0 Owner: OSHUN Product + OSHUN Engineering + OSHUN Design Last Updated: February 16, 2026 Related: docs/releases/v1/specs/product-brief.md, docs/releases/v1/scope/mvp-scope.md, docs/releases/v1/specs/post-mvp-scope.md

1. Purpose#

This document defines the user personas and jobs-to-be-done (JTBD) that guide OSHUN UX, feature prioritization, and acceptance criteria for mobile, web, and PWA surfaces.

2. Evidence Inputs#

This persona model is derived from current repository artifacts and existing platform capabilities:

  • Tara feature and app-store docs (docs/domains/tara/features.md, apps/tara/docs/marketing/app-store-listing.md)
  • Veritas feature and user-story docs (docs/domains/veritas/features.md, docs/domains/veritas/user-stories.md)
  • Nyx feature and user-story docs (docs/domains/nyx/features.md, docs/domains/nyx/user-stories.md)
  • Arete feature docs (docs/domains/arete/features.md)

3. Persona Framework#

Personas are grouped by priority for MVP and near-term roadmap.

  • P1: Primary target personas for MVP design and delivery.
  • P2: Secondary personas addressed by post-MVP depth.

4. P1 Personas (MVP-Critical)#

4.1 Persona P1-A: The Daily Balancer#

Profile:

  • Age range: 24-44
  • Context: busy professional or caregiver with limited uninterrupted time
  • Device behavior: mobile-first, checks app multiple short sessions per day

Core intent:

  • Reduce stress quickly and maintain consistency in wellbeing habits.

Primary domains:

  • Tara, Arete

Primary JTBD:

  • Functional: "When my day is chaotic, help me start a grounding session fast."
  • Emotional: "Help me feel in control, not behind."
  • Social: "Help me sustain routines I can confidently tell others about."

Top pains:

  • Friction in choosing what to do next
  • Feature overload and decision fatigue
  • Inconsistent progress feedback

Design implications:

  • Keep one-tap quick actions on Home.
  • Default to short, high-confidence routines.
  • Show progress in simple, motivating summaries.

Success signals:

  • Starts a session within 30 seconds of app open
  • Completes at least 4 weekly quick sessions
  • Uses "continue" and "daily check-in" flows repeatedly

4.2 Persona P1-B: The Truth Seeker#

Profile:

  • Age range: 20-50
  • Context: actively follows current affairs and wants reliable signal
  • Device behavior: mobile during the day, web in deeper reading sessions

Core intent:

  • Understand what is true, what is uncertain, and why.

Primary domains:

  • Veritas (with occasional Arete/Tara for decompression)

Primary JTBD:

  • Functional: "When information is noisy, give me verified, source-grounded summaries quickly."
  • Emotional: "Help me feel informed without feeling manipulated."
  • Social: "Help me share reliable context without spreading misinformation."

Top pains:

  • Unclear confidence levels in news content
  • Too much content with weak prioritization
  • Hard to save and revisit trusted items

Design implications:

  • Always expose confidence and evidence context for Veritas cards.
  • Offer concise summaries before deep dives.
  • Keep save/follow actions obvious and fast.

Success signals:

  • High completion rate on claim/article drill-downs
  • Repeat usage of save/follow topic workflows
  • Increased return rate to saved Veritas items

4.3 Persona P1-C: The Curious Observer#

Profile:

  • Age range: 16-40
  • Context: curious learner and hobby explorer of astronomy
  • Device behavior: evening usage, often outdoors, intermittent connectivity

Core intent:

  • Turn curiosity about the sky into regular discovery moments.

Primary domains:

  • Nyx (with occasional Veritas and Tara)

Primary JTBD:

  • Functional: "When I look up at the sky, help me quickly know what I am seeing and what is happening tonight."
  • Emotional: "Help me feel wonder and competence at the same time."
  • Social: "Help me share interesting findings simply."

Top pains:

  • Complex interfaces that assume expert astronomy knowledge
  • Low-light readability issues and fragile outdoor UX
  • Limited continuity across sessions/devices

Design implications:

  • Prioritize nightly highlights and obvious sky exploration entry points.
  • Keep night-safe contrast and legibility standards strict.
  • Ensure useful offline fallback states.

Success signals:

  • Frequent use of nightly highlights
  • Increased repeat evening sessions
  • Completion of star-map exploration loops

4.4 Persona P1-D: The Intentional Builder#

Profile:

  • Age range: 23-48
  • Context: self-improvement oriented, actively tracks habits/goals/journal
  • Device behavior: morning planning + evening reflection behavior

Core intent:

  • Build long-term personal growth through structured daily action.

Primary domains:

  • Arete (plus Tara for regulation)

Primary JTBD:

  • Functional: "When I set growth goals, help me convert intention into daily actions and visible progress."
  • Emotional: "Help me feel momentum, not guilt."
  • Social: "Help me stay accountable without losing privacy."

Top pains:

  • Fragmented tools for habits, goals, and journaling
  • Weak feedback loops and delayed sense of progress
  • Difficulty restarting after missed days

Design implications:

  • Daily check-in should complete in <= 60 seconds.
  • Reinforce recovery patterns after misses.
  • Show compact streak/progress signals near primary actions.

Success signals:

  • High daily check-in completion rate
  • Stable weekly streak retention
  • Re-engagement after missed days

5. P2 Personas (Post-MVP Priority)#

5.1 Persona P2-E: The Routine Integrator#

Profile:

  • Uses 2-4 domains weekly and wants a connected routine.

JTBD focus:

  • "Help me combine calm, truth, curiosity, and growth into one coherent daily/weekly rhythm."

Post-MVP significance:

  • Primary beneficiary of cross-domain routine engine and recommendation quality.

5.2 Persona P2-F: The Accessibility-First User#

Profile:

  • Uses assistive technologies or high-accessibility settings by default.

JTBD focus:

  • "Help me get full product value without workaround behavior."

Post-MVP significance:

  • Drives expanded accessibility presets, semantic rigor, and test coverage.

6. JTBD Catalog (Cross-Persona)#

6.1 Core Functional Jobs#

  • Start a useful session quickly from one home surface.
  • Resume meaningful progress without searching across domains.
  • Find reliable information with clear evidence signals.
  • Save and return to important items across contexts.
  • Complete daily check-ins and see progress trends.

6.2 Core Emotional Jobs#

  • Feel calm and focused in moments of overload.
  • Feel confident in information quality.
  • Feel inspired by discovery and growth.
  • Feel momentum rather than pressure.

6.3 Core Social Jobs#

  • Share useful, trustworthy content responsibly.
  • Build and maintain routines that are socially sustainable.
  • Participate in accountability with consent and control.

7. Persona-to-Feature Mapping#

Feature Area P1-A Daily Balancer P1-B Truth Seeker P1-C Curious Observer P1-D Intentional Builder
Home quick actions Critical Important Important Critical
Domain trust signals Useful Critical Useful Useful
Night-ready UX Useful Useful Critical Useful
Daily check-in Important Optional Optional Critical
Unified save/library Important Critical Important Important
Activity timeline Important Important Useful Critical
Notification controls Critical Important Important Critical
Offline fallback Important Important Critical Important

8. Journey Snapshots (P1)#

8.1 P1-A Daily Balancer Journey#

  • Trigger: stress spike between meetings
  • Entry: opens OSHUN -> taps Home quick action
  • Value moment: starts Tara or Arete micro-session in <= 30s
  • Completion: sees calming/progress signal and returns to day

8.2 P1-B Truth Seeker Journey#

  • Trigger: sees a contested claim online
  • Entry: opens OSHUN -> Veritas card/search
  • Value moment: confidence + evidence context shown fast
  • Completion: saves/shares trusted summary

8.3 P1-C Curious Observer Journey#

  • Trigger: evening sky event or curiosity
  • Entry: opens OSHUN -> Nyx nightly highlights
  • Value moment: identifies what to observe now
  • Completion: follows exploration path and saves object/event

8.4 P1-D Intentional Builder Journey#

  • Trigger: morning planning or evening reflection
  • Entry: opens OSHUN -> Arete daily check-in
  • Value moment: logs progress with minimal friction
  • Completion: receives clear next step and streak context

9. Persona-Driven Design Constraints#

  • Two taps to domain value from home for all P1 personas.
  • Primary action controls must remain thumb-reachable on mobile.
  • Trust and uncertainty must be visible for information-heavy cards.
  • Recovery pathways (missed day, offline mode, API failure) must be first-class.
  • Accessibility must preserve full completion of core journeys.

10. Persona-Driven KPI Mapping#

  • P1-A: time-to-first-session, quick-action completion rate, weekly streak health
  • P1-B: verification drill-down completion, save/follow conversion, return-to-save
  • P1-C: nightly-highlight engagement, exploration completion, repeat evening use
  • P1-D: daily check-in completion, recovery-after-miss rate, weekly planning retention

11. Validation Plan#

  • Quantitative:
    • Funnel instrumentation for each P1 journey
    • Weekly cohort retention by persona proxy behavior
  • Qualitative:
    • Monthly user interviews by persona segment
    • In-app feedback prompts on journey completion pain points
  • Operational:
    • Track failed journey states and top abandonment points per persona flow

12. Update Cadence#

  • Review persona fit monthly during product/engineering sync.
  • Recalibrate JTBD wording quarterly using telemetry and research.
  • Treat persona updates as versioned product artifacts.