generated from eblume/project-template
Erich Blume
1c94a08cda
All checks were successful
Build / validate (pull_request) Successful in 9m33s
A new explanation doc making the task model explicit: lifecycle state
(outstanding → done/dropped) is orthogonal to attention (white/orange/red/
blue), attention only matters while outstanding, and On Deck (blue) is a live
"later" task — NOT the same as dropped ("let go", terminal). Covers delete/
tombstone (soft-delete that keeps the context doc) and a table of where each
task shows up (agenda / search / export). Cross-links design §6.2/§6.3 and
tech-spec §4.3/§7/§8.1/§12; wired into the explanation index.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.1 KiB
1.1 KiB
- Added a task-lifecycle explanation doc: the two-axis task model (lifecycle state — outstanding/done/dropped — kept separate from attention white/orange/red/blue), why On Deck (blue) is not the same as dropped, what delete/tombstone does (and that it keeps the context doc), and where each task shows up across the agenda, full-text search, and export.
- Surface strategy revised to a three-surface model (design §4, tech-spec §1/§8), grounded in a study of the owner's live Todoist usage (387 active tasks, 34 hierarchical projects — design §6.2.1): the CLI is task capture/scripting plus the complete daemon API, a planned
heph-tuiterminal UI (tech-spec §8.1) is the primary task agenda/triage surface, andheph.nvimis the primary context/knowledge-base surface. The study also confirms do-date-not-due-date (zero deadlines used), that task descriptions are already full of unresolved[[wiki-links]](the exact task↔KB fusion heph provides), and surfaces new needs (project hierarchy, natural-language recurrence) while showing tags are negligible.