Question intelligence: the demand signal nobody else has.
Market data is a commodity; the stream of what people ask is not. Question Intelligence instruments every question across the products into anonymized, aggregate signal: which names and intents the market is confused about right now, a form of information asymmetry that can lead volume and volatility.
Instrument the questions, not the people
Every question or query across issuer Q&A, education, and the API explain endpoints is recorded into aggregate counters by symbol, intent, and source, plus a grounded-versus-refused ratio that tracks answer quality. Recording is best-effort and can never break an answer: it swallows all errors. The insights view is fully anonymized (no principal, no identity) and surfaces the top symbols and intents the audience is asking about, alongside a live sample of recent question shapes.
An MVP that starts the flywheel
This is honest about its stage. The current implementation is an in-memory store that resets on restart, with an optional Supabase backend that persists events when configured. Persistence is the productization step; the mechanism itself, capturing demand signal from question one, is what makes the asset compound. The same stream feeds the Alpha Feed, which aggregates recent questions into a rolling view of where attention is concentrating.
- Aggregates questions by symbol, intent, and source into anonymized signal
- Grounded-versus-refused ratio as a live answer-quality gauge
- Top confused symbols and intents, plus a recent-question sample
- Zero identity capture: aggregate counters only, no principal stored
- Recording is failure-safe and never blocks or breaks an answer
- In-memory MVP today, with an optional Supabase persistence backend
Questions
Is any personal or identity data stored?
No. Question Intelligence keeps only aggregate, anonymized counters by symbol, intent, and source, plus recent question shapes. It records no principal or identity.
Does it persist across restarts?
The default is an in-memory store that resets on restart. Setting a Supabase URL and service key turns on persistent storage; the endpoint reports which backend is active.
What is the signal actually good for?
It surfaces what the audience is confused about right now, which can concentrate before it shows up as volume or volatility. It is descriptive signal, not a prediction or advice.