Standalone

A node that has no prerequisites and no dependents. Useful for milestones, events, or work whose dependencies aren't fully understood yet.

A standalone is a node that has no prerequisites and no dependents. It exists on the graph but doesn't participate in the project's dependency structure.

What they're for

Standalones are useful for capturing work or events that matter to the team but don't fit the graph's structural logic. Examples from Tree's own roadmap include:

  • "100th tree planted" (a milestone tied to user growth, not project work)
  • "First user who isn't a friend" (an event that marks a moment but doesn't unlock or depend on anything else)

Why a graph can hold them

A list-based tool wouldn't have a natural place for standalones because lists assume sequence: every item is positioned relative to other items.

A graph-based tool can hold standalones as nodes that simply exist without edges, occupying their own space on the canvas without forcing them into a structure they don't belong to.

A placeholder slot

Standalones are also useful for capturing project work whose dependencies aren't fully understood yet. A node can be planted as a standalone, then edges added as the team discovers what it depends on or what depends on it. Standalones are the "we know this matters but haven't placed it yet" slot.

How they render

Tree renders standalones in a separate visual region of the canvas, typically along an edge or in a dedicated band. They're available for completion the same way any other node is, since they have no prerequisites to satisfy.

LAST UPDATED · 2026-05-11