Oshun Platform · Architecture

Oshun V1 — Architecture (Page Index)

A focused page within the Oshun Platform Architecture documentation. The full map and every sibling page live in the Architecture hub.

7sections3 minread1diagram

On this page

This directory holds the Oshun V1 architecture documentation, decomposed from the single ../ARCHITECTURE.md hub into focused, in-depth pages. The hub remains the canonical entry point and preserves every heading anchor (so existing arch§"…" cross-references keep resolving); each page below expands one section with far richer, code-grounded detail.

Companion documents: the product feature map lives in ../features/, the backlog in ../TODOS.md, the dependency registry in ../DEPENDENCIES.md, and the 2026-06-24 review/audit ledger in ../AUDIT_2026-06-24.md.

Cross-reference convention. A bare §N / §N.M points at a section of the backlog ../TODOS.md; deps§N points at ../DEPENDENCIES.md; page-to-page links are relative (./<slug>.md, or ../features/<slug>.md for the companion).

Architecture landscape#

FlowchartFlowchart: 9 steps and 11 connections.Member creator operatorand channel surfacesOshun BFF and trustededgesTara Arete Nyx NisabaVeritas MetisSophia Iris Psyche LilithIsis AjeStudio and governedworkbenchesContracts adapters identitytenancy events and auditDomain stores blobsqueues search and graphprojectionsModel media paymentmessaging and engineprovidersObservability lifecyclebackup restore and release
Flowchart: Flowchart. Flowchart: 9 steps and 11 connections.

Drawn from its Mermaid source.

As text
Parts:
- Member creator operator and channel surfaces
- Oshun BFF and trusted edges
- Tara Arete Nyx Nisaba Veritas Metis
- Sophia Iris Psyche Lilith Isis Aje
- Studio and governed workbenches
- Contracts adapters identity tenancy events and audit
- Domain stores blobs queues search and graph projections (data)
- Model media payment messaging and engine providers
- Observability lifecycle backup restore and release

Connections:
- Member creator operator and channel surfaces to Oshun BFF and trusted edges
- Oshun BFF and trusted edges to Tara Arete Nyx Nisaba Veritas Metis
- Oshun BFF and trusted edges to Sophia Iris Psyche Lilith Isis Aje
- Oshun BFF and trusted edges to Studio and governed workbenches
- Tara Arete Nyx Nisaba Veritas Metis to Contracts adapters identity tenancy events and audit
- Sophia Iris Psyche Lilith Isis Aje to Contracts adapters identity tenancy events and audit
- Studio and governed workbenches to Contracts adapters identity tenancy events and audit
- Contracts adapters identity tenancy events and audit to Domain stores blobs queues search and graph projections
- Contracts adapters identity tenancy events and audit to Model media payment messaging and engine providers
- Domain stores blobs queues search and graph projections to Observability lifecycle backup restore and release
- Model media payment messaging and engine providers to Observability lifecycle backup restore and release
Show source
flowchart TB
  Surfaces[Member creator operator and channel surfaces] --> BFF[Oshun BFF and trusted edges]
  BFF --> Domains[Tara Arete Nyx Nisaba Veritas Metis]
  BFF --> Substrates[Sophia Iris Psyche Lilith Isis Aje]
  BFF --> Workbenches[Studio and governed workbenches]
  Domains --> Foundations[Contracts adapters identity tenancy events and audit]
  Substrates --> Foundations
  Workbenches --> Foundations
  Foundations --> Data[(Domain stores blobs queues search and graph projections)]
  Foundations --> External[Model media payment messaging and engine providers]
  Data --> Operations[Observability lifecycle backup restore and release]
  External --> Operations

The pages below zoom into each box and boundary. A line represents a governed contract or effect path, not permission to reach around domain ownership or a claim that every provider and later-release surface is deployed.

Orientation#

  • V1 Product Promise — what V1 commits to shipping across customer, admin, assistant, and platform surfaces.
  • Subsystem Glossary — every domain and substrate name mapped to the real lib/app that owns it.
  • High-Level Architecture — the runtime topology: surfaces → BFF → domain adapters → substrates → data stores.
  • Product Surfaces — the customer, operator, tenant, and public apps and the shared consumer shell.

Customer Domains#

  • Customer-Facing Domains — Tara, Arete, Veritas, Nyx, Nisaba, and Metis at the contract/data/event level, with their real availability tiers (active / beta / planned).

Platform Substrates#

Foundations, Data, and Communication#

  • Foundations — contracts, adapters, persistence, OpenAPI/codegen, idempotency, multi-tenant routing, queues, event-bus, identity/audit.
  • Communication Patterns — synchronous BFF request lifecycle, asynchronous events, and a worked cross-domain cascade.
  • Data Architecture and Tenancy — per-domain databases, shared cluster features, residency, the tenant/consent/memory-scope model.
  • Security, Privacy, and Compliance — access control, operational hardening, and the compliance posture.

Experiences and Systems#

Governance, Operations, and Launch#