Created by: Xule LinRead the full argument: The Foreclosure Problem on Thread CountsImplementation: Available to Thread Counts paid subscribers as a skill file that any coding agent can use to build a customized scanner for your research domain.
The Foreclosure Problem
When we sit down with seed papers and a careful prompt, AI can produce helpful results — related work, relevant concepts, a summary of the landscape. But how often does it challenge us to look at what we didn’t know to ask? This is less of an AI problem and more a framing problem. Humans have always done this: following citation chains that loop back on themselves, reading the same thirty people who read each other. With AI, the closure happens faster and less visibly. When you can process a hundred documents in an afternoon, efficiency almost feels like thoroughness.The most valuable thing any knowledge search can do is not confirm what you suspected but change what you’re looking for.
Exploitation and Exploration
James March’s distinction between exploitation (working with what you have) and exploration (searching for what you don’t know you’re missing) is one of the most durable ideas in organizational theory. AI makes this tension sharper. Exploitation is where AI chatbots shine — talk through implications, test logic, identify unstated assumptions in your known material. Exploration is the harder problem. Maybe a parallel conversation is happening in a field that uses completely different terminology. Maybe someone in an adjacent discipline wrote the exact critique of your underlying assumption years ago. Broad searches generate thousands of results, beyond human capacity to process. What changes with agentic AI tools is the possibility of doing both simultaneously, at scale. One thread goes deep into seed material. Another scans broadly across databases, catching anomalies that don’t fit your criteria but share structural similarities with your question. A third brings these together.What the Research Scanner Does
The scanner is a pipeline that turns a coding agent into a thinking partner for literature surveillance — not just retrieval, but interpretation based on a profile you curate together over time. Built to run with Claude Code (though adaptable to any coding agent), the scanner queries academic APIs — Semantic Scholar, OpenAlex, and arXiv — across two directions:- Exploitation layers — what’s new in the journals and topics you already watch
- Exploration layers — citation-chasing, author-tracking, and semantic similarity searches that surface papers you’d never have searched for
“While you were away, three things happened that complicate the argument you were building.”That’s the kind of provocation that makes thinking sharper.
Why This Matters for Research
For someone with deep expertise, this means building systems that force encounters with what you’d otherwise filter out — narrowing from a position of strength. For someone starting out, the foreclosure problem is about never having the breadth to narrow from. The scanner addresses both: it starts wide and narrows as your taste develops. The concept registry evolves with your understanding. Last week’s assumptions get re-tested against this week’s literature.Part of the Research Memex Ecosystem
The Research Scanner connects to:- Agentic Workflows — The broader vision for multi-agent research systems
- Memex Plugin — Persistent memory that tracks how your research question evolves
- Zotero Setup Guide — Where scanner results land for reference management
- AI Model Reference Guide — Choosing models for agent triage of scan results