Skip to content

Git and Notion Responsibilities

Devonshire Digital uses two systems that must not be confused with one another: this Git repository, and Notion. This document defines what each is responsible for.

Git is canonical

This repository (Git) is the canonical source of truth for:

  • Approved company policies and standards.
  • Company and venture Architecture Decision Records (ADRs).
  • AI agent instructions (AGENTS.md, CLAUDE.md, GEMINI.md, and docs/ai/).
  • Product specifications and component specifications.
  • Versioned technical artifacts of any kind.

If a question arises about what the current, authoritative rule or specification is, the answer is whatever is in this Git repository (at the appropriate document status — see docs/governance/document-lifecycle.md), not whatever happens to be written in Notion.

Notion is management-only

Notion may be used for:

  • Portfolio views and dashboards.
  • Prioritization and planning.
  • Task tracking.
  • Roadmaps (as working/planning artifacts, not as specifications).
  • Discussions and management workflows.

Notion is a useful tool for the human-facing, fast-moving work of running the company day to day. It is not a substitute for the documentation discipline this repository enforces.

Notion does not override Git

Notion does not silently override approved repository documentation. If Notion content conflicts with an approved document in this repository, the repository wins (see docs/governance/authority-and-inheritance.md) unless and until the repository is deliberately updated to reflect a new decision. A Notion page is not a valid mechanism for changing company policy, a standard, or a specification — those changes flow through the normal document lifecycle in this repository.

If a contributor or agent notices Notion and Git disagreeing about something that matters, that is a contradiction to be surfaced and escalated per docs/governance/authority-and-inheritance.md, not silently resolved in either direction.

Synchronization

A future integration or synchronization approach between Git and Notion may be defined later. This is explicitly not implemented now. See docs/governance/open-questions.md (OQ-010) for this open question. Until it is resolved, any duplication between the two systems is maintained manually, and Git remains authoritative wherever the two disagree.

Report an issue about this page