|
71 | 71 | - [x] Either show something like in tasks-collector-tools (summary of each day with plan/reflection/etc.) |
72 | 72 | - [x] Or make a console tool |
73 | 73 | - [x] Add markings if weekly summary and monthy summary has been added for this period |
| 74 | +- [x] Either remove projected outcome events from events or handle them in tasks-collector-tools |
| 75 | +- [x] Show weekly plan on the tasks utility and journal so that focus/want is more visible |
| 76 | +- [x] Enable login on every page and request |
74 | 77 |
|
75 | 78 | ## Pending Tasks |
76 | 79 |
|
77 | | -- [ ] How about [ ] for Plan? |
78 | | - - Need to rethink that / possible to use other input method |
79 | | -- [ ] Show weekly plan on the tasks utility and journal so that focus/want is more visible |
80 | | -- [ ] a weekly report could list out count and a summary of all items as email (for example) |
81 | | - - [ ] Add ell and personality cores to summary |
82 | | -- [ ] Add journal to the `today` view |
83 | | -- [ ] add `pub_date` to events and allow for setting different day (yesterday) than now for events affecting a specific date (e.g. HabitsTracked) |
| 80 | +- AI Ideas |
| 81 | + - [ ] a weekly report could list out count and a summary of all items as email (for example) |
| 82 | + - [ ] Add personality cores to summary |
| 83 | + - [ ] create a quantified satori element |
| 84 | + - [ ] on a scale 1-10 how was I close to the "true-to-self" (breakthrough) goal? Was there some task that was connected to the projected outcome elements? |
84 | 85 | - [ ] Add post-it boards for ideas |
85 | 86 | - [ ] Use the tasks backend |
86 | 87 | - [ ] Add another view (with two components – a "shelf" and a "board") |
|
89 | 90 | - [ ] Put things back from board to shelf |
90 | 91 | - [ ] Coordinates remove |
91 | 92 | - [ ] ability to move board around |
92 | | -- [ ] Observation Closed History View |
93 | | - - [ ] [Merge View](https://codemirror.net/try/?example=Merge%20View) |
94 | | - - [ ] Event timeline component |
95 | | - - [ ] Better styling |
96 | | -- [ ] Dump database before automatic migration / deployment |
| 93 | +- Devops |
| 94 | + - [ ] Dump database before automatic migration / deployment |
97 | 95 | - [ ] Quests: merge them with journals |
98 | 96 | - [ ] (draft) Use journal for journalling, and quest object as a side to it |
99 | 97 | - JournalQuestMeta: quest_id, journal_id, stage |
|
102 | 100 | - [ ] PoC: https://developers.google.com/tasks/quickstart/python |
103 | 101 | - [ ] Board action |
104 | 102 | - [ ] Board status - scheduled |
105 | | -- [ ] Habits – shift around |
106 | | - - [ ] Define a list of habits I'd like to track |
107 | | - - Possible integrations: |
108 | | - - Internal with events |
109 | | - - External with GH API |
110 | 103 | - [ ] Add Expectation model to Habit to track redline/greenline, goal, etc. |
111 | | -- [ ] Habit: plan satisfied? |
112 | | -- [ ] Threads / split into threads and scopes |
113 | | -- [ ] Journal with reflections from daily reflection from past 7 days |
| 104 | + - [ ] Habit: plan satisfied? |
114 | 105 | - [ ] Split/merge observations |
115 | | -- [ ] Add ObservationMentioned event |
116 | | -- [ ] Add plan templates for a day (e.g. Cleaning: ..., Writing: ..., etc.) |
| 106 | +- [ ] Add plan templates to Journal (e.g. Cleaning: ..., Writing: ..., etc.) |
117 | 107 | - [ ] Add [ ] to journal processing so that it can be used to add a plan for tomorrow |
118 | | -- [ ] Ideally if journal add, etc. returned in their json additional objects that were created, so that can be printed out as a summary then on the frontend |
119 | 108 | - [ ] The same view as eventdump but on web |
120 | 109 | - [ ] migrate distractions to integrity? true-to-self |
121 | | -- [ ] ell / use that for a quantified satori element |
122 | | - - on a scale 1-10 how was I close to the "true-to-self" (breakthrough) goal? Was there some task that was connected to the projected outcome elements? |
123 | | -- [ ] Enable login on every page and request |
124 | 110 | - Creativity Explorer |
125 | 111 | - [ ] Random: Three events and and "find a connection" |
126 | 112 | - Pseudorandom -> navigate left/right/top (leave one item, add two random) |
|
129 | 115 | - Year-on-Year Explorer |
130 | 116 | - [ ] See journal entries from last 5 years |
131 | 117 | - [ ] Allow to write a journal with a specific tag |
132 | | -- [ ] Refactor text processing for side-effects as a separate layer (e.g. journal -> reflection + habits, etc) – so that can become a more unified mechanism (allowing for on/off processing etc) |
133 | | -- [ ] Either remove projected outcome events from events or handle them in tasks-collector-tools |
| 118 | +- Side-effects refactor |
| 119 | + - [ ] Refactor text processing for side-effects as a separate layer (e.g. journal -> reflection + habits, etc) – so that can become a more unified mechanism (allowing for on/off processing etc) |
| 120 | + - [ ] Ideally if journal add, etc. returned in their json additional objects that were created, so that can be printed out as a summary then on the frontend |
134 | 121 | - [ ] Completely REFACTOR weekly/monthly summary code into a better shape |
| 122 | +- [ ] Threads / split into threads and scopes |
135 | 123 | - [ ] How about I do the AREAS for life? |
136 | 124 | - [ ] To mark then reflection templates (weekly monthly) |
137 | 125 | - [ ] Better product roadmap than this TODO file |
|
0 commit comments