Dynamic Retrieval
The distinction the 2023 Contrary Research report draws at the retrieval stage of Capture-Storage-Retrieval Pipeline: static retrieval (tags, links, search) depends on the human remembering that the insight exists, recalling where it lives, and going to get it — which reimports the very limit of the unaided mind the store was built to escape. Dynamic retrieval inverts the direction: the system surfaces relevant information based on the user's context and current task, without being asked. The report pairs this with an interoperability requirement — a second brain wired into email, calendar, project and communication tools acts within the user's ecosystem instead of standing alone as an archive.
For the vault: this is the demand side of the retrieval patterns already on the shelf. Context Routing, Semantic Retrieval, and the Retrieval Maturity Levels ladder are mechanisms; dynamic retrieval names the bar they are climbing toward — retrieval initiated by the task, not by the operator's memory. The vault's agent-era resolution is worth noting: the intelligence can live in the agent reading plain files rather than in the store itself (see the tension recorded in AI Second Brain).
Claims
- An AI-powered second brain should adapt to the user's needs and present relevant information based on context and current tasks, in contrast to static tag/link/search stores. (principle — as asserted by the report)
- Retrieval that depends on user-initiated recall is bounded by the human mind's limits; the store's value is capped by what its owner remembers to ask. (principle — as asserted)
- The report cites Coveo research that knowledge workers average 3.6 hours/day searching for information. (observation — the source's statistic; check-worthy)
- Integrate the second brain with the surrounding tool ecosystem (email, calendar, project management, communication) so retrieval can act, not just answer. (best_practice — context: the report's 2023 thesis for AI-native PKM products; "best" where the store is meant to participate in work rather than archive it)
- Information overload is less about volume than unresolved inputs: most captured material is only potentially useful because almost none of it surfaces at the moment it would actually help — the capture-to-reuse gap is the design problem. (principle — as asserted by the glukhov.org second-brain article; an independent restatement of this concept's premise from outside the Contrary lineage)
Related
- Capture-Storage-Retrieval Pipeline — the pipeline stage this concept fixes.
- AI Second Brain — the store; holds the recorded tension over whether dynamic retrieval needs product machinery or just an agent over plain files.
- Context Routing — the simplest working mechanism: tell the agent where to look.
- Semantic Retrieval — retrieval by meaning; one rung of the mechanism ladder.
- Retrieval Maturity Levels — how much retrieval machinery is actually warranted.
- Distillate: From Notetaking to Neuralink (Contrary Research)
- Distillate: Second Brain Explained for Engineers and Knowledge Workers — the capture-to-reuse gap restated as the reason second brains exist.