# Tasks

Human-readable companion to `tasks.json`.

## Purpose
- `tasks.json` is the structured source of truth for active task state.
- This file explains how to use it and what kinds of items belong there.

## Task statuses
- `open` → captured, not actively being worked yet
- `in-progress` → currently being worked
- `blocked` → waiting on a dependency, decision, or fix
- `done` → explicitly confirmed complete

## Priority meanings
- `high` → important / urgent / likely to need follow-up
- `med` → useful but not urgent
- `low` → backlog / nice-to-have / revisit later

## When to add a task
Add a task when:
- Will asks for something that should be tracked over time
- there is a follow-up commitment
- there is a deferred fix or investigation
- there is a project thread with multiple steps

Do not add a task for:
- tiny one-off answers
- trivial actions completed immediately with no follow-up value
- noisy internal micro-steps

## Operating rules
- Keep active state in `tasks.json`
- Append notable updates to the current daily note when useful
- Mark done only on explicit confirmation or very clear completion evidence
- Prefer a few meaningful tasks over dozens of tiny chores
