"Not yet" conditions the forecast instead of clamping the window #12
Labels
No Label
P0
P1
P2
release-blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Privacy-Period-Tracker#12
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The baseline handles a "Not yet" by moving
windowStartpast the ruled-out date and subtracting a flat penalty from confidence. That satisfies the letter of §51's not-yet case and misses what §13 actually asks for.§13: "Do not merely move a fixed prediction by +1 day without updating confidence and the remaining probability distribution", and "Repeated 'Not yet' observations should progressively update the forecast."
What to build:
The distribution stays internal. §12: the normal interface should not show percentages unless usability research supports it.
Trap: renormalising a distribution whose remaining mass is nearly zero — a user who says "not yet" far past every candidate — must degrade to a sensible answer rather than producing a division by zero or a wildly confident date.
Verify: a test where the forecast is Aug 22–24 and Aug 22 is answered "Not yet" shows the most likely date, the window AND the confidence all changing; and five consecutive "Not yet" answers move the forecast progressively rather than in equal steps, without the window collapsing or the confidence rising.