Product Architecture

Anuva Video Creator is coordinated from anuva-main-video-creator and delivered through its registered implementation repositories. Product delivery and development coordination deliberately use separate ownership boundaries.

flowchart TD
    Main["anuva-main-video-creator\nProduct + process + Anuva CLI"]
    Linear["Linear\nwork control plane"]
    GitHub["GitHub\ncode delivery plane"]
    Bento["anuva-bento\nPrivate slide platform"]
    Web["anuvax-cms"]
    Python["anuva-python-server"]
    Unity["anuva-unity-video-creator"]
    DevDocs["anuva-dev-docs\ncanonical aggregate"]

    Main --> Linear
    Main --> GitHub
    Main --> Bento
    Main --> Web
    Main --> Python
    Main --> Unity
    Bento -. "contract, editor, player" .-> Web
    Bento -. "player artifacts" .-> Unity
    Main -. "source docs" .-> DevDocs
    Bento -. "source docs" .-> DevDocs
    Web -. "source docs" .-> DevDocs
    Python -. "source docs" .-> DevDocs
    Unity -. "source docs" .-> DevDocs

End-to-end product flow

sequenceDiagram
    participant User
    participant Web as anuvax-cms
    participant AI as AI planning and RAG
    participant Bento as anuva-bento
    participant Python as anuva-python-server
    participant Unity as anuva-unity-video-creator

    User->>Web: Create project and provide knowledge
    Web->>AI: Plan presentation
    AI->>Web: Return structure, narrative, assets, and multi-surface intent
    Web->>Bento: Validate documents and host exact-version editor/player
    Bento->>Web: Structured surfaces and player artifacts
    Web->>Python: Submit render job with PresentationConfig
    Python->>Unity: Start and monitor render workflow
    Unity->>Python: Emit render progress and output
    Python->>Web: Publish progress and completed-video metadata
    Web->>User: Show progress and deliver final video

Development boundary

Product Main defines product behavior, repository ownership, cross-repository contracts, and the development harness. Implementation repositories own their code, tests, local technical docs, and repository-specific decisions. Linear links the work; GitHub delivers the code; Markdown explains why and how.

anuva-bento is the registered private downstream boundary under ANU-8. It owns Bento product implementation and upstream synchronization; Product Main owns the cross-repository contract, acceptance gates, and completion review.