Some day, I will implement my task priority system. I start with a task's due date as a good proxy for priority, then tweak the priority: 1. The task with due

Some day, I will implement my task priority system. I start with a task's due date as a good proxy for priority, then tweak the priority: 1. The task with due date that comes first has the higher priority. - Tasks with no due date have the highest priority (the task being to give them a due date). - There is an abstract "WHENEVER" due date that is effectively the lowest priority and due infinite days from now. 2. A task's priority may be "bumped up" by creating a subtask with an earlier due date. - This surfaces long-term tasks, forcing you to break them down into smaller tasks. Long-term tasks without smaller short-term tasks can be automatically flagged with warnings and floated to the top.) - The subtask may be abstract/artificial, to tweak the effective priority. Usually manually entered via intuition (or adjusting order via drag-drop UI). An artificial sub-task with effective priority (effective due date) could be calculated by answering questions like in the OP's Task Ranker app. Example: - "Write a book" task due 2024-12-31 can be bumped up with sub-task "Write chapter 1" due 2024-09-01. - The same task can be given an "effective due date" with an abstract sub-task like "Bump priority" due 2024-09-01.