The Weekly Architecture Session
Once a week, you step back from the daily rhythm and look at the larger picture. The Weekly Architecture Session takes about 45 minutes. It clears the inbox, reviews your projects, checks in on your roles, sets three outcomes for the week, and protects the time to actually pursue them. When it's done, you know exactly what the week is for.
When it runs
The session is triggered by a notification at your configured time — Sunday evening by default, at 7:00 PM. The notification says: "Time for your weekly planning session. 45 minutes now saves 10 hours of confusion this week." You can also open it manually at any time from the Me tab.
The session is a linear wizard — seven screens in sequence. You can't skip screens, but you can exit and resume exactly where you left off. If something interrupts you mid-session, nothing is lost. Pick it back up when you're ready.
Sunday evening works well for most people because it creates a clean mental boundary between the week just ending and the week beginning. But the right time is when you'll actually do it. Some people prefer Friday afternoon as the old week closes. Others prefer Monday morning before the day starts. Whatever you set, the system will prompt you then — consistently, not repeatedly if you decline.
The seven screens
Writing good Big Three outcomes
The Big Three are the most important output of the Architecture Session. They shape which tasks surface in your Launchpad all week, what the fit score boosts, and what the system advocates for when other things are competing for your time. Getting them right is worth taking seriously.
The system's hint text reminds you: "Think in outcomes, not activities. What would done look like?" Here's what that means in practice:
Three outcomes is a hard limit, not a suggestion. The constraint is the point. ADHD often produces a planning impulse that generates fifteen "priorities" — which is the same as having none. The Big Three forces a real decision about what this week is actually for. Everything else is held safely in the system and will surface appropriately.
After you write each Big Three outcome, the system looks for matching active projects and offers to link them. Accepting the link means every task inside that project gets a scoring boost for the week — it surfaces more often, earlier, and more prominently in your Now list. If the outcome doesn't connect to a project — "rest and recover this week" — it still anchors the week even without a boost. Linkage is optional but valuable when it fits.
The role pulse — noticing what's been neglected
Screen 4 is one of the most distinctive features of the Architecture Session. Most weekly reviews ask what you're going to do next week. The role pulse asks what you've been ignoring.
The neglect detection algorithm computes each role's status before the session begins, based on how recently tasks in that role were completed:
Critically neglected roles appear as a warning card at the top of the screen before the full role list — requiring a response before you can continue. This isn't punitive. It's a signal that something real has gone quiet, and the session is the right moment to notice it.
Each role has an optional text field. Write something if it helps you think. The notes are stored in your weekly log and visible to your coach if you have one — a week-by-week record of what you were paying attention to and why.
Time sovereignty — paying yourself first
Screen 6 is where the week gets real. Not the intentions — the actual structure.
The problem with most weekly planning is that it happens in the abstract. You write down what you want to accomplish and then discover on Wednesday that the week's calendar left no room for any of it. The obligations came first. The goals got whatever was left. Which was nothing.
The time sovereignty screen inverts this. You see next week's calendar exactly as it is — every external commitment plotted, every sovereign window highlighted. You see the truth of the week before you plan it. Then for each Big Three outcome, a direct question: "When will you work on this?" You tap a sovereign window. A time for your own goals block appears. The goals are in the calendar before anything else claims those hours.
If you can't find time for one of your Big Three, the screen surfaces that directly: "It looks like this outcome has no protected time this week. Do you want to adjust your commitments, or is this outcome realistic for this week?" This is a real question. If an outcome can't get a single hour of protected time, it may not be a realistic Big Three item for this particular week — and the honest answer is more useful than a plan that was never going to happen.
The maintenance window is a single 60–90 minute block for life-upkeep tasks — household tasks, medical appointments to schedule, errands that have been accumulating. Scheduling it deliberately in the Architecture Session is what keeps maintenance from becoming the reactive flood that drowns the week. One block, once a week, handles it all.
make this week a success?
Screen 4a — File the unfiled (conditional)
This screen only appears when you have more than five active tasks with no role assigned — tasks you created using "I'll decide later" during inbox processing. Below that threshold, the session skips it entirely and moves straight to Screen 5.
Its placement is deliberate. The role pulse just put you in a role-thinking frame of mind — sorting through which areas of your life have been active, which haven't. Asking "want to file the loose ones?" right after is a natural continuation. You're already thinking in roles.
When the screen appears, you get a choice: take a few minutes to file them now, or skip for this week. If you choose to file them, a fast batch flow runs — one task at a time, full screen, same role list the processing flow uses. Three ways to respond per task:
- Tap a role — files the task and advances to the next
- "Skip — still not sure" — leaves it unfiled, advances to the next
- "Done for now" — exits the batch flow, keeps whatever was filed
If you skip the screen, or tap "Done for now" partway through, the session continues without penalty. Whatever was filed sticks. Whatever wasn't filed will appear here again next week if the count is still above threshold. No badge, no notification, no out-of-band nagging — just a quiet reappearance in the session you've already committed to.
"I'll decide later" is a fast escape valve during processing — it lets you capture and move on without forcing a filing decision you're not ready to make. Screen 4a is how those decisions get made eventually, batched into a weekly session rather than scattered across the week as individual interruptions.
What changes after a completed session
Your Big Three are active from the moment the session completes. Tasks inside linked projects immediately receive a fit score boost — surfacing more often, earlier in the Now list. The time blocks you assigned appear in the calendar and on the time strip. The week goes from a collection of tasks to something with an intention. The daily rhythm is how you execute that intention, one day at a time.
Missing one session doesn't break your system. Your tasks are still there, your roles are still there, the Launchpad still works. What you lose is the Big Three boost — tasks won't have active weekly targets to connect to. Run the session as soon as you can; even a shortened version of screens 4, 5, and 6 restores most of the benefit. The system doesn't punish the gap. It just waits for you to return.
In the next part of the guide, we'll go deeper into the building blocks the daily and weekly rhythms operate on — tasks, projects, recurring commitments, and calendar management. These are reference chapters; come back to them when you encounter a feature you want to understand more fully.