Eve library

OSHUN V1 Subsystem Ownership Matrix

Guide

Revision 1

On this page

Status: Active

Date: March 23, 2026

Owners: OSHUN Product, OSHUN Engineering, OSHUN Platform, OSHUN Safety

Related:

  • docs/releases/v1/specs/program-charter.md
  • docs/releases/v1/reports/metis-subsystem-ownership-matrix.md
  • docs/releases/v1/reports/metis-domain-gap-analysis-and-full-integration-report-2026-03-23.md
  • docs/releases/v1/specs/web-app-admin-v1-prd.md
  • docs/releases/v1/specs/when-to-call-which-subsystem-guide.md
  • docs/reference/data-ownership-matrix.md
  • docs/releases/v1/specs/todos.md

1. Purpose and Authority#

This document is the authoritative quick-reference ownership matrix for OSHUN V1.

It normalizes the ownership model defined in:

  • docs/releases/v1/specs/program-charter.md section 3.3
  • docs/releases/v1/specs/program-charter.md section 6.1
  • docs/releases/v1/specs/web-app-admin-v1-prd.md section 16

Use this matrix for planning, implementation, review, escalation, and boundary checks.

If another document or implementation suggests a conflicting owner, this matrix, the charter, and the unified PRD win. docs/reference/data-ownership-matrix.md remains a legacy pre-V1 reference only.

2. Boundary Rules#

  • The shell composes product experiences; it does not absorb domain business logic or core substrate state.
  • Customer-facing domains own their experience responsibilities; they do not replace the shell or the core substrates.
  • Metis may compose material, goals, and context from multiple domains into educational flows, but it does not become the source-of-record owner for those originating domain objects.
  • Iris, Psyche, Lilith, Sophia, and Isis stay separate by default; do not collapse them into a generic assistant blob.
  • Shared platform services remain shared infrastructure and do not become ad hoc peer domains or assistant subsystems.
  • Cross-row interactions must use explicit adapters, contracts, or BFF composition boundaries.

3. Product Surface and Orchestration Ownership#

Owner Owns Depends On Must Not Be Treated As
OSHUN Shell consumer UX, admin UX, routing and shells, domain adapters, shared object composition, entitlement-aware orchestration, continuity and recommendation presentation BFF, shared contracts, domain adapters, platform services domain business-logic owner, durable memory store, grounding system of record, persona-policy engine, generation control plane
Shared Platform Services identity, entitlements, search, offline/cache, observability, audit, privacy, experimentation, notification infrastructure persistence, infra, shared contracts customer-facing peer domain, assistant substrate, bypass path around shell or domain adapters

4. Customer-Facing Domain Experience Ownership#

Important: Sophia is not a peer customer-facing domain. It appears only in the core substrate table below. Metis is a peer customer-facing domain and also the shared educational substrate for course, tutor, assessment, and cross-domain learning journeys. That does not transfer system-of-record ownership away from originating domains or the core substrates.

Domain Owns Depends On Must Not Be Treated As
Tara centering, rituals, transitions, sleep, and presence experiences shell orchestration, domain adapters, shared services shell orchestrator, grounding substrate, generic assistant policy owner
Arete habits, goals, reflection, and daily structure experiences shell orchestration, domain adapters, shared services shell orchestrator, memory substrate, notification or search owner
Veritas grounded claims, briefings, and evidence inspection experiences shell orchestration, domain adapters, Sophia where grounded generic grounding substrate, shell peer, memory or persona-policy owner
Nyx sky awareness, events, and cosmological orientation experiences shell orchestration, domain adapters, shared services shell orchestrator, research substrate, assistant embodiment owner
Nisaba passages, study, compare, annotation, and scholarship experiences shell orchestration, domain adapters, Sophia where grounded generic research substrate, shell peer, grounding system of record
Metis learner journeys, course/tutor/assessment experiences, and cross-domain study handoffs shell orchestration, domain adapters, Sophia where grounded, Iris/Lilith/Isis/Psyche where applicable shell orchestrator, generic grounding substrate, source-of-record owner for origin domains, memory owner, model control plane

5. Core Substrate Ownership#

Subsystem Owns Exposes Through Must Not Be Treated As
Iris assistant identity, persistent conversation history, durable memory, memory scopes, memory privacy boundary, memory consent state, user memory controls canonical memory adapters and contracts real-time avatar/runtime layer, grounding source, generation control plane
Psyche real-time session orchestration, live text/voice/avatar runtime, conferencing and turn-taking, multimodal embodiment, low-latency interaction state embodiment/runtime adapters and session orchestration contracts durable memory store, grounding source of record
Lilith contemplative teacher logic, meditation-tone policy, spiritual-domain persona policy, voice quality and safety policies, contemplative safeguards persona-policy adapters and policy bundles shell router, generic product orchestration layer, grounding or memory source of record
Sophia grounding, retrieval, citations, evidence packs, knowledge graph, notebooks, research evaluation evidence adapters, grounding contracts, citation/evidence packages fifth shell tab, durable memory owner, generation control plane
Isis model registry, workflow registry, generation execution policy, staging and promotion, provenance bundles, release gates, media workflow orchestration generation-control adapters, workflow/model contracts, provenance bundles ad hoc direct-runtime bypass layer, shell UX owner, grounding/memory/policy source of record

6. Ownership Escalation Rule#

If a feature, incident, or roadmap item appears to require more than one row to own the same responsibility, stop and split the problem into:

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

If the responsibility still does not map cleanly, update this matrix, the charter, and the unified PRD together before implementation proceeds.