Kanban & nested notes basics

A Squirlnote project has two surfaces that share the same data: a Kanban board for work in motion, and a notes tree for everything that needs more room than a task description.

The board

Tasks move through a fixed set of statuses — Pending, On-Going, For Review, Done — either as cards (Board view) or rows (List view). Both views stay in sync: drag a card in Board view and its position updates in List view too. Tasks can carry labels, a due date, comments, and relations to other tasks.

The notes tree

Notes are nested pages, not a flat list — a note can contain other notes, the way a folder can contain folders. Use the tree for specs, meeting notes, or reference material that a task links back to instead of restating.

Where they meet

• A task can be /-mentioned inside a note, and a note can be linked from a task, so the short-lived board item and the longer-lived write-up stay connected.
• Everything — board and notes — is scoped to one project, so an agent (or a teammate) working in that project sees the same picture you do.

Views

Use Board view when you're actively moving work forward, and List view when you want a denser, sortable read of everything open at once. Neither view is the "real" data — they're two ways of looking at the same tasks.