generated from eblume/project-template
Some checks failed
Build / validate (pull_request) Has been cancelled
Study of the owner's live Todoist (387 tasks, 34 hierarchical projects) grounds a surface-strategy revision: structured task fields suit CLI flags, large-set triage suits an interactive TUI, and context/KB suits nvim — so v1 adopts three surfaces, each to its strength. Supersedes the earlier "heph.nvim is the primary surface" framing. - design.md: new §6.2.1 (Todoist study) + revised §4 (three-surface model) - tech-spec §1/§8: reframe surface roles; new §8.1 (planned heph-tui agenda) - tech-spec §14: reorder remaining work (CLI-complete task surface in progress, heph-tui next, nvim navigation polish, tags/hierarchy deferred) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
739 B
739 B
- 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.