Eve library

OSHUN Post-MVP Scope

Spec

Revision 1

On this page

Status: Draft v1.0 Owner: OSHUN Product + OSHUN Engineering Last Updated: March 22, 2026 Related: docs/releases/v1/specs/product-brief.md, docs/releases/v1/scope/mvp-scope.md, OSHUN_APP_TODOS.md, docs/releases/v1/specs/program-charter.md

1. Purpose#

This document defines the prioritized backlog after OSHUN MVP exit criteria are met. It captures what gets built next, in what order, and under what quality constraints.

Post-MVP scope is structured to:

  • Increase retention and cross-domain depth
  • Improve personalization and quality of recommendations
  • Expand domain capability depth without breaking shell simplicity
  • Scale reliability, observability, and operational maturity

2. Post-MVP Planning Assumptions#

  • MVP shell (mobile/web/PWA) is live and stable.
  • Tara, Arete, Veritas, Nyx, and Nisaba are integrated at the launch depth defined by the active V1 release model.
  • Shared auth, navigation, search, save, and notifications are in production.
  • Post-MVP work remains shell-first and adapter-based unless a rewrite has clear ROI and timeline justification.

3. Prioritization Framework#

Work is prioritized by the following weighted criteria:

  1. Retention impact (D7/D30 uplift potential)
  2. Cross-domain usage expansion (users engaging with >= 2 domains)
  3. Effort-to-value ratio
  4. Technical risk and dependency complexity
  5. Operational readiness (testability, observability, support burden)

4. Release Waves#

4.1 Wave 1 (0-3 Months After MVP)#

Primary objective: strengthen core loops and reduce friction.

Cross-Platform Product Enhancements#

  • Recommendation transparency controls ("why this", hide/less/more)
  • Smarter continue-state and session resumption logic
  • Richer universal search (query suggestions, domain facets, recents)
  • Advanced offline queue handling for write actions
  • Notification quality tuning (quiet hours, digest personalization)

UX and Ergonomics#

  • Refined one-handed mobile navigation patterns
  • Advanced motion polish and haptic grammar consistency
  • Faster perceived loading via skeleton and predictive prefetch tuning
  • High-contrast and large-text mode refinement

Reliability and Quality#

  • Expanded e2e test matrix across device classes
  • Deep-link regression suite (mobile + web)
  • Enhanced fallback states for partial domain outage scenarios
  • Production SLOs with alerting runbooks per critical funnel

4.2 Wave 2 (3-6 Months After MVP)#

Primary objective: increase domain depth and personalization quality.

Tara Depth Expansion#

  • Expanded breathing and timer customization controls
  • Enhanced streaks, milestones, and motivation loops
  • Offline downloads management improvements
  • More advanced recommendation personalization for meditation journeys

Veritas Depth Expansion#

  • Deeper claim-to-evidence exploration UX
  • Enhanced bias/comparison views for multi-source perspectives
  • Personalized topic intelligence and digest quality improvements
  • Higher-density article reading controls (summaries, source drill-down)

Nyx Depth Expansion#

  • Native Nyx module baseline if MVP shipped in embed mode
  • Observation planning and saved object workflows
  • Event reminder orchestration and calendar integrations
  • Improved offline star-map and night mode usability

Arete Depth Expansion#

  • Full daily planning and review flows (goals + habits + time)
  • Deeper journaling workflows and structured reflection templates
  • Expanded AI coaching insights and recommendation cadence controls
  • Balance/wellness trend visualizations and progress narratives

4.3 Wave 3 (6-12 Months After MVP)#

Primary objective: strategic differentiation and ecosystem flywheel.

Cross-Domain Intelligence Layer#

  • Unified routine engine combining Tara + Arete + Nyx context
  • Context-aware cross-domain recommendations by time, intent, and behavior
  • Adaptive home layout personalization based on proven usage patterns
  • Cross-domain achievement and progression system

Community and Accountability (Phased)#

  • Optional accountability circles and trusted sharing
  • Goal/habit check-in partnerships for Arete surfaces
  • Shared domain challenges with privacy-first controls

Content and Growth Expansion#

  • Broader localization and translated content depth
  • Editorial/curated cross-domain journeys (e.g., daily resilience path)
  • Stronger re-engagement programs with lifecycle orchestration

5. Post-MVP Backlog by Domain#

5.1 Tara Backlog#

  • Deeper timer presets and custom bell workflows
  • Enhanced ambient mixer and soundscape controls
  • Teacher-centric discovery and learning path depth
  • Advanced analytics for practice consistency and outcomes
  • Expanded accessibility presets for meditation sessions

5.2 Veritas Backlog#

  • Topic watchlists with richer follow controls
  • Evidence map visualizations for claims
  • Multi-language reading/audio parity improvements
  • Personalized trust profiles and source preference controls
  • Advanced multimedia convergence (audio/video/news sync)

5.3 Nyx Backlog#

  • Observation planner with weather and visibility integration
  • Satellite tracking and event timeline tools
  • AR/VR module progression where hardware permits
  • Educational mode packs for guided learning sequences
  • Astrophotography support workflows (capture/log/share)

5.4 Arete Backlog#

  • Seven Habits guided programs with staged progression
  • Time mastery workflows (time blocks, deep work, weekly review)
  • Gamification surfaces (levels, badges, accountability contracts)
  • Advanced affirmations and routine anchoring
  • Longitudinal coaching insights and milestone retrospectives

6. Cross-Cutting Platform Backlog#

6.1 Design System#

  • Expanded component coverage for high-density and editorial layouts
  • Advanced theming variants and dynamic personalization tokens
  • Motion and haptic test harnesses for regression detection

6.2 Data and Personalization#

  • Improved recommendation ranking models with guardrails
  • User controls for feed tuning and explanation depth
  • Better conflict resolution for sync and offline writes

6.3 Security and Compliance#

  • Hardened fraud and abuse detection for high-risk actions
  • Expanded consent controls and transparency surfaces
  • Policy automation for evolving platform requirements

6.4 Developer Platform#

  • Domain adapter SDK templates and scaffolds
  • Contract testing framework expansion for adapters
  • Better local simulation tooling for cross-domain integration

7. Defer-Until-Later Backlog (Not Scheduled)#

The following items are explicitly deferred until product-market signals justify investment:

  • Full desktop-native OSHUN client
  • Broad social feed and public profile ecosystem
  • Complex marketplace/partner ecosystems inside shell
  • Advanced wearable-first experiences beyond targeted pilots

8. Success Metrics for Post-MVP Waves#

8.1 Wave 1 Targets#

  • Improve D7 retention by >= 10% from MVP baseline
  • Improve cross-domain WAU (>=2 domains) by >= 15%
  • Reduce critical funnel error rate by >= 30%

8.2 Wave 2 Targets#

  • Improve D30 retention by >= 12% from Wave 1 baseline
  • Increase average weekly sessions per active user by >= 20%
  • Increase save-to-return conversion by >= 15%

8.3 Wave 3 Targets#

  • Increase users engaging >= 3 domains weekly by >= 25%
  • Increase routine completion rate by >= 20%
  • Maintain crash-free sessions >= 99.7%

9. Dependencies and Sequencing Constraints#

  • Nyx native depth depends on integration mode chosen during MVP.
  • Arete advanced surfaces depend on stabilization of data contracts from @arete/core and related modules.
  • Personalization quality upgrades depend on analytics data completeness and data quality pipelines.
  • Community/accountability work depends on privacy policy and safety controls.

10. Post-MVP Definition of Ready#

A post-MVP item is ready for implementation when:

  • User value hypothesis is explicit and measurable.
  • API/domain dependencies are identified and validated.
  • UX requirements are documented for mobile + web/PWA parity.
  • Telemetry plan and experiment plan are defined.
  • Test strategy is scoped (unit/integration/e2e + failure modes).

11. Post-MVP Definition of Done#

A post-MVP item is complete when:

  • Implementation is merged with passing quality gates.
  • Accessibility and performance checks pass against defined budgets.
  • Observability and alerting are in place for new critical paths.
  • Documentation and runbooks are updated.
  • Impact metrics are tracked and reviewed after release.

12. Governance and Review Cadence#

  • Weekly: backlog triage and scope health review
  • Bi-weekly: roadmap adjustments based on telemetry and support data
  • Monthly: cross-domain product review with engineering and design leads
  • Quarterly: re-baseline the post-MVP roadmap against outcomes