Oshun Platform · Guides & deep dives

V1 Diagram Atlas

Member, creator, and operator surfaces share foundations but not authority.

10sections3 minread

On this page

This atlas collects the small set of mental models needed to navigate V1 before opening subsystem detail. It complements the generated Docs Center diagram gallery, which indexes every authored diagram across the repository. Each model below is deliberately scoped: it explains responsibility or flow, not shipment.

Product and platform landscape#

FlowchartFlowchart: 12 steps and 12 connections.Member surfaces: webPWA mobile TelegramShared consumer shellCreator and StudiosurfacesOshun Studio andworkbenchesAdmin tenant and supportsurfacesOperator control planesOshun BFF and channelboundariesTara Arete Nyx NisabaVeritas MetisSophia Iris Psyche LilithIsis AjeContracts persistenceevents identity auditDomain stores blobsqueues and projectionsModel media paymentmessaging and platformproviders
Flowchart: Flowchart. Flowchart: 12 steps and 12 connections.

Drawn from its Mermaid source.

As text
Parts:
- Member surfaces: web PWA mobile Telegram
- Shared consumer shell
- Creator and Studio surfaces
- Oshun Studio and workbenches
- Admin tenant and support surfaces
- Operator control planes
- Oshun BFF and channel boundaries
- Tara Arete Nyx Nisaba Veritas Metis
- Sophia Iris Psyche Lilith Isis Aje
- Contracts persistence events identity audit
- Domain stores blobs queues and projections (data)
- Model media payment messaging and platform providers

Connections:
- Member surfaces: web PWA mobile Telegram to Shared consumer shell
- Creator and Studio surfaces to Oshun Studio and workbenches
- Admin tenant and support surfaces to Operator control planes
- Shared consumer shell to Oshun BFF and channel boundaries
- Oshun Studio and workbenches to Oshun BFF and channel boundaries
- Operator control planes to Oshun BFF and channel boundaries
- Oshun BFF and channel boundaries to Tara Arete Nyx Nisaba Veritas Metis
- Oshun BFF and channel boundaries to Sophia Iris Psyche Lilith Isis Aje
- Tara Arete Nyx Nisaba Veritas Metis to Contracts persistence events identity audit
- Sophia Iris Psyche Lilith Isis Aje to Contracts persistence events identity audit
- Contracts persistence events identity audit to Domain stores blobs queues and projections
- Contracts persistence events identity audit to Model media payment messaging and platform providers
Show source
flowchart TB
  Member[Member surfaces: web PWA mobile Telegram] --> Shell[Shared consumer shell]
  Creator[Creator and Studio surfaces] --> Studio[Oshun Studio and workbenches]
  Operator[Admin tenant and support surfaces] --> Ops[Operator control planes]
  Shell --> BFF[Oshun BFF and channel boundaries]
  Studio --> BFF
  Ops --> BFF
  BFF --> Domains[Tara Arete Nyx Nisaba Veritas Metis]
  BFF --> Substrates[Sophia Iris Psyche Lilith Isis Aje]
  Domains --> Foundation[Contracts persistence events identity audit]
  Substrates --> Foundation
  Foundation --> Data[(Domain stores blobs queues and projections)]
  Foundation --> Providers[Model media payment messaging and platform providers]

Member, creator, and operator surfaces share foundations but not authority. Every request crosses the BFF/channel policy and a domain or substrate boundary; a shared shell does not authorize a domain effect.

Member request sequence#

sequenceDiagram actor Member participant Surface as Lilith surface participant BFF as Oshun BFF participant Policy as Identity and policy participant Domain as Domain or substrate participant Store as Durable store or provider Member->>Surface: Intent plus current context Surface->>BFF: Authenticated typed request BFF->>Policy: Resolve tenant grants consent release and safety alt refused or withheld Policy-->>BFF: Named reason and safe posture BFF-->>Surface: Denied unavailable or grounded abstention else admitted Policy-->>BFF: Scoped capability BFF->>Domain: Versioned command or query Domain->>Store: Read write or provider effect Store-->>Domain: Durable result receipt or failure Domain-->>BFF: Typed outcome plus evidence BFF-->>Surface: Content disclosure provenance and recovery end Surface-->>Member: Honest visible outcome

The provider/store receipt and typed domain outcome matter. A surface label or planned response is not proof that a write or delivery occurred.

Durable identity and evidence relationships#

Entity-relationship diagramEntity-relationship diagram: 15 entities and 16 relationships.grantsholdsauthenticatescontrolsownscontainsversionssupportscitesproducesemitsrecordspermitssubjectsrecordsattributesTENANTMEMBERSHIPMEMBERSESSIONCONSENTPROJECTRESOURCEREVISIONEVIDENCESOURCEJOBARTIFACTPROVENANCEMEMORY_RECORDAUDIT_EVENT
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 15 entities and 16 relationships.

Drawn from its Mermaid source.

As text
Parts:
- TENANT
- MEMBERSHIP
- MEMBER
- SESSION
- CONSENT
- PROJECT
- RESOURCE
- REVISION
- EVIDENCE
- SOURCE
- JOB
- ARTIFACT
- PROVENANCE
- MEMORY_RECORD
- AUDIT_EVENT

Connections:
- TENANT to MEMBERSHIP (one to zero or many): grants
- MEMBER to MEMBERSHIP (one to zero or many): holds
- MEMBER to SESSION (one to zero or many): authenticates
- MEMBER to CONSENT (one to zero or many): controls
- TENANT to PROJECT (one to zero or many): owns
- PROJECT to RESOURCE (one to zero or many): contains
- RESOURCE to REVISION (one to zero or many): versions
- REVISION to EVIDENCE (one to zero or many): supports
- EVIDENCE to SOURCE (zero or many to zero or many): cites
- REVISION to JOB (one to zero or many): produces
- JOB to ARTIFACT (one to zero or many): emits
- ARTIFACT to PROVENANCE (one to zero or many): records
- CONSENT to MEMORY_RECORD (one to zero or many): permits
- MEMBER to MEMORY_RECORD (one to zero or many): subjects
- RESOURCE to AUDIT_EVENT (one to zero or many): records
- SESSION to AUDIT_EVENT (one to zero or many): attributes
Show source
erDiagram
  TENANT ||--o{ MEMBERSHIP : grants
  MEMBER ||--o{ MEMBERSHIP : holds
  MEMBER ||--o{ SESSION : authenticates
  MEMBER ||--o{ CONSENT : controls
  TENANT ||--o{ PROJECT : owns
  PROJECT ||--o{ RESOURCE : contains
  RESOURCE ||--o{ REVISION : versions
  REVISION ||--o{ EVIDENCE : supports
  EVIDENCE }o--o{ SOURCE : cites
  REVISION ||--o{ JOB : produces
  JOB ||--o{ ARTIFACT : emits
  ARTIFACT ||--o{ PROVENANCE : records
  CONSENT ||--o{ MEMORY_RECORD : permits
  MEMBER ||--o{ MEMORY_RECORD : subjects
  RESOURCE ||--o{ AUDIT_EVENT : records
  SESSION ||--o{ AUDIT_EVENT : attributes

Domains specialize these records and may use different stores. The invariant is that tenant, actor/session, resource/version, consent, evidence, job/artifact, provenance, and audit identities do not collapse into one convenient id.

Governed action lifecycle#

State diagramState diagram: 15 states and 22 transitions.schema and domain preconditions passinvalid unavailable or prohibitedsensitive member or operator side effectread or pre-authorized bounded effectexact scope confirmed and reauthorizedasynchronous worksynchronous effectlease and fence acquireddurable receipt and evidencetransient bounded failureterminal or policy failurerequired evidence provider or rights absentgoverned reversal or correctionnew revision and receiptProposedValidatedRejectedAwaitingConfirmationAuthorizedCancelledQueuedExecutingCompletedRetryableFailedWithheldCompensating
State machine: State diagram. State diagram: 15 states and 22 transitions.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Parts:
- Start (initial)
- Proposed
- Validated
- Rejected
- AwaitingConfirmation
- Authorized
- Cancelled
- Queued
- Executing
- Completed
- Retryable
- Failed
- Withheld
- Compensating
- End (final)

Connections:
- Start to Proposed
- Proposed to Validated: schema and domain preconditions pass
- Proposed to Rejected: invalid unavailable or prohibited
- Validated to AwaitingConfirmation: sensitive member or operator side effect
- Validated to Authorized: read or pre-authorized bounded effect
- AwaitingConfirmation to Authorized: exact scope confirmed and reauthorized
- AwaitingConfirmation to Cancelled
- Authorized to Queued: asynchronous work
- Authorized to Executing: synchronous effect
- Queued to Executing: lease and fence acquired
- Executing to Completed: durable receipt and evidence
- Executing to Retryable: transient bounded failure
- Retryable to Queued
- Executing to Failed: terminal or policy failure
- Executing to Withheld: required evidence provider or rights absent
- Completed to Compensating: governed reversal or correction
- Compensating to Completed: new revision and receipt
- Rejected to End
- Cancelled to End
- Failed to End
- Withheld to End
- Completed to End
Show source
stateDiagram-v2
  [*] --> Proposed
  Proposed --> Validated: schema and domain preconditions pass
  Proposed --> Rejected: invalid unavailable or prohibited
  Validated --> AwaitingConfirmation: sensitive member or operator side effect
  Validated --> Authorized: read or pre-authorized bounded effect
  AwaitingConfirmation --> Authorized: exact scope confirmed and reauthorized
  AwaitingConfirmation --> Cancelled
  Authorized --> Queued: asynchronous work
  Authorized --> Executing: synchronous effect
  Queued --> Executing: lease and fence acquired
  Executing --> Completed: durable receipt and evidence
  Executing --> Retryable: transient bounded failure
  Retryable --> Queued
  Executing --> Failed: terminal or policy failure
  Executing --> Withheld: required evidence provider or rights absent
  Completed --> Compensating: governed reversal or correction
  Compensating --> Completed: new revision and receipt
  Rejected --> [*]
  Cancelled --> [*]
  Failed --> [*]
  Withheld --> [*]
  Completed --> [*]

Confirmation, authorization, domain validity, execution, and verification are separate. Compensation creates new history; it does not erase the original action.

Shared contract composition#

classDiagram class RequestContext { tenantId actorId sessionId correlationId releaseScope grants } class DomainCommand { commandId resourceId expectedVersion idempotencyKey } class PolicyDecision { outcome reason obligations } class JobReceipt { jobId state leaseFence resultRef } class EvidenceEnvelope { sourceRefs provenanceRef disclosure auditRef } RequestContext --> DomainCommand : scopes RequestContext --> PolicyDecision : evaluated by PolicyDecision --> DomainCommand : admits or refuses DomainCommand --> JobReceipt : may enqueue DomainCommand --> EvidenceEnvelope : returns JobReceipt --> EvidenceEnvelope : completes with

Concrete packages use richer domain-specific schemas. This model shows the shared contract roles that should remain visible through every implementation.

Cross-cutting ownership map#

V1 cross-cutting ownershipMind map: 33 ideas.V1 cross-cutting ownershipMember experienceLilith identityShared shellRooms and domainsAccessibilityBuilder operationsEveWorkbenchesConfirmation and leasesIndependent verificationTrustIdentity and tenantLilith policySophia evidenceIris consent and memoryRights provenance auditCreationIsis generationYemaya production andstudyAja motionEuterpe audioBellona interchangeDeliveryWeb and PWATelegram and channelsNotificationsPublishing and exportsOperationsObservability and SLOsCapacity and costBackup and restoreRollout rollback incidents
Mind map: V1 cross-cutting ownership. Mind map: 33 ideas.

This picture is wider than it can be shown here. Move across it, or read it as text.

Drawn from its Mermaid source.

As text
Tree:
- V1 cross-cutting ownership
  - Member experience
    - Lilith identity
    - Shared shell
    - Rooms and domains
    - Accessibility
  - Builder operations
    - Eve
    - Workbenches
    - Confirmation and leases
    - Independent verification
  - Trust
    - Identity and tenant
    - Lilith policy
    - Sophia evidence
    - Iris consent and memory
    - Rights provenance audit
  - Creation
    - Isis generation
    - Yemaya production and study
    - Aja motion
    - Euterpe audio
    - Bellona interchange
  - Delivery
    - Web and PWA
    - Telegram and channels
    - Notifications
    - Publishing and exports
  - Operations
    - Observability and SLOs
    - Capacity and cost
    - Backup and restore
    - Rollout rollback incidents
Show source
mindmap
  root((V1 cross-cutting ownership))
    Member experience
      Lilith identity
      Shared shell
      Rooms and domains
      Accessibility
    Builder operations
      Eve
      Workbenches
      Confirmation and leases
      Independent verification
    Trust
      Identity and tenant
      Lilith policy
      Sophia evidence
      Iris consent and memory
      Rights provenance audit
    Creation
      Isis generation
      Yemaya production and study
      Aja motion
      Euterpe audio
      Bellona interchange
    Delivery
      Web and PWA
      Telegram and channels
      Notifications
      Publishing and exports
    Operations
      Observability and SLOs
      Capacity and cost
      Backup and restore
      Rollout rollback incidents

The map is a reading aid. The V1 documentation guide links each branch to its detailed feature, architecture, handbook, reference, and evidence home.

Release timeline#

timeline title V1 product-line release boundaries V1.0 : Customer web app and PWA : Tara Nyx Arete and Nisaba rooms : Crypto payment rail V1.1 : Native mobile and watch surfaces : Fiat card bank wallet and app-store rails V1.2 : Veritas member room : Metis member room

This timeline describes product scope, not a calendar promise or proof that a release is deployed. Current backlog, deployment, and release-gate evidence remain authoritative.

Multi-actor release journey#

From product decision to supported V1 capabilityUser journey: 10 stages.1Define user promise and releaseDecide. Product, Design. Score 5 of 5.2Approve architecture trust and data boundariesDecide. Architecture, Governance. Score 5 of 5.3Implement contracts storage services and surfaceBuild. Engineering. Score 4 of 5.4Add failure accessibility and observability behaviorBuild. Engineering, SRE. Score 5 of 5.5Run unit contract integration and browser journeysVerify. QA, Engineering. Score 5 of 5.6Validate security privacy performance and recoveryVerify. Governance, SRE. Score 5 of 5.7Deploy compatible changes and canary cohortRelease. SRE. Score 4 of 5.8Inspect provider receipts and operational evidenceRelease. SRE, Product. Score 5 of 5.9Re-evaluate quality drift cost and incidentsMaintain. Owners. Score 5 of 5.10Update docs diagrams backlog and runbooksMaintain. Owners. Score 5 of 5.
User journey: From product decision to supported V1 capability. User journey: 10 stages.

Drawn from its Mermaid source.

As text
Steps:
- 1. Define user promise and release (good). Decide. Product, Design. Score 5 of 5.
- 2. Approve architecture trust and data boundaries (good). Decide. Architecture, Governance. Score 5 of 5.
- 3. Implement contracts storage services and surface (good). Build. Engineering. Score 4 of 5.
- 4. Add failure accessibility and observability behavior (good). Build. Engineering, SRE. Score 5 of 5.
- 5. Run unit contract integration and browser journeys (good). Verify. QA, Engineering. Score 5 of 5.
- 6. Validate security privacy performance and recovery (good). Verify. Governance, SRE. Score 5 of 5.
- 7. Deploy compatible changes and canary cohort (good). Release. SRE. Score 4 of 5.
- 8. Inspect provider receipts and operational evidence (good). Release. SRE, Product. Score 5 of 5.
- 9. Re-evaluate quality drift cost and incidents (good). Maintain. Owners. Score 5 of 5.
- 10. Update docs diagrams backlog and runbooks (good). Maintain. Owners. Score 5 of 5.
Show source
journey
  title From product decision to supported V1 capability
  section Decide
    Define user promise and release: 5: Product, Design
    Approve architecture trust and data boundaries: 5: Architecture, Governance
  section Build
    Implement contracts storage services and surface: 4: Engineering
    Add failure accessibility and observability behavior: 5: Engineering, SRE
  section Verify
    Run unit contract integration and browser journeys: 5: QA, Engineering
    Validate security privacy performance and recovery: 5: Governance, SRE
  section Release
    Deploy compatible changes and canary cohort: 4: SRE
    Inspect provider receipts and operational evidence: 5: SRE, Product
  section Maintain
    Re-evaluate quality drift cost and incidents: 5: Owners
    Update docs diagrams backlog and runbooks: 5: Owners

No actor or gate can stand in for the entire journey. In particular, a product decision is not implementation, a green unit suite is not deployment, and a successful provider call is not the whole member experience.

Review discipline#

Use a diagram to ask better questions, then verify the answer in its canonical source. For a request path, inspect the typed contract, the admitting policy, the owning service, the durable write or provider receipt, and the visible recovery state. For a data relationship, confirm tenant and actor scope, revision behavior, retention, deletion, provenance, and audit semantics in the real schemas and migrations. For an action lifecycle, prove idempotency, authorization freshness, lease fencing, retry limits, cancellation, and compensation with tests that cross the relevant boundaries.

Review diagrams in the same change as the behavior they explain. Rename nodes when ownership changes, remove edges that no longer exist, label rollout or provider conditions, and preserve explicit refusal or withheld paths. A visual that silently promotes a plan to a runtime fact is a documentation defect even when its syntax renders perfectly. Conversely, implementation detail that does not change responsibility, sequence, state, or evidence need not make the overview denser; link to the focused source instead.

How to use this atlas#

  • Start with the landscape to choose the owning surface/domain/substrate.
  • Use the request sequence to trace an end-to-end behavior.
  • Use the ER model when reviewing identity, data, evidence, retention, or deletion.
  • Use the action lifecycle when reviewing commands, tools, workbenches, jobs, confirmations, retries, or compensation.
  • Use the class model when evolving shared contract boundaries.
  • Use the ownership map to find the correct cross-cutting handbook.
  • Use the release timeline and journey to keep product scope and completion evidence honest.

Continue into the feature index, architecture index, Eve, workbenches, Telegram, and Lilith handbooks. The generated Docs Center diagram gallery links every additional diagram to its host page and heading.