Skip to content

Product Repository Registry

The Product Repository Registry is the canonical product-level record of the repositories that participate in Anuva Video Creator delivery, coordination, and publishing.

flowchart TD
    Handbook["anuva-engineering-handbook<br/>Engineering Platform"]
    DevDocs["anuva-dev-docs<br/>Docs publisher"]
    Main["anuva-main-video-creator<br/>Product coordination"]
    Project["Anuva Video Creator<br/>GitHub Project"]
    Web["anuvax-cms<br/>Web and CMS"]
    Python["anuva-python-server<br/>Render orchestration"]
    Unity["anuva-unity-video-creator<br/>Virtual production"]

    Handbook -. "standards" .-> Main
    Main --> Project
    Main --> Web
    Main --> Python
    Main --> Unity
    Main -. "source docs" .-> DevDocs
    Web -. "source docs" .-> DevDocs
    Python -. "source docs" .-> DevDocs
    Unity -. "source docs" .-> DevDocs

Current Product Repositories

Repository Status Role Product Responsibility Product-Main Sync
anuva-main-video-creator Active Product / Program Management Vision, architecture, roadmap, product capability map, repository registry, cross-repository planning, product GitHub task creation, playbooks, prompts, product ADRs, releases, progress reviews, and product documentation. Owns feature change folders, tasks.yml, GitHubTasks.md, Progress.md, and release review.
anuvax-cms Active Web implementation Web application, Payload CMS, AI planning, RAG, PresentationConfig generation, asset management, billing, user experience, and Web-local docs. Receives Web-scoped GitHub issues and reports PR, docs, verification, and integration notes back through issues and project fields.
anuva-python-server Active Python implementation Render orchestration, ZeroMQ communication, Unity lifecycle, render workers, upload pipeline, monitoring, and server-local docs. Receives server-scoped GitHub issues and reports PR, docs, verification, and integration notes back through issues and project fields.
anuva-unity-video-creator Active Unity implementation Virtual production, cameras, bot presenter, virtual screens, playback, rendering, final video generation, and Unity-local docs. Receives Unity-scoped GitHub issues and reports PR, docs, verification, and integration notes back through issues and project fields.
anuva-engineering-handbook Active Engineering Platform Shared engineering standards, Codex workflows, AGENTS.md guidance, change workflows, templates, prompt library, registry rules, and skills guidance. Update only when product work changes shared Anuva process, ownership, templates, prompts, skills, or registry rules.
anuva-dev-docs Active Docs publishing Aggregated development docs publisher and GitHub Project status page for discoverable docs output. Refresh or document refresh need when product-main docs, implementation docs, or GitHub Project status output changes.

GitHub Project Coordination

anuva-main-video-creator coordinates implementation work through the Anuva Video Creator GitHub Project after product docs are reviewed.

Expected project fields:

Field Purpose
Status Tracks Backlog, Ready, In Progress, In Review, Done, or Blocked state.
Repository Names the owning repository for the task.
Feature ID Links issues, PRs, and product-main docs for one feature.
Product Change Folder Points to the product-main source folder under docs/changes/.
Priority Helps sequence implementation work.
Docs Impact Records None, Local, Product, Handbook, or Publisher impact.
PR Links the implementation pull request.
Verification Tracks Pending, Passed, Skipped, or Failed verification state.

Registry Rules

  • Add or update registry entries when repository ownership changes.
  • Keep this registry aligned with the Product Architecture and Capability Map.
  • Do not record implementation details that belong inside implementation repositories.
  • Link product-level plans to repository-specific GitHub issues and project items when work is ready.
  • Keep GitHubTasks.md, Progress.md, GitHub issues, PR completion reports, and project fields aligned for active product changes.
  • Route shared process changes to anuva-engineering-handbook and publishing refreshes to anuva-dev-docs.