Document type: plan
Table of Contents
This page defines the plan document type — one entry in the
document types taxonomy. The general contract every document follows
(frontmatter, state, linking, tags) lives on the taxonomy page; this
page carries only what is specific to plan.
1. Contract
- Implements
- loading. See Regulatory Functions.
- (no term)
- Lives inside a task or story document as the
* Plansection. Not a separate file. (Previouslyplan.orgas a sibling file; that was retired when tasks became flat files.) - Level
s1(task plan) ors2(story plan).- Transient
- cleared or summarised in
* Noteswhen the task or story closes; distilled content moves to* Decisionson the parent story. Plans do not outlive their task.
2. Not to be confused with design
A plan is how we will do this work. A design is what the target state is, and why — the argument that produced the tasks, rather than the strategy for executing one of them.
When a story-scoped argument spans many tasks, precedes them, and will
be distilled into a durable document, it outgrows a * Plan section and
becomes a design.org in the story folder. Everything else stays a
section, as above. A design that produces no durable outcome was a plan
all along.