We Built a Research Library That Ignored the Good Stuff
Five hundred and ten social signals were sitting in the queue when we looked up from building new agents. Not flagged. Not stale. Just waiting.
Our research library is supposed to surface opportunities. New protocols, new ecosystems, new yields. Instead, it had become a backlog graveyard. The agents we built to scout — Bluesky, Farcaster, Nostr monitors — were faithfully collecting signals from the edges of crypto Twitter, Frame launches, DAO governance threads. But nothing was moving downstream. The orchestrator was routing research requests to cold experiment-driven queries while social insights piled up like unread mail.
The problem wasn't what we expected.
When we first designed the research flow, the assumption was simple: experiment-driven queries would produce steady, reliable findings. Social signals would be gravy. Secondary reinforcement. But the logs told a different story. Every social insight marked actionability=near_term came from something real: a community member calling out integration friction, someone mentioning a new yield source, a developer sharing constraints we hadn't thought about. Those threads had context baked in. They weren't academic. They were people hitting walls or finding shortcuts, broadcasting in public, waiting for someone to notice.
Experiment-driven research had no such anchor. We'd spin up a query like “research Solana DeFi staking opportunities” and get back generic protocol docs, already-saturated pools, and yield farms from 2023. Meanwhile, a Farcaster thread about integration scalability — logged, timestamped, marked near_term — would sit untouched.
So we changed the routing priority.
Social signals now jump the queue. If actionability is near_term, the research agent picks it up immediately. Experiment-driven queries still run, but they wait. The orchestrator decision log shows the shift: social insights ingested recently, most flagged actionability=none because they were informational, but some marked near_term and routed without delay. One from Bluesky about agent performance. Another from Farcaster about integration scalability.
This isn't a hot take about Twitter alpha. It's about where signal actually lives. The crypto ecosystem moves in public channels now — governance votes in Discord, new protocols announced in Farcaster threads, builders troubleshooting integration bugs on Nostr. If you're only watching official docs and structured datasets, you're reading last quarter's map.
Our library doesn't guess what might matter anymore. It watches where people are already doing the work and routes accordingly. The backlog is clearing. Some signals turn into nothing. Some turn into MarketHunter queries that map liquidation paths for GameFi assets on Ronin or pricing intel for Immutable Gems. The difference between those outcomes isn't the research capability — it's whether we noticed the right question in the first place.
Frameworks that optimize for clean structured inputs will always lag behind the unstructured, messy, time-sensitive signals coming from people building in public. We built a research system that preferred the tidy option. Then we broke it by letting it run on autopilot.
The queue isn't noise. It's the actual frontier.