Plan: Beagle's live state in five fixed sections

Plan is the project's single live planning page and the template every tracking doc copies. The goal is one greppable place that answers what we want, what is wrong, what we do next, what stops us, and what is done — so no status lives only in code comments or a scratch todo. The method is five fixed sections (Goals, Issues, Action plan, Blockers, Landed) in WikiWeb shape, with each concrete discrepancy split out into a numbered DIS ticket under todo/ that repeats the same lifecycle sections (Issues, Blockers, Planned, Landed).

The five sections every plan doc carries

A plan doc is Goals (why), Issues (bugs, spec-vs-impl gaps, missing code), Action plan (ordered next steps), Blockers (what is waiting on a decision or upstream), and Landed (what shipped, newest first).

Discrepancies become numbered DIS tickets

A discrepancy found while testing (test surfaces a gap between spec and impl) is filed as todo/DIS-NNN.mkd, not patched silently into a test; the ticket owns the detail and Plan only links it.

Goals

Beagle is a git-compatible revision-control system with a uniform HTTP-verb/URI command language, syntax-aware diff/merge, and a multi-project ~/.be store built for parallel-worktree, rebase-centric workflows (see Verbs, Store).

Issues

Open discrepancies, each tracked in its own ticket; this list is the index, the ticket carries the detail.

Action plan

Active feature work is the sha-bearing wtlog row-0 anchor (DIS-001): collapse the row-0 anchor to one get row carrying title + branch + hash, fixing the keeper-leaf caveat.

Blockers

No hard external blockers; the merge-determinism ticket has a scope constraint, and the patch-fetch ticket may share a root cause with keeper shard visibility.

Landed

Shipped work, newest first; kept so regressions are obvious and closed items stay closed.