The daily rhythm: inbox, meetings, and the evening call
The first years of Station were about thinking — capture, challenge,
plan, do. This past stretch has been about something different: making
Station show up on its own schedule, not just when I open a browser
tab. It now bookends my working day, and fills the gaps in between.
← Back to the Station overview · See also:
the grand tour · capturing things ·
from idea to done
Jump to: Inbox triage · Meetings · The debrief call · Journals · The follow-up loop · The shape of it
📥 Inbox triage — the mail gets read before I read it
Station watches my mailbox through Microsoft Graph and classifies
everything that lands — with a few-shot classifier that runs locally
and learns from my corrections, not a cloud service reading my mail.
Each category has a policy I control: newsletters get summarised and
parked, notifications get folded away, things that actually need me
surface with the context attached. When an email contains a commitment or
an action, it doesn’t auto-spawn a task — it pre-fills the task popup
with the source linked, and I decide. (Autopilot is earned, not assumed.)
🎙️ Meetings — the commitments I make out loud
The most dangerous place for a commitment is a meeting: I say "I’ll send
you that report" and it evaporates before the call ends.
Now meeting audio goes through Whisper (locally), and Station reads
the transcript looking for one thing only: first-person, future-tense
commitments that I made. Not everyone’s action items — mine. Each
candidate shows up for a quick confirm or reject, and every decision
trains the extractor. I can correct the transcript, and maintain my own
vocabulary list for the names and jargon Whisper trips over.
And because the transcripts are there anyway: there’s a swear jar. A
persistent, per-word tally of what I said on which call. It survives even
after the recording is deleted, which feels like a design decision aimed
directly at me.
📞 The debrief — Station calls me, in my voice
At the end of every weekday, my phone rings. Full-screen incoming call,
answer/decline, the whole thing. It’s Station — and it speaks in a
clone of my own voice, slowed down a touch, asking me how the day went.
It’s a real interview, not a form: it knows what was on my plate, asks
about what moved, and pulls the loose threads. Out of that ten-minute
call come:
- Journal entries — written per workspace, so the client-work notes
land in the client workspace and the homelab notes in the homelab one. - Untracked work, captured — the things I did but never put in
Station become tasks that are created and closed in one motion,
after I approve them out loud. The record stays honest without me
doing data entry.
Talking to yourself was supposed to be a warning sign. Turns out it’s a
productivity system.
📝 Journals — a diary I don’t have to write
Every workspace has its own journal. The debrief writes them nightly, and
anything notable from the day’s activity lands there too. Months from
now, "what actually happened on that engagement?" has a real answer,
written the same evening — not reconstructed from a calendar.
🔁 The follow-up loop — features don’t get to rot
The newest piece closes a loop most tools never even acknowledge: the gap
between shipping something and knowing whether it earned its place.
Every feature that ships gets registered — with a user-facing test
plan — and Station checks in on it at 2, 7, 14, and 30 days:
did you actually use this? Is it doing what you wanted? The check-ins
are grounded in real usage telemetry (a local, append-only event log
— nobody’s analytics platform), drip-fed one a day so it never becomes
homework, and a "not now" parks the follow-up instead of losing it.
Ripe feedback gets bundled into a triaged batch of fixes. The result: a
personal tool where "shipped but never used" gets caught in two days
instead of never. The house rule is written into the dev standards now —
not registered = not shipped.
The shape of it
Morning: the daily email and the mobile app’s top-3 focus pick.
During the day: inbox triage and meeting capture feed the queue quietly.
Evening: the phone rings, the day gets debriefed, the journals write
themselves. And in the background, the follow-up loop keeps the whole
system honest about itself.
The next step on the roadmap is the other bookend: an overnight
thinker that reads the day’s brain-dump while I sleep and greets me
with syntheses in the morning. Suggest-only — it can look, not touch.
← Back to the Station overview.