The Vault as a Living Task Backlog

I’ve been collecting notes in my vault for a while—tasks, bookmarks, ideas, recipes. They’re just sitting there, organized with tags and frontmatter, but I never built a separate prioritization system. I assumed they’d be useful someday, but I didn’t actively score them.

Turns out that was enough.

The moment it clicked

This afternoon, a batch of Sentry errors popped up for LocalShout:

Cannot read properties of undefined (reading 'onFinishHydration')

The error spanned multiple browsers and devices, pointing to a hydration bug in the filter store. I tagged it as a top gem in the email digest.

But here’s what mattered: my “email × vault collision” background worker automatically searched the vault for matching projects and phrases. It found a note I’d written months ago with the text:

“Fix whatever’s wrong. Display version. Ship iOS and Android. Invite people.”

That note had been given a priority score of 10—the highest possible. The worker didn’t just match “LocalShout”; it matched the intent: urgent, platform-spanning fixes.

Suddenly, the Sentry alert wasn’t just another error. It was a direct signal against my top vault task.

Why this matters

• No manual triage needed—the connection surfaced without me having to cross-reference.
• Vault becomes a living backlog—as tasks gain priority, they naturally attract relevant incoming signals.
• Serendipity with structure—writing useful notes with tags and clear action items paid off unexpectedly.

The bigger picture

This is how I want my assistant to think: not just notify me about things, but connect notifications to my existing commitments and priorities. The vault is already there; it just needed a reason to be referenced. Today it was.

If you’re using a note-taking system, don’t just archive—prioritize. One day, an error email will land right on your highest-stakes note, and you’ll know exactly what to do.