Skip to content

Memory

Memory is where Sadie’s knowledge of you lives. Everything on Today, every chip you attach in Chats, every discourse opportunity is grounded in something here.

The surface has six tabs. You can treat them as the six faces of one thing.

The Graph tab is the visual map. Nodes are wiki entries, sources, soul items, briefs, ideas, and feed items. Edges are typed: mentions, derives, refutes, supports, anchors, related, authored.

The renderer is custom canvas plus HTML. Earlier versions used Sigma.js; the current implementation gives Sadie full Clay art direction, custom layout tuning, and avoids the WebGL SSR boundary. Node radii use a power curve so weight differences at the high end are visually meaningful. Hover a node and its neighborhood dims the rest. Click a node to jump to the underlying entry, brief, or source.

The Wiki tab lists every wiki entry. Entries are the primary compounding artifact: markdown bodies plus metadata that synthesize what you know about a concept, person, theme, or open question. Each entry carries provenance (which sources and feed items support its claims), status (active, stale, contradicted, draft), and a full patch history.

Wiki entries are versioned. Every mutation writes a wikiPatchEvents row with the before and after content hash, the trigger, and the sources involved. You can trust that nothing has been silently overwritten.

When you edit a wiki entry, Sadie records the save as a rewrite correction signal. Future generated wiki pages can learn from what you tightened or made more specific, while still treating only cited sources as factual evidence.

Sources are the raw material. Notes, past posts, saved articles, RSS, newsletter content, Notion or Obsidian exports, Readwise highlights, direct uploads. The library is general-purpose: anything worth keeping goes here, and the compilers draw from all of it.

You can optionally weight a source (personal library, representative of me, reference material, use cautiously). Weighting is a framing knob, not a gate. Sources without weighting still count. When you add or weight a user-chosen source, the Soul learning ledger records the signal so Sadie can explain what it learned from that choice.

Filed Studio drafts carry provenance in the library. Source rows show whether they came from Studio or from a Today-origin Studio draft, and the detail view keeps the path back to the original draft or Today card when available.

Briefs are time-boxed synthesis artifacts. Where a wiki entry is meant to compound over months, a brief is scoped to a moment: what does the current wave of discourse around a theme mean for you, given what you already know. Briefs anchor to wiki entries and reference the feed items they synthesize.

Briefs can be filed, which promotes their content into the related wiki entries or creates a new entry. They can also be edited or dismissed; edits become rewrite correction signals, and dismissal records negative brief feedback so future brief generation avoids the same failure mode.

Each brief detail page includes a compact trust panel derived from the stored source trail: cited live items, wiki anchors, section structure, and whether the brief has been filed, edited, dismissed, or left as-is.

Soul is Sadie’s structured model of you. Three layers sit together: individual soul_state claims (audience, voice, obsession, allergy, recurring theme, goal, taste, angle style), a deeper voice portrait with eight dimensions, and a narrative context portrait in six sections.

You can edit any of it. Soul is meant to be corrected, not just accumulated. Each claim exposes evidence and a “Why this confidence” rationale so you can see whether Sadie is relying on confirmation, recent reinforcement, multiple receipts, a manual correction, or a still-tentative signal. The learning ledger also names posted-angle outcomes as landed examples or prediction misses, including the metrics and pattern tags Sadie is learning from.

Activity is the durable log of what Sadie has done: compile runs, promotions, soul updates, brief dismissals. It is the audit trail you reach for when you want to know why something changed. Compile entries can also show trust-check chips for Today cards and briefs that were kept or held back, so an empty refresh is visible as a quality decision rather than a silent miss.