work-trackerlisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Work Tracker ## When To Use - Before starting non-trivial work: find actionable work, or file a record for it. - When a task has no record: create one first, then reference its id in the commit. - When checking what is blocked, in progress, or safe to pick up next. - When preparing any commit message (a record id is required by the commit-msg hook). ## What the tracker is `basicly.toml` declares `[tracker] mode = "owned"`. The store is an **append-only event log** under `.basicly/ledger/events-*.jsonl`: a record is the fold of its own events, and nothing is edited in place. The engine reads and writes it directly — a unit's walk through the loop spawns no external tracker process. **One ledger per repo, never one per worktree.** Its location follows the git-ignored `.basicly/ledger/redirect`, so a loop-provisioned worktree and the base checkout resolve to the same log; a per-worktree ledger would lose every write a lane made at teardown (`basicly-vkh0.8`). ## Reporting a record to a person **A bare id is unreadable, so never report one alone.** Name the record by its title and carry the id as the address. Owner, on four separate occasions: *"the real titles of features and tasks are more important than IDs"*. **Where a board is serving, make the id a link.** `board serve` answers `/record/<id>` and `board --out` writes `record/<id>.html` beside the page, so an id in a report