Skip to content

Sources of Truth

The process uses several durable systems, each with a deliberately narrow role.

Information Authoritative system Examples
Development work classification and approval policy Product Main Markdown Anuva Development Process Policy
Product request and priority Linear change intake issue User outcome, constraints, priority
Work scope and state Linear implementation issue Repository, status, dependencies, acceptance checks
Product reasoning Product Main Markdown Change brief, repository impact, ADR, progress, completion review
Implementation reasoning Implementation repository Markdown Implementation plan, log, decisions, completion report
Code delivery GitHub Branch, commits, PR, checks, reviews, merge
Live docs view Machine-specific MkDocs preview Current working tree, including uncommitted docs
Published docs anuva.girishd.com Manually refreshed canonical aggregate

Linear is required for product intent, shared application contracts, and cross-repository implementation handoffs. It is not the default record for routine repository changes, development-process work, or machine operations. Those lanes use the proportionate durable records defined by the development policy.

Every active change should be navigable in both directions:

flowchart LR
    Change["Linear change issue"]
    ProductDocs["Product Main change folder"]
    Impl["Linear implementation issue"]
    ImplDocs["Repository implementation docs"]
    PR["GitHub PR"]
    Completion["Product completion review"]

    Change <--> ProductDocs
    ProductDocs <--> Impl
    Impl <--> ImplDocs
    Impl <--> PR
    PR <--> ImplDocs
    Completion --> Change
    Completion --> ProductDocs
    Completion --> Impl
    Completion --> PR

Conflict rules

  • If Linear scope and repository docs disagree, stop implementation and resolve the issue description or plan before continuing.
  • If a PR differs from the approved plan, document the reason in the implementation log and update affected contracts before merge.
  • Never infer delivery from a chat message. Product and tracked implementation work requires the corresponding GitHub and Linear evidence. Issue-free routine or development-process work requires the approved repository delivery evidence for its lane.
  • Generated HTML is disposable. Edit source Markdown only.