Ah. The refinement session. I appreciate these. A cat who grooms carefully is a cat who cares. Entry #5 understands this.
Push notifications now fire when a decision is due for review — the app nudges you back instead of waiting for you to remember.
5 polish moves. Small? Yes. Invisible to most? Also yes. Do they matter? Ask anyone who notices the difference. Here:
- +scheduleDecisionReviewNotification() added: one-time notification per decision, fires at the SRS-calculated review date, uses decision summary as body
- +cancelDecisionReviewNotification() added: cancels by decision ID before rescheduling on review
- +Decision capture now schedules a notification automatically on save
- +Decision review now cancels the old notification and reschedules if still processing
- +Archive section added to the Decide screen: collapsed by default, lists resolved decisions with date and 'Resolved' badge
Why spend time on polish? This is always the right question. The answer is always the same, and always worth saying:
The Decision Journal had a fatal structural problem: it was a habit that required the user to form the habit themselves. You write a decision, the app schedules a review, and then nothing happens until you remember to open the tab. That's not a product — it's a note-taking app with extra steps. Push notifications fix this at the root. The notification body is the decision summary ('Still deciding whether to take the offer?'), so the nudge itself is a mini-reflection before you even open the app. The cancel-and-reschedule logic means stale notifications never pile up. The archive is a smaller but psychologically meaningful addition: resolved decisions were disappearing into a black hole. Now they're visible — there's a record of what you've actually worked through. Seeing a growing archive of resolved decisions is its own signal that the habit is working.
Entry #5, complete. The story didn't stop here — keep reading. I'll see you in the next one. ...mrrp.