...::: User story :::... As a regular Recall user with a reasonably large knowledge base, I want to be shown an occasional surprising connection between two or more items in my own content, so that I rediscover things I've forgotten and notice links I would never have searched for. ...::: Problem :::... Recall is excellent at cross-referencing when I go looking. The retrieval model is pull, not push. Everything I get out depends on me remembering that something is in there, or thinking to ask about it. With a few thousand cards accumulated this year, most of the base is effectively dormant. The value sitting in older material is invisible unless a search query happens to hit it. Search rewards what I already know I want. It does nothing for what I've forgotten I have. ...::: Proposed behaviour :::... On login, or on page load with sensible frequency capping, surface a small non-blocking card. It presents one insight drawn from my own knowledge base. Framings could rotate: ■ Did you know - a fact, claim or observation surfaced from across the knowledge base and its connections. Not restricted by age or last-opened date. The test is whether it's interesting, not whether it's old. ■ Hidden gem - content saved but never revisited. ■ Unexpected connection - two cards from different topics, sources or time periods that share a concept, argument or contradiction. ■ Then and now - something saved a year ago that relates directly to something saved this week. ■ Contradiction watch - two sources in the base that disagree on the same point. One says a control works, another says it doesn't. I may have saved both without noticing they conflict, and holding both unexamined is a small blind spot worth exposing. ■ Bridge card - a single item that sits between two otherwise unconnected clusters. It's the only thing linking two areas of interest, which usually means either it's unusually valuable or the connection is worth developing. ■ Orphan cluster - a group of related cards that connects to nothing else in the base. A topic that was picked up, explored briefly, and abandoned. Useful for spotting dropped threads. ■ Recurring theme - a concept that keeps appearing across sources I never filed together, saved over months without ever being named as a topic. Effectively: here's a pattern in your reading that you haven't noticed you have. ■ Source echo - two different authors, publications or formats making substantially the same argument. Either corroboration worth trusting more, or a sign that a single idea is circulating unchallenged and both sources trace back to one origin. ...::: Requirements :::... ■ Insights are drawn only from my own content. No external suggestions. ■ Each insight links directly to the source cards so it can be followed up immediately. ■ Frequency is configurable: every load, daily, weekly, off. ■ Fully dismissible and fully disableable, in settings, not buried. ■ Dismissal is per-insight, not per-session, so a bad one doesn't cost the feature its credibility. ■ Feedback signal on each card, something as light as useful or not useful, to tune what gets surfaced. ■ Insight types should be individually toggleable. Some users will want connections but not trivia. ■ Where an insight type depends on age or visit history, prefer older and less-visited material. This does not apply to “Did you know”, which should draw from the whole base. ...::: Request motivation :::.... The reason I build my personal knowledge base is the belief that past reading compounds. In practice it only compounds if it resurfaces. This feature turns the archive from a lookup system into something that occasionally teaches me something about my own thinking. It's also a differentiator. Plenty of tools store and retrieve. Very few tell you something you didn't know you knew.
