Twinned from https://github.com/cfsh/ninefold/issues/1009 by tools/beads/import_github.py's reconcile pass.
Design doc: design_docs/011-task-tracking-on-beads.md (PR to follow from branch design/beads-tracking).
Recommendation in two lines: migrate the issue side of the workflow (issues, claims, labels, per-doc task boards) into Beads (bd) — local ~0.7s reads, sync over the git wire protocol on the existing remote (no API quota), scheduled JSONL export to a private R2 prefix as the tracker-independent backup — and keep PRs + review on GitHub. Design docs stay repo files + PRs; their tasks become a bd epic (which also lands the 'project' generalisation).
Shape of the work: nine tasks, ~10-11 PRs. T1 (a battle-test prototype tracking design 011's own tasks in bd, in parallel with GitHub) lands first and alone; T2 (cross-machine sync), T3 (R2 backup — blocked on Aedan minting a private-prefix token), T4 (the nflib/bd.py seam) follow in parallel; T5–T8 (poll issue-half, triage/spec/claims, operationalize→epics, dashboard on local bd) build on the seam; T9 (import + turndown of GitHub Issues) is last and gated on a real chunk running end-to-end in bd, the cross-machine drill, and one R2 restore drill.
None.
No comments.