# Tasks

Actionable work queue.

Purpose:
- hold concrete work that is ready or nearly ready to execute
- make active priorities visible without mixing them with vague ideas
- give future chats one stable place to pull next actions from

## How to use

Workflow:
1. move shaped work here from `BACKLOG.md`
2. keep each item concrete and execution-oriented
3. mark `active` only for a small number of current priorities
4. move completed items to `DONE.md`

Status meanings:
- `queued`: actionable, not started
- `active`: currently being worked
- `blocked`: waiting on info/access/decision
- `done`: finished; then move to `DONE.md`

Fields:
- `id`: stable handle for future chats
- `status`: current execution state
- `goal`: concrete outcome
- `source`: where it came from (`BACKLOG.md`, project doc, etc.)
- `workspace`: per-task folder for notes/artifacts
- `next_step`: immediate next action
- `notes`: short implementation context

---

## Items

### T-002 - Document reusable offline/navigation patterns
- status: `queued`
- goal: write the durable pattern doc for offline/navigation behavior reusable across Ballbox and local nginx-served surfaces
- source: `BB-002`
- workspace: `/home/sebas/work/tasks/T-002/`
- next_step:
  - draft the first pattern document covering progressive enhancement, cache strategy, offline fallback, history/scroll restoration, invalidation, and rollout boundaries
- notes:
  - this is the main source-of-truth task before local or Ballbox rollouts

### T-003 - Apply offline/navigation patterns to local nginx surfaces
- status: `queued`
- goal: apply the BB-002 pattern set to one local nginx-served surface as the first rollout
- source: `BB-003`
- workspace: `/home/sebas/work/tasks/T-003/`
- next_step:
  - choose the first surface, likely `/portal/` or `/calistenia/`, after T-002 is documented enough
- notes:
  - depends on T-002 being solid enough to guide implementation