Product Architecture

Anuva Video Creator is coordinated from anuva-main-video-creator and delivered through three implementation repositories. The shared Engineering Platform is defined by anuva-engineering-handbook, while aggregated documentation is published through anuva-dev-docs when configured.

flowchart TD
    Org["Shoonya Organization"]
    Platform["Engineering Platform"]
    Handbook["anuva-engineering-handbook"]
    Product["Anuva Video Creator"]
    Main["anuva-main-video-creator"]
    Project["Anuva Video Creator<br/>GitHub Project"]
    DevDocs["anuva-dev-docs"]
    Web["anuvax-cms"]
    Python["anuva-python-server"]
    Unity["anuva-unity-video-creator"]

    Org --> Platform
    Org --> Product
    Platform --> Handbook
    Platform --> DevDocs
    Product --> Main
    Handbook -. "process, standards, templates" .-> Main
    Main --> Project
    Main --> Web
    Main --> Python
    Main --> Unity
    Main -. "source docs" .-> DevDocs
    Web -. "local docs" .-> DevDocs
    Python -. "local docs" .-> DevDocs
    Unity -. "local docs" .-> DevDocs

Product Repository Hierarchy

anuva-main-video-creator is the product coordination parent for:

• anuvax-cms
• anuva-python-server
• anuva-unity-video-creator

It also coordinates the Anuva Video Creator GitHub Project for implementation handoffs, progress tracking, verification state, and product review state. The GitHub Project does not replace source docs; it links product change folders to repository-owned issues and PR completion reports.

End-to-End Product Flow

sequenceDiagram
    participant User
    participant Web as anuvax-cms
    participant AI as AI Planning / RAG
    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 script, structure, assets, and config intent
    Web->>Python: Submit render job with PresentationConfig
    Python->>Unity: Start render workflow
    Unity->>Python: Return render output
    Python->>Web: Publish completed video metadata
    Web->>User: Deliver final video

Boundary Principle

This repository defines what the product is, where work belongs, and how cross-repository changes should be planned. It does not contain Web, Python, or Unity implementation code.

Implementation repositories own code, tests, local technical docs, and repository-specific implementation decisions. Shared process or ownership model changes belong in anuva-engineering-handbook; aggregated publishing mechanics belong in anuva-dev-docs.