Oshun Platform · Features

Oshun V1 — Features (Page Index)

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

12sections6 minread1diagram

On this page

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

Release scope (2026-08-05). This index covers the whole V1 line, not a V1.0 shipping list. V1.0 ships the customer web app + PWA with four rooms — Tara, Nyx, Arete, Nisaba — charging through the crypto rail only. V1.1 adds the native mobile apps and the fiat payment rails. V1.2 opens the Veritas and Metis rooms. Pages for deferred work carry a release banner at the top; the scope record is ../BRAND.md.

Companion documents: the runtime/package architecture lives in ../architecture/, the backlog (source of completion truth) 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 ../architecture/<slug>.md for the companion).

Feature landscape#

FlowchartFlowchart: 9 steps and 14 connections.V1 product promiseMember domains andaccountAuthoring curation andworkbenchesLilith experience Eveoperations memory andgroundingGeneration media searchand Living ScenesTelegram and otherchannelsAdmin tenant supportsafety and privacyFoundations design qualitylocalization and launchV1.0 V1.1 V1.2 releasescope
Flowchart: Flowchart. Flowchart: 9 steps and 14 connections.

Drawn from its Mermaid source.

As text
Parts:
- V1 product promise
- Member domains and account
- Authoring curation and workbenches
- Lilith experience Eve operations memory and grounding
- Generation media search and Living Scenes
- Telegram and other channels
- Admin tenant support safety and privacy
- Foundations design quality localization and launch
- V1.0 V1.1 V1.2 release scope

Connections:
- V1 product promise to Member domains and account
- V1 product promise to Authoring curation and workbenches
- V1 product promise to Lilith experience Eve operations memory and grounding
- V1 product promise to Generation media search and Living Scenes
- V1 product promise to Telegram and other channels
- V1 product promise to Admin tenant support safety and privacy
- V1 product promise to Foundations design quality localization and launch
- Member domains and account to V1.0 V1.1 V1.2 release scope
- Authoring curation and workbenches to V1.0 V1.1 V1.2 release scope
- Lilith experience Eve operations memory and grounding to V1.0 V1.1 V1.2 release scope
- Generation media search and Living Scenes to V1.0 V1.1 V1.2 release scope
- Telegram and other channels to V1.0 V1.1 V1.2 release scope
- Admin tenant support safety and privacy to V1.0 V1.1 V1.2 release scope
- Foundations design quality localization and launch to V1.0 V1.1 V1.2 release scope
Show source
flowchart LR
  Promise[V1 product promise] --> Member[Member domains and account]
  Promise --> Creator[Authoring curation and workbenches]
  Promise --> Assistant[Lilith experience Eve operations memory and grounding]
  Promise --> Media[Generation media search and Living Scenes]
  Promise --> Channels[Telegram and other channels]
  Promise --> Operator[Admin tenant support safety and privacy]
  Promise --> Platform[Foundations design quality localization and launch]
  Member --> Release[V1.0 V1.1 V1.2 release scope]
  Creator --> Release
  Assistant --> Release
  Media --> Release
  Channels --> Release
  Operator --> Release
  Platform --> Release

This is a navigation model, not a dependency graph. The architecture index owns runtime composition; the release table and per-page banners decide which parts of this feature landscape are member-visible in each V1 release.

Orientation#

  • V1 Product Promise — the experience V1 commits to across customer, admin, assistant, and platform surfaces.
  • Subsystem Glossary — domains, substrates, surfaces, and cross-domain support defined in one place.
  • Product Surfaces — Customer Web/Mobile, the shared consumer shell, operator surfaces, and public web/distribution.
  • Account, Profile, and Settings — the account hub: identity, preferences, privacy/consent, data rights, devices, memory controls, and safety settings.

Customer Domains#

Authoring, Editorial, and Curation#

Assistant, Memory, Persona, and Embodiment#

Living Scenes#

Agentic AI Studio#

Admin, Tenant, and Operator#

Governance, Safety, Support, and Privacy#

Messaging Channels#

Platform, Quality, and Launch#