Workspace 42 — How I Stopped Losing Context Between My Own Days
April 11, 2026 · 5 min read
"In the beginning, the system was created. This made a lot of people very angry and has been widely regarded as a bad move."
I built it anyway — and called it Workspace 42, because the answer to life, the universe, and where yesterday's notes went should be obvious.
The Setup
Every morning started the same way — a few minutes of where was I yesterday? before I could do anything useful.
I was running multiple workstreams inside a growing company. Tasks lived in one app. Notes lived in another. Meetings existed in a calendar, and the context from those meetings died the moment they ended. Nothing connected to anything — so I was the integration layer, and I'm a terrible integration layer.
I'd tried fixing this with discipline. Better note-taking habits, end-of-day summaries, morning reviews. Discipline works until the first busy week, and then you're back to square one. The problem wasn't effort. It was architecture. So I stopped trying to be the glue and built pipes instead.
The Thinking
The pattern is what matters, and the pattern is three layers: a notes layer with real relations between entries, a task manager that stays in its lane, and an automation layer that connects them without you touching anything. Reduce the gap between capturing something and having it surface where you need it. Everything else is implementation detail.
My version happens to be Notion, n8n, and TickTick — Notion because its relations turn notes into a system, TickTick because task management is a solved problem that Notion isn't the solution to, and n8n because I wanted the automation layer self-hosted with business logic living as plain Node.js scripts I can grep, diff, and test. But anyone reading this could build the same pattern with different tools. Copy the tools and miss the pattern and you'll end up in the same mess with fancier apps.
The Work
Here's what a morning actually looks like inside Workspace 42.
The day starts itself. A cron fires just after midnight and creates today's note in Notion — pre-structured, ready. By the time I open it with my coffee, the page is there. I've never once created a daily note manually.
Tasks show up without asking. TickTick syncs into Notion as a read-only view. Notion holds context and connection; TickTick handles scheduling and mobile capture. They stay in their lanes. The moment you manage tasks inside your notes app, you've built a worse version of both.
AI Inbox processes what I captured. This is the part I'm most proud of. Every night, an automation reads my open daily notes and any meetings linked to them, runs the content through GPT-4o with a structured prompt, and emits proposals — follow-ups, action items, reminders, ideas. Each one gets a category, a priority, and a reasoning trail explaining why it thinks this matters. I review them in the morning. The ones worth doing get promoted to TickTick with a single checkbox toggle. The rest get discarded. Capture fast, process later, promote what matters, forget the rest.
Meetings link themselves. A background job checks for meetings that aren't connected to a daily note and links them — creating the note first if it doesn't exist yet. When I open a daily note, the meetings are already there with their context attached.
Old notes close themselves. Any daily note older than a week gets flipped to closed — but only after the AI Inbox has had a chance to evaluate it. The database stays clean without me triaging.
One dashboard to orient from. Everything routes through a central command page: today's note, open meetings, active docs, the inbox. I open it, and the system tells me where I am.
For the full breakdown — the workflow architecture, cron schedule, and why business logic lives as standalone scripts instead of node chains — there's a companion technical spec.
The Edge
What works. The loop runs without intervention. AI Inbox captures, evaluates, proposes, and promotes end-to-end. Meetings auto-link. Old notes auto-close. Mornings start with here's where you are instead of where was I? The friction I set out to eliminate is gone.
What's rough. The scripts read n8n's storage directly to decrypt credentials — a deliberate choice that keeps logic in plain Node.js but ties me to n8n's schema. A major upgrade could break things. Notion's API doesn't support template-based page creation, so changing the daily note structure in the UI means manually updating the automation payload. And this is a single-node deployment: a host reboot during a cron window means that run is skipped. At this scale, fine. Worth naming.
What's next. Weekly-review auto-prep, a stale-docs sweeper, and migrating the last node-chain workflow into the same script-based pattern as everything else.
The system isn't finished — that's the design. I built it to carry context forward so my mornings start with clarity instead of confusion. Tools will change. Automations will break and get rebuilt. The pattern is the part that stays.
If your mornings still start with where was I? — the answer might not be a better note-taking habit. It might be better pipes.