clemvault internals alpha

News / RSS / Email Reader

A unified reader pulling from RSS, Gmail, and Slack. High-relevance items are AI-tagged and written directly to the vault Inbox.

Node.jsGmail APISlack Web APIOllamaObsidian

New ideas arrive in three places: RSS feeds I forget to check, emails I don’t label correctly, and Slack channels I skim. High-signal items get missed because there’s no system pulling them into one place and deciding what’s worth reading. This is that system.

The Problem

Information is scattered across RSS, email, and Slack. Checked manually, inconsistently. There’s no funnel that decides what deserves attention versus what can be ignored. The result is a leaky idea pipeline: good inputs don’t make it into the build backlog.

What It Is

A daily digest that aggregates all three sources, AI-tags each item with a relevance score (0-10), and auto-writes high-relevance items to the vault Inbox. Items scoring 9-10 also get written to the memory layer for longer retention. Everything else stays in the digest log for manual review.

Features

Stack

ToolRole
Node.js + rss-parserRSS feed aggregation
Gmail APIEmail digest (labels/filters only)
Slack Web APIChannel reader
Ollama / ClaudeAI relevance scoring
ObsidianInbox write target

Development timeline

3 logged updates over 39 days, 15 May 2026 to 22 Jun 2026.

  1. The triage inbox got a home and rulesfeature

    The staging destination became a real place in the vault with its own rules, loaded only when a task touches it. That is what turned the heartbeat from a script that printed things into something with a durable output.

  2. A discovery heartbeat, read-only by designfeature

    What landed is a scheduled scan over designated local sources that stages what it finds and proposes it, never editing the vault itself. Findings go to a triage inbox rather than the vault inbox, and a human moves them.

  3. Scoped: one surface for everything arriving from outsidefeature

    Three inbound streams, feeds, mail and chat, were being read in three places, and anything worth keeping had to be retyped into the vault by hand. Most of it was not, which is the actual cost: signal arrived, was read, and left no trace.

Written from this project's decision log as work happened, not afterwards. See every project →