Most productivity advice focuses on what to do. Less attention goes to where the data about what you’re doing actually lives — and whether the tools that hold it can communicate with each other.
The Single Source of Truth Plus Satellites (SSoT+S) framework addresses the second problem. It’s a structural model for arranging your productivity stack so that your goals are always the center of gravity, and every other tool orbits them with a clear, functional connection.
This is not a new app recommendation. It’s a way of thinking about the architecture of your existing tools.
Why Architecture Matters More Than App Choice
The productivity software market produces a new “all-in-one” tool approximately every six months. The pitch is consistent: one app to handle goals, tasks, calendar, notes, and everything else. The logic is sound — if everything lives in one place, there’s no fragmentation.
The problem is that no single tool is best at all of these things simultaneously. Notion is excellent for structured notes and databases. Linear is excellent for engineering task management. Google Calendar is the most reliable calendar tool for most people. Trying to force all your workflows into one app means accepting significant trade-offs in the areas where that app is weakest.
The SSoT+S framework takes a different approach. It says: use the best tool for each function, but impose a clear architecture on how they relate to each other. One node is canonical. Every other node is a satellite. Data flows predictably between them.
This is analogous to how well-designed software systems work. A database is the source of truth. Applications read from and write to it. No application maintains its own separate authoritative copy of the data. When you apply this principle to your personal productivity stack, goal fragmentation becomes structurally impossible.
The Two Components in Detail
The Single Source of Truth
The SSoT has one job: it is where goals, milestones, and progress metrics are definitively recorded.
A well-designed SSoT has five properties:
Uniqueness. Goals exist here and nowhere else with authority. If you find yourself maintaining a separate “goals” list in another tool, one of them needs to be absorbed into the SSoT or deprecated.
Completeness. Every active goal lives here. Not “most goals” — all of them. If a goal isn’t in the SSoT, the system doesn’t know it exists, and the satellites can’t serve it.
Structured progress tracking. Goals have a clear progress field — not a freeform notes section, but a structured indicator: percentage complete, milestone status (not started / in progress / complete), or a simple traffic-light system. Structure makes the data queryable by your AI assistant.
A log layer. Each goal record should have a time-stamped log of updates. This is what your AI assistant reads during review sessions — the history of what happened and when.
Access from satellites. Your SSoT should be accessible, or at least exportable, in a form your other tools can read. A locked-down proprietary format that nothing else can integrate with is a dead end.
The Satellites
Each satellite serves a specific function that the SSoT doesn’t provide natively. The four essential satellites:
Task Manager Satellite. Your task manager holds the day-to-day actions that advance goals. The connection to the SSoT runs in both directions: goal milestones generate tasks (SSoT → task manager), and task completions update progress (task manager → SSoT).
The quality of this satellite depends entirely on how well you tag tasks to goals. An untagged task is invisible to the system. Tagging every task at the point of creation is the highest-leverage habit in the entire framework.
Calendar Satellite. Your calendar holds the time you’ve committed to goal-related work. The connection to the SSoT is primarily outbound: calendar data tells the SSoT how many hours you allocated to each goal area this week, and how many you actually spent (assuming you use your calendar to track actual time, not just planned time).
The calendar integration guide covers this satellite in depth, including how to use event labels and color-coding to make goal time allocation readable at a glance.
Time Tracker Satellite. Where the calendar satellite tracks planned time, the time tracker satellite records actual time. This distinction is critical — planning fallacy research shows that people consistently underestimate how long work takes and overestimate how much time they dedicate to high-priority goals.
A time tracker that maps to your goal taxonomy closes this gap. Tools like Beyond Time (beyondtime.ai) are built specifically for goal-time alignment, mapping logged hours to your stated priorities so you can see not just how many hours you worked, but whether those hours served your goals. This data is among the most actionable signals in any goal system.
AI Assistant Satellite. Your AI assistant is the synthesis layer — it reads data from the SSoT and helps you make sense of it. Unlike the other satellites, which primarily collect and transmit data, the AI assistant primarily analyzes and responds.
The connection to the SSoT can be direct (via MCP, if your setup supports it) or mediated (via a structured prompt where you paste in the current goal state). Direct connection is more powerful; mediated connection is sufficient for most users. What matters is that the AI always has access to current, structured goal data before it gives you any advice.
The Connection Topology
Each satellite connects to the SSoT through one of three connection types:
Read connections let a satellite pull data from the SSoT. Your AI assistant uses a read connection to access current goal state before a review session.
Write connections let a satellite push data to the SSoT. Your task manager uses a write connection to update progress when tasks are completed.
Bidirectional connections support both. Your task manager has a bidirectional connection: milestones from the SSoT generate tasks (read), and completions update milestones (write).
Most connections are asymmetric in practice. The calendar writes time-allocation data to the SSoT but doesn’t typically read milestones from it. The AI assistant reads from the SSoT but — unless you’re using a sophisticated setup — doesn’t write back to it. Knowing the direction of each connection helps you design the flows correctly and diagnose them when they break.
How the Data Flows in Practice
A working SSoT+S system has four recurring data flows:
Weekly flow: Task completions → Goal progress. Every week, completed tasks (tagged to goals) flow to the SSoT and update progress metrics. This can happen via a Zapier automation, a native integration, or a five-minute manual update. What matters is that it happens on a fixed schedule.
Weekly flow: Calendar hours → Time allocation. Each week’s goal-tagged calendar events contribute to a running time-allocation metric in the SSoT. You can see, at the goal level, how many hours you planned versus how many you spent.
Weekly flow: SSoT state → AI review. Before each weekly review, current SSoT data is delivered to your AI assistant — either via MCP query or a structured prompt template. The assistant uses this as the basis for its analysis.
Quarterly flow: Goal refresh. Goals change. At the end of each quarter, you review and revise the SSoT: mark completed goals, archive abandoned ones, add new ones, reset milestones. This is the maintenance cycle that keeps the system accurate over time.
Designing Satellite Connections That Last
The most common reason satellite connections break is that they were designed for a specific app version and the app changed. A Zapier flow built around a specific field in Notion breaks when Notion renames that field. An MCP server breaks when the underlying API changes its authentication requirements.
Three practices improve connection durability:
Use stable fields. Name your SSoT fields predictably and don’t rename them. If your goal ID field is called “goal_id,” keep it “goal_id” everywhere — in every satellite connection, every automation, every prompt template.
Document your connections. Keep a simple list (even a text note) of what connects to what and how. When a connection breaks, you can diagnose it in minutes rather than hours because you know where to look.
Test monthly. Schedule a 15-minute monthly review of your automation stack. Run each connection manually, confirm it produces the expected output, and fix anything that has drifted. Connections that fail silently are worse than connections that fail loudly — you don’t know the data is stale until you make a bad decision based on it.
When the Framework Needs to Flex
The SSoT+S framework is a structural principle, not a rigid prescription. Two legitimate exceptions:
Temporary parallel tracking. During a major transition — switching task managers, migrating your note system — you may temporarily run two SSoTs in parallel. This is acceptable as a migration state. It should resolve within four weeks; if it doesn’t, you haven’t committed to the migration.
Domain-separated stacks. Some people find it useful to maintain separate SSoTs for work and personal goals, with the same satellite architecture serving each. This is a principled exception — two SSoTs are fine if they cover genuinely separate domains and there’s no goal that meaningfully belongs to both.
What doesn’t work is an arbitrary proliferation of goal-holding locations — a Notion database, a Notion page, a Google Sheet, a note in Bear — where each one “might” be the real source of truth but none of them definitively is. That’s not a multi-SSoT architecture; it’s a lack of architecture.
The Framework Versus the Method
SSoT+S is an architectural framework, which means it’s agnostic about how you set and manage your goals. Whether you use OKRs, SMART goals, the 12-Week Year method, or your own system, the framework applies. It doesn’t tell you which goals to set or how to prioritize between them. It tells you where to record them and how to ensure your tools support them.
This makes it compatible with any goal methodology and any AI workflow. The integration with MCP, Zapier, or native connections is mechanical. The thinking about what goals matter — that’s still yours.
Identify your SSoT candidate today and audit the five most important tasks in your current list to see whether they’re tagged to a goal.
Tags: AI tool connection framework, single source of truth, productivity stack architecture, goal integration, satellite tools
Frequently Asked Questions
-
What makes the Single Source of Truth Plus Satellites framework different from other productivity systems?
Most productivity frameworks tell you how to think about goals or tasks — GTD, OKRs, PARA. The SSoT Plus Satellites framework is structural rather than methodological. It doesn't tell you what goals to set or how to prioritize. It tells you how to arrange your tools so that whatever goal method you use, the data flows coherently between the tools that support it. It's a system architecture, not a planning philosophy.
-
Can I use this framework with my existing tools, or do I need to switch apps?
You can use it with any combination of tools that have some data-sharing capability. The framework specifies structure, not specific apps. Your SSoT can be Notion, Obsidian, Airtable, a Google Sheet, or a dedicated goal app. Your satellites can be whatever task manager, calendar, and time tracker you already use. The only requirement is that your chosen SSoT can receive input from the satellites — which almost any tool can, even if only via a manual weekly update.
-
How many satellites should I have?
Three to five is the practical range for most knowledge workers. The essential satellites are: task manager, calendar, and AI assistant. Optional satellites that add significant value: time tracker, project management tool, note-taking app. Beyond five, the connection overhead starts to exceed the value of the data flowing through those connections. More is not better — coherence is better.