Backlog
The documented ledger for work we deliberately are not doing now: parked investigations (with
their evidence), improvement candidates, and escape-hatched designs. It fills the gap before
something becomes a plan — the promotion path is backlog → docs/plans → docs/adr.
Rules:
- One numbered file per item. Entries are never deleted — status flips instead, so a symptom someone trips over next year finds the prior investigation instead of restarting it.
- Every item carries a Reopen trigger: the concrete event or evidence that justifies picking it up. Until that fires, the item is settled — do not re-litigate it from scratch.
Status: parked(investigated, evidence recorded, waiting on the trigger) ·candidate(improvement we would take, unscheduled) ·promoted → plans/00xx/promoted → adr/00xx(one-line pointer to the plan or ADR that superseded it) ·dropped(decided against; keep the why).- This directory is an engineering ledger, not user documentation.
- 0001 — Electric-proxy auth verification posture — candidate
- 0002 — Provisioning and onboarding UI gaps — candidate
- 0003 — Per-learner Assessment targeting — candidate
- 0004 —
astro checkunder TypeScript 7 — parked - 0005 — Chart app-key name guard — candidate
- 0006 — One-vocabulary sweep residuals — candidate
- 0007 — typesafe-i18n generator under TypeScript 7 — parked
- 0008 — Gate the learner-web Sync monitor to admins — done
- 0009 — Brocrobes browser-extension port — parked
- 0010 — A grouping-unit screen in the Surface Experience — candidate