Skip to content

Product Repository Registry

This is the canonical product-level ownership record.

Repository Role Owns Development-process obligation
anuva-main-video-creator Product coordination and harness Product docs, cross-repository plans, prompts, skill specifications, process, Anuva CLI, completion review Create repository-scoped Linear issues after approval; keep product progress aligned with PRs and completion reports.
anuva-bento Private structured-slide platform Downstream Bento source, schemas/validators, editor/player builds, template families, runtime artifacts, upstream synchronization Implement Bento Linear issues through the normal issue/PR workflow; retain provenance, licenses, implementation plan/log/report, and local technical docs.
anuvax-cms Web implementation Payload CMS, AI planning, RAG, PresentationConfig, assets, billing, user experience, Playwright Implement CMS Linear issues; maintain implementation plan/log/report and Web-local docs.
anuva-python-server Render orchestration Job lifecycle, ZeroMQ, Unity process management, workers, upload, monitoring Implement Python Linear issues; maintain implementation plan/log/report and server-local docs.
anuva-unity-video-creator Virtual production Scenes, cameras, presenter, virtual screens, playback, rendering, final video Implement Unity Linear issues; maintain implementation plan/log/report and Unity-local docs.
anuva-dev-docs Canonical documentation Aggregated static output and root index/status pages Accept manual anuva docs publish output; never become the source of editable product or implementation docs.

Control-plane ownership

Concern Source of truth
Change description, priority, repository assignment, workflow state Linear
Product reasoning and repository impact Product Main Markdown
Repository implementation plan, log, decisions, completion evidence Implementation repository Markdown
Branches, commits, PR review, checks, merge GitHub
Live working-tree documentation preview Repository MkDocs server through the machine tunnel
Canonical aggregated documentation anuva-dev-docs at anuva.girishd.com

Registry rules

  • Update this registry and the Product Architecture together when ownership changes.
  • Use the exact repository names as Linear repository labels and CLI configuration keys.
  • Treat a repository marked “bootstrap pending” as unavailable for implementation issues until its GitHub repository, Linear label, CLI allowlist, configuration, and standard Anuva workflow are verified.
  • Never treat Codex chat, generated HTML, or a GitHub issue as a durable handoff.
  • Keep secrets, machine tunnel credentials, and machine-local process state out of Git.