Tasks live in Obsidian with structural discipline; calendar items live in Calendar

Context and Problem Statement

ADHD literature recommends tasks-out-of-notes-app to prevent rot. But the vault functions as a single entrypoint for me and LLM agents — splitting tasks across tools breaks unified context. The 2024 → 2026 brain-dump drift showed unstructured todos rot in any app.

Considered Options

• Tasks in Obsidian as - [ ] checkboxes in known locations; calendar items in Calendar (with MCP for agent access).
• All tasks in dedicated app (Things / Reminders / Todoist).
• All tasks in Obsidian without Calendar split.

Decision Outcome

Chosen option: “Tasks in Obsidian, calendar items in Calendar”, because the actual ADHD failure mode wasn’t “tasks in same app as notes” — it was “unstructured todos in long docs that nobody reviewed.” Structural discipline (- [ ] shape, predictable locations, aggregation surface) addresses the real failure mode while preserving single-source-of-truth for agents. Calendar items are time-bound events, not actions; they benefit from native calendar surface.

Tasks live in:

• Praxis/Projects/<name>.md ## Next Actions
• Inbox/Brain Dump.md triage queue
• Daily notes

Recurring/habit tracking is out of scope for the vault. Calendar tool selection is pending; current practice keeps appointments in Inbox/Brain Dump.md.

Pros and Cons of the Options

Tasks in Obsidian + Calendar split

• Good, because preserves single-entrypoint-for-LLM benefit.
• Good, because events vs actions are conceptually distinct surfaces.
• Bad, because requires structural discipline that user must maintain.

All tasks in dedicated app

• Good, because matches ADHD orthodoxy.
• Bad, because breaks single-entrypoint-for-LLM benefit.

All tasks in Obsidian without Calendar split

• Good, because keeps unified context.
• Bad, because conflates events with actions.