§ My Areas of Focus
These are my current Areas of Focus — a Getting Things Done concept. They're the stable organizing principle above all my tools (Todoist, Toggl, Linear, vault).
Areas of Focus
At the highest level, I have 5 overall areas of focus for my life:
- Area - Buffer
- Area - Creator
- Area - Side Hustle
- Area - Personal
- Area - GTD — cross-area and purely operating: running the reviews that keep the other four trusted. Building the system belongs to Sub-area - Productivity System.
Sub-Areas of Focus
Sub-areas are the layer beneath the areas — the things that deserve ongoing attention but have no finish line. Each is a first-class note under Sub-areas of Focus (categories/Sub-area - <Name>.md) so journal entries, meeting notes, Linear projects, and Toggl time can all share it as a join key. A sub-area is the memory of my thinking on a topic.
- Area - Buffer
- Sub-area - Leadership
- Sub-area - Operations
- Sub-area - Management
- Sub-area - Connection (Buffer)
- Sub-area - Customers
- Sub-area - Area Guidance
- Sub-area - EPD
- Sub-area - Marketing
- Sub-area - Advocacy
- Sub-area - People & Finance
- Sub-area - Study
- Sub-area - Reflection
- Sub-area - Team Notes
- Sub-area - Team Responsiveness
- Sub-area - Buffer Tools
- Area - Creator
- Sub-area - Content Creation
- Sub-area - Community Building
- Sub-area - Note Making
- Sub-area - Creator Tools
- Sub-area - Personal Website
- Sub-area - Note Taking System
- Sub-area - Productivity System
- Sub-area - Helping Others
- Area - Side Hustle
- Sub-area - Flow Reader
- Sub-area - Curated Clippings
- Sub-area - Creature Comforts
- Area - GTD
- Sub-area - GTD Reviews
- Area - Personal
- Sub-area - Health & Fitness
- Sub-area - Play
- Sub-area - Family
- Sub-area - Connection (Personal)
- Sub-area - Travel
- Sub-area - Home
- Sub-area - Cars
- Sub-area - Wealth
- Sub-area - Personal Tools
Area Guidance carries a nested layer (EPD, Marketing, Advocacy, People & Finance): the roles I play toward Buffer's functions, each a parent_sub_area: child that shares its parent's Toggl category and has no Linear team of its own.
What is not a sub-area
The Todoist project list conflated sub-areas with containers of other kinds. These are deliberately not sub-areas and get no note (classification settled 2026-09-06, recorded on PROD-126):
| Kind | Items | Where they go |
|---|---|---|
| Routine container | 📆 Meetings, 🛠️ Home Maintenance | Recurring routines need a home outside Linear (PROD-129) |
| List-shaped container | 🏠 Housekeeping, 🛍️ Shopping / Errands | Obsidian lists, own migration |
| Dissolved | 🏡 ⚡ Productivity | Served by the PROD team and sub-area-specific projects |
| Merged | 📋 Buffer Systems | Folded into Sub-area - Buffer Tools; its Toggl category stays as a plain binding for old time |
| Named, not sub-areas | Strategy, Owners & Board | Work inside Sub-area - Leadership and Sub-area - Operations, not areas of their own |
| Responsiveness dimension | 📥 External Comms | A different axis from areas; destined for a sqlite store in joeldash/core, separate migration. 🤝 Team Responsiveness was reclassified as a Buffer sub-area on 2026-10-17 — it carries its own Toggl category and real time, the grounds on which Reflection, Study and Team Notes were reclassified in September |
Comms queue (type: comms) |
💬 Slack, 🔵 Linear, ⛺ Campsite, ✉️ Email, 💬 Buffer Messages, 💌 Personal Email, 💬 Personal Messages, 📰 Newsletter Email | Their own comms store project |
Consequence: the Toggl category set is a superset of the sub-area set — six Toggl categories (Home Maintenance, Housekeeping, Shopping, External Comms, GTD, Buffer Systems) track time against things that are not sub-areas. Those bindings stay hand-maintained in project_groups.yaml. Reflection, Study and Team Notes were reclassified as Buffer sub-areas on 2026-09-07; Operations was added without a Toggl category.
Convention
Areas and sub-areas have three representations that must stay in sync:
| Layer | Form | Example | Used by |
|---|---|---|---|
| Vault notes (source of truth) | Note with slug: |
categories/Area - Creator.md, categories/Sub-area - Wealth.md |
The taxonomy itself; project_groups.yaml is derived from these (generator + drift validator, CORE-381) |
| Persistence filenames | Slug in filename | weekly-priorities-creator-2026-05-20.md |
get_agent_state / get_agent_log MCP filters (regex on filename) |
| Vault frontmatter | Wikilink | area: "[[Area - Creator]]", sub_area: "[[Sub-area - Wealth]]" |
Goals, habits, projects, journal + meeting notes, agent state/log files; queried by Bases + Dataview |
The bridge is the slug: field on each hub note — categories/Area - Creator.md::slug resolves to creator, categories/Sub-area - Wealth.md::slug to wealth (the same key project_groups.yaml uses). Emojis are display-only (display_emoji: frontmatter + # 🎨 Creator heading) so tooling can ignore them.
Each sub-area note declares: slug, area (wikilink), display_emoji, toggl_id, todoist_id (retires with Todoist), linear_team (the sub-team key in my joelg Linear workspace), and parent_sub_area (set on nested sub-areas, which share the parent's Toggl category). Each area note declares linear_team for its parent team. Linear teams are the tree of areas and sub-areas: one parent team per area, one sub-team per top-level sub-area (nested children have none). The product teams (Dash Web, Dash App, Dash Extension, Core, Agent Skills) sit under a separate non-area Code parent; the Tools sub-areas (Buffer, Creator, Personal) run multi-team projects with them. The team key is one more id on the taxonomy, like the Toggl category; the notes stay the source and the tree is built from them.
area: null (or omitted) marks intentionally cross-area artifacts (e.g. retro-review-*.md, agent-stack-decision-*.md). sub_area may be omitted where only the area is known.
GTD as an area
The ⚡ GTD review rhythms became their own top-level area in September 2026 — see Area - GTD and Sub-area - GTD Reviews, which carry the old ⚡ GTD Toggl category and Todoist project.
Todoist setup
I organize Todoist projects both as nested projects and with the emoji of the Area of Focus included in the project name. This means I can easily see — and programmatically retrieve — projects for an Area of Focus by looking at project names for an emoji. For example, all Personal projects include the 🏡 emoji in their name.
Areas of Focus and Linear teams
They used to be different concepts — teams were product and domain boundaries, deliberately mismatched against areas. Since September 2026 they are the same tree.
- One parent team per area, and one sub-team per top-level sub-area.
- A non-area Code parent holds the multi-area surfaces, the things I build rather than areas of my life.
- A project is usually multi-team: a product team plus the sub-area team it serves.
So the bridging the agent layer used to do — correlating Linear teams to areas approximately — is gone. The team is the sub-area.
The team list is not written down here. Read it from Linear: clinear teams for the charters, clinear docs --team KEY for a surface's charter doc. See How my GTD works now.
History
In January 2026, I restructured from 5 areas to 4 by eliminating ⚙️ Systems as a standalone area. Systems projects were distributed to the areas they serve (Buffer systems → 🚀 Buffer, Creator systems → 🎨 Creator). This change was made to enable cleaner separation between Buffer and Creator work, allowing dedicated Creator focus time without Buffer-related systems appearing.
In May 2026, the vault representation was unified: 4 area hub notes (categories/Area - X.md), wikilink-based area: frontmatter convention everywhere, deduplication of habit notes, and consolidation of three legacy "Areas of Focus" notes into this hub.
In September 2026, ⚡ GTD became a fifth area — cross-area and purely operating, holding the review rhythms while all system-building stays in Creator. It is the counterpart to the January change, kept narrow so it does not become another Systems.
In September 2026, sub-areas became first-class notes (categories/Sub-area - X.md) and the source of truth for the taxonomy, with project_groups.yaml derived from them. Containers that had been listed as sub-areas (routines, lists, comms queues, responsiveness) were classified out. Part of the GTD on Linear + Obsidian project.