When two tools hold the same data, designate one canonical…
When two tools in your stack both maintain authoritative copies of the same data type, designate one as canonical (single source of truth) and demote the other to either capture-point (temporary holding before transfer) or read-replica (displays data but cannot edit) status to prevent sync drift.
When This Fires
- When the same information exists in multiple tools and you're not sure which is current
- When "sync issues" cause missed tasks, conflicting data, or lost updates
- When designing a multi-tool workflow and deciding where data lives
- Complements Automate the single highest-frequency manual data transfer… (automate highest-frequency transfer) with the architectural decision that makes automation meaningful
Common Failure Mode
Dual-authority systems: tasks in both Todoist and Notion, both treated as authoritative. You add a task to Todoist on your phone, mark a different task complete in Notion on your laptop, and neither system reflects the other's changes. Two weeks later, you miss a deadline because the task existed in one system but not the one you checked.
The Protocol
(1) List every data type in your tool stack: tasks, notes, contacts, calendar events, project status, reference materials. (2) For each data type, identify all tools that contain it. (3) For each data type with 2+ tools: designate one as canonical. This is the source of truth for that data type. All edits happen here. (4) Demote other tools to capture point (data enters here temporarily, then gets transferred to canonical — e.g., quick-capture app → main task manager) or read replica (displays data from canonical but is not directly editable — e.g., calendar widget showing tasks from your task manager). (5) Document the designations: "Tasks: canonical = Todoist. Notion task view = read replica. Apple Reminders = capture point (transfer within 24 hours)."