Eve library

Oshun V1 Ownership Matrix

Guide

Revision 1

On this page

Status: Active

Authority: This quick-reference satisfies the V1 domain-registry publishing requirement and points to the deeper governing documents:

  • docs/releases/v1/reports/subsystem-ownership-matrix.md
  • docs/releases/v1/specs/when-to-call-which-subsystem-guide.md
  • docs/releases/v1/specs/program-charter.md
  • docs/releases/v1/specs/web-app-admin-v1-prd.md

If another document conflicts with this page, update this page and the deeper governing documents in the same change. Do not resolve ownership conflicts in application code.

Boundary Rules#

  • The shell composes product surfaces, routes, adapters, continuity, and shared presentation. It does not own domain business rules.
  • Domain services own domain-specific records, workflows, policy hooks, and domain correctness.
  • Core substrates own durable cross-domain capabilities. Do not collapse Iris, Psyche, Lilith, Sophia, or Isis into one assistant subsystem.
  • Shared platform services own infrastructure capabilities such as identity, entitlements, audit, privacy, notification infrastructure, search infrastructure, observability, and experimentation.
  • Cross-domain flows must call explicit adapters, BFF routes, event contracts, or shared-service APIs. No surface should read another owner's persistence tables directly.

Feature Surface Ownership#

Feature Surface Owning Subsystem Call When Common Collaborators Do Not Use As
Home, domain switching, routing, shared navigation, activity, library, notification center, profile/settings, changelog, help, feedback, global command surface OSHUN Shell The work is about product composition, cross-domain presentation, route state, shared UX, or admin/operator shell behavior. Domain adapters, BFF, Shared Platform Services, Iris for continuity Domain business-logic owner, durable memory store, grounding source of record
Auth, session refresh, account recovery, entitlements, billing entry, feature flags, experiments, audit plumbing, privacy plumbing, search infrastructure, notification infrastructure, observability Shared Platform Services The work is infrastructure used by more than one domain or shell surface. OSHUN Shell, BFF, domain services Customer-facing peer domain, assistant substrate, shortcut around domain adapters
Tara rituals, meditation sessions, breathing, sleep transitions, teacher lineage, contemplative completion, ritual recovery Tara The user-facing value is centering, practice, ritual continuation, presence, or contemplative transition. Lilith for contemplative tone and safety, Iris for memory continuity, Psyche for live voice/avatar runtime Shell router, generic grounding service, notification owner
Arete goals, habits, routines, check-ins, weekly review, streaks, recovery prompts, coaching summaries, friction signals Arete The user-facing value is habit formation, reflection, disciplined follow-through, recovery, or coaching synthesis. Iris for consented accountability memory, Tara for recovery rituals, Shared Platform Services for reminders Durable memory owner, generic notification system, shell orchestrator
Veritas stories, claims, source inspection, evidence sidebars, counterclaims, corrections, retractions, topic hubs Veritas The user-facing value is claim briefing, confidence display, source quality, correction, or public evidence inspection. Sophia for grounding, citations, evidence packs, contradiction probes Sophia replacement, memory owner, shell peer
Nyx sky events, observation windows, sky map, calendar sync for events, visibility guidance, astronomy education Nyx The user-facing value is celestial event discovery, observation planning, sky context, or astronomy learning. Shared Platform Services for calendar/notification infrastructure, Sophia when source attribution is needed Research substrate, shell orchestrator, assistant embodiment layer
Nisaba passages, manuscripts, editions, translation comparison, lexicon, morphology, annotations, notebooks, study plans, citations, scholar profiles Nisaba The user-facing value is primary-text study, passage comparison, annotation, scholarship, citation, or notebook work. Sophia for grounding and citations, Iris for reading continuity, Metis for educational handoffs Generic research substrate, grounding source of record, shell peer
Metis source ingestion, grounding packs for learning, course builds, lesson assets, publication packages, tutor sessions, assessments, integrity verdicts, LMS integration Metis The user-facing value is course, tutor, assessment, mastery, learning-source ingestion, or cross-domain educational composition. Sophia for evidence, Iris for tutor memory, Lilith for policy, Isis for generation governance, Psyche for live tutoring runtime Source-of-record owner for origin-domain objects, memory owner, model control plane
Persistent assistant identity, memory scopes, conversation history, memory consent, memory review/export/delete Iris A flow needs durable assistant memory, consent-aware recall, profile/session/notebook/operator/tenant memory boundaries, or memory governance. OSHUN Shell, domain services, Psyche for live runtime Real-time runtime, grounding store, generation control plane
Live text/voice/avatar runtime, turn-taking, conferencing, interruption handling, embodiment state, low-latency session orchestration Psyche A flow needs live voice, avatar, multimodal runtime state, or interruption-aware orchestration. Iris for durable memory, Lilith for persona policy, OSHUN Shell for surfaced UX Durable memory store, grounding source of record
Contemplative teacher logic, tone rubric, persona safety, crisis policy hooks, voice/persona quality rules Lilith A flow needs contemplative tone, spiritual-domain persona policy, teacher behavior, safety rubric, or crisis handoff policy. Tara, Iris, Psyche, Trust and Safety Shell router, grounding source, memory store
Grounding, retrieval, citations, evidence packs, citation trails, knowledge graph, research evaluation, source-aware synthesis Sophia A flow needs evidence, citations, retrieval, contradiction checks, source lineage, or grounded-answer evaluation. Veritas, Nisaba, Metis, OSHUN Shell Customer-facing peer domain, durable memory owner, generation control plane
Model registry, workflow registry, generation policy, provider selection, provenance bundles, watermark/release gates, media workflow orchestration Isis A flow needs model/workflow selection, generation execution governance, provenance, rights/safety review, staging, promotion, rollback, or release gates. Shell/domain surfaces, Lilith policy, Sophia when grounding is needed Direct provider bypass, shell UX owner, memory or grounding owner
Embodied instruction, pose/motion interpretation, instructional feedback hooks for Metis and avatar-led flows Aja A flow needs embodied instruction, motion/pose feedback, avatar physical guidance, or Metis embodied-learning hooks. Metis, Psyche, Lilith Generic assistant runtime, source-of-record learning owner

When To Call Which Subsystem#

  1. Call OSHUN Shell first for route composition, shared UX, continuity UI, admin/operator workspaces, and cross-domain presentation.
  2. Call Shared Platform Services first for identity, entitlements, audit, privacy, notification infrastructure, search infrastructure, observability, experimentation, billing infrastructure, and tenant infrastructure.
  3. Call Tara, Arete, Veritas, Nyx, Nisaba, or Metis first when the work is primarily a domain-specific customer or learner experience.
  4. Add Iris when the flow needs durable memory, consent-aware recall, conversation continuity, or memory export/delete/review controls.
  5. Add Psyche when the flow needs live voice, avatar, real-time turn-taking, conferencing, or interruption-aware orchestration.
  6. Add Lilith when the flow needs contemplative tone, persona policy, safety review, or crisis handoff rules.
  7. Add Sophia when the flow needs grounded retrieval, citations, evidence packs, contradiction probes, source lineage, or research evaluation.
  8. Add Isis when the flow needs model/workflow governance, generation policy, provider orchestration, provenance, watermarking, staging, promotion, or rollback.
  9. Add Aja when the flow needs embodied instruction or motion/pose feedback.

Escalation#

When a feature appears to have multiple owners, split the decision into:

  1. system-of-record owner
  2. calling or composing owner
  3. policy or approval owner

If that split remains ambiguous, update this page, the subsystem ownership matrix, the when-to-call guide, the program charter, and the unified PRD before implementation proceeds.