No Praxis/Areas/ subfolder

Context and Problem Statement

Considered adding Praxis/Areas/ for ongoing no-deadline work (à la PARA’s distinction between time-bound Projects and ongoing Areas). Open question carried through the restructure.

Considered Options

• Do not add Praxis/Areas/. Praxis/ contains only Projects/.
• Add Praxis/Areas/ for ongoing-no-deadline maintenance work.
• Promote completed projects to “Area” status when they continue indefinitely.

Decision Outcome

Chosen option: “Do not add Areas/”, because no current use case demands it. ADHD-aligned principle: don’t pre-build folders for hypothetical needs. The PARA Areas concept is one of PARA’s most-criticized fuzzy boundaries (Areas vs Resources blur). Skip it until a concrete need surfaces.

Ongoing concerns live elsewhere:

• Domain knowledge → Atlas/Notes/
• Reference material → Atlas/References/
• Relationship maintenance → Atlas/People/
• Pondering / open questions → Inbox/Brain Dump.md

Pros and Cons of the Options

No Praxis/Areas/

• Good, because doesn’t pre-build for hypothetical needs.
• Good, because avoids PARA’s fuzzy Areas-vs-Resources boundary.

Add Praxis/Areas/

• Bad, because no current use case.
• Bad, because PARA’s Areas concept has known boundary problems.

Promote completed projects to “Area” status

• Bad, because status frontmatter (active/completed/etc.) handles lifecycle adequately.