ADR 0007: BACKLOG.md for work tracking

Published

September 25, 2026

Context

We considered GitHub Issues (private repo), beads and kata (local agent-oriented trackers), and plain SQLite. A remote repo would publish institutional curriculum data, including paths that may name students. The backlog is small, and it’s one person plus an agent.

Decision

Track work in BACKLOG.md (Now / Next / Later / Blocked / Parked), findings in NOTES.md, and decisions in ADRs. There is no remote until the data review in the backlog is done.

Consequences

Tracking changes land in the same commits as the work. Revisit if the backlog grows past about 30 items or several agents work in parallel. kata is the preferred trial.