Skip to content
Sadie

Today

Today is where Sadie lands each session. You get three cards. Not ten, not a feed, not a timeline. Three.

Each card is a discourse opportunity: a live conversation Sadie thinks you are positioned to enter right now, given everything she has learned about how you think.

What’s on a card

Section titled “What’s on a card”

Every card is built from four frames:

  • Why now. What changed in the last day or two that makes this topic worth your attention. A cluster of feed items crossing a threshold, a policy shift, a new paper, a thread that has reached critical mass.
  • Why you. Why your specific wiki, your specific Soul, your specific obsessions connect to this moment. This is the line that would be missing from any generic briefing product.
  • Who’s talking. A handful of voices already in the discourse. Handles, rough stance, and a short quote from each so you can decide whose thread to reply to.
  • Candidate angles. Three to five plausible things you could say, each with a confidence score and usually a single critique: the one sharpening note Sadie has on that angle.

Click through the card and you can save it, dismiss it (with a reason), or open the related wiki entries and feed items that generated it.

Why three and not thirty

Section titled “Why three and not thirty”

Today is editorial by design. The product’s job is to spare you the timeline, not to replace it with a second one. If you want volume, Feeds is where raw signal lives. Today is curation.

When you dismiss a card, the reason you pick (stale topic, wrong audience, not useful, wrong take) flows into your Soul’s substance tier. Sadie learns what falls off your radar, not just what you engaged with.

Recalibrating cadence

Section titled “Recalibrating cadence”

Today refreshes whenever the compile job runs. The default cadence is every four hours. If you want hourly cards, daily, or manual only, change it in Settings under Sadie. Pick “Manual only” and the page waits until you explicitly trigger a recompile.

If you have not wired up a scheduler, the cadence setting just captures intent: the next recompile respects it. Self-hosters can run pnpm dev:scheduler locally or hook the same endpoint from a Cloudflare Worker in production.

Section titled “Related”