Where this is going
A journal should run on your own machine.
What you write here is about as personal as text gets — how you slept, who you called, what you're trying to stop doing. That kind of record shouldn't live on someone else's computer because that was the only option on offer.
Five parts, one loop
Journal
You write what happened and how it went. Nothing is required of it — several entries a day or one a week, whatever the rhythm you set.
Habits
The steering made concrete. Each one carries a cadence — once, twice, three times a day, a week, a month, a trimester, a semester, a year — so you can see what's holding.
Goals
The part that points forward. Open-ended, or a to-do you tick off — and each one keeps a thread of how it changed shape.
Check-ups
Once a week, five questions with that week's numbers beside them. Where you look at the rest and decide what changes.
Insights
A gratitude, a realization, a lesson, a pattern you noticed. Short, dated, and kept apart from the day's entry so they stay findable.
Works with no AI at all
Reflect answers real questions — how you've been, what you did, how you felt that day — and every one of those answers is arithmetic over rows you wrote. No model sees your entries to produce them. That isn't a limitation to be fixed later; it's the floor everything else stands on.
A platform, not just a page
The intent is to speak MCP, so the journal is something you can talk to from the assistant you already pay for — or from a free account — rather than a place you have to visit. The website and the interface an assistant sees would be the same journal underneath.
Companions you choose
If you do turn AI on, what it's like should be your call — one that simply holds the facts, one that reads you back through Stoicism, one that keeps a record of what went well and tells you so. Different companions over the same journal. On your own compute and your own tokens where you have them.
Where it actually stands
- Journal, habits, goals, check-ups, insights
- Runs without any AI
- Your data stays in one file
- No third-party requests
- MCP interface
- Companions
- Open source
- One-command self-install