Decide deleted-task-statistics design question #17

New issue

Open

opened 2026-07-05 20:02:57 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-07-05 20:02:57 -07:00

Collaborator

Context

Human Documentation/Things to consider todo/Deleted Task Statistics.md raises an open design question: how should the system remember lightweight statistics for deleted tasks while still fully removing them from persistence? Commit f18c5b5 only recorded the question — it did not resolve or implement anything.

Scope

Decide whether a separate deletion-statistics record is needed for V1 (likely shape: deleted task name + deletion timestamp only)
Confirm privacy/export/backup implications of whatever is decided
Close this issue with the decision recorded; file a follow-up implementation issue only if the decision requires one

Out of scope

Implementation itself — this issue is the product decision, not the code.

Acceptance criteria

A decision is recorded (even if the decision is "not needed for V1").

Human Documentation/Things to consider todo/Deleted Task Statistics.md

## Context `Human Documentation/Things to consider todo/Deleted Task Statistics.md` raises an open design question: how should the system remember lightweight statistics for deleted tasks while still fully removing them from persistence? Commit `f18c5b5` only recorded the question — it did not resolve or implement anything. ## Scope - [ ] Decide whether a separate deletion-statistics record is needed for V1 (likely shape: deleted task name + deletion timestamp only) - [ ] Confirm privacy/export/backup implications of whatever is decided - [ ] Close this issue with the decision recorded; file a follow-up implementation issue only if the decision requires one ## Out of scope Implementation itself — this issue is the product decision, not the code. ## Acceptance criteria A decision is recorded (even if the decision is "not needed for V1"). ## Related `Human Documentation/Things to consider todo/Deleted Task Statistics.md`