Anuva Repository Bootstrap Context

This implementation repository owns its code, local docs, tests, and verification. anuva-main-video-creator owns product planning, repository impact, cross-repository acceptance, shared workflow specifications, and product completion review.

flowchart TD
    Product["Product Main plan"] --> Child["Repository-scoped Linear child"]
    Local["Repository-local request"] --> Preflight["Plugin ownership and risk preflight"]
    Preflight --> Routine["Routine: issue-free delivery"]
    Preflight --> Material["Material: plan approval, then delivery"]
    Preflight --> Escalate["Product Main required; no side effects"]
    Tracked["Explicit standalone tracking request"] --> Standalone["Marked standalone Linear issue"]
    Child --> Repo["Implementation repository PR"]
    Standalone --> Repo
    Routine --> Repo
    Material --> Repo
    Repo --> Report["CompletionReport evidence"]
    Report --> ProductReview["Product Main completion review"]

Use Linear for Product Main children and explicitly requested standalone tracking, GitHub as the code-delivery plane, and repository Markdown as the technical record. Follow docs/process/ChangeWorkflow.md and docs/bootstrap/AnuvaCli.md. Older references to GitHub issue handoffs, GitHub Projects, BrainDump requirements, or manual status changes are superseded by this contract.

Repository-local changes use $anuva-development:anuva-repository-change. Routine and material changes are issue-free by default; material work has a separate exact-plan gate. Product decisions, shared contracts, multiple implementation repositories, migrations, authentication/authorization, privacy, security, billing, deployment architecture, release coordination, and ownership uncertainty return to Product Main without creating a standalone issue, branch, artifact, or PR.