Documentation Index
Fetch the complete documentation index at: https://lurkai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What Nerve is
Nerve is Lurk’s intelligence layer. It is designed to sit across the product and help users understand what matters, what changed, what deserves attention, and what may be worth reviewing next. If the terminal is where users work, Signal Search is where users research, and the Arb Scanner is where users find possible opportunities, Nerve is the system that helps connect those pieces into a smarter workflow. Nerve is not a separate feature users occasionally open. It is the layer that helps Lurk feel more aware, contextual, and useful over time.What Nerve is for
Nerve helps users:- understand what changed since they last checked
- prioritize markets, signals, and opportunities
- surface relevant context from across Lurk
- connect Signal Search results to market activity
- connect Arb Scanner opportunities to broader market context
- identify which items deserve attention first
- reduce noise in the workflow
- make the product feel more personalized and intelligent
How Nerve fits into Lurk
Lurk has several core product areas.Terminal
The Terminal is the main workspace for reviewing markets, opportunities, and trading workflow. Nerve helps the Terminal by prioritizing what matters and surfacing context around the user’s current activity.Signal Search
Signal Search helps users research a market, event, or trade idea. Nerve can use that research context to help connect searches to relevant markets, saved items, alerts, or future recommendations.Arb Scanner
The Arb Scanner finds possible cross-market opportunities. Nerve helps rank, explain, and contextualize those opportunities so users are not just staring at raw spreads.Divergent View
Divergent View explains why an Arb Scanner result may exist. Nerve helps connect that divergence to supporting context, related markets, freshness, and user attention.Threshold Alerts
Threshold Alerts notify users when something crosses a level they care about. Nerve helps make alerts more useful by connecting them to context instead of treating every alert as isolated noise.Track Records and Lurk Scores
Track Records show documented history. Lurk Scores summarize credibility signals from that history. Nerve can use those credibility signals to help users understand which people, sources, or strategies may deserve more attention.What Nerve may surface
Depending on the current version of Lurk, Nerve may surface things like:- markets that moved since the user was away
- scanner opportunities worth reviewing
- stale or suspicious scanner results
- relevant Signal Search context
- active Threshold Alerts
- related market movement
- saved items that became relevant again
- high-priority signals
- changes in user-watched markets
- credibility context from Track Records or Lurk Scores
Example workflow
A user opens Lurk. Instead of manually checking every page, Nerve may help answer:- A market moves.
- A related Arb Scanner opportunity appears.
- Divergent View shows the spread may be caused by real cross-venue disagreement.
- Signal Search finds new context around the event.
- A Threshold Alert triggers.
- Nerve prioritizes the item because it connects across multiple signals.
- The user reviews the opportunity with more context and less manual digging.
Why Nerve matters
Without Nerve, Lurk is a set of useful tools. With Nerve, those tools start working together. Nerve helps turn isolated product areas into a connected intelligence system. Instead of forcing users to manually jump between:- markets
- searches
- scanner results
- alerts
- track records
- source context
- saved items
What Nerve is not
Nerve is not:- a trading bot
- financial advice
- a guarantee that something is profitable
- a replacement for user judgment
- a generic chatbot
- a magic answer machine
Best practices
Use Nerve as a starting point for review. When Nerve surfaces something, check:- why it was surfaced
- what market or signal changed
- whether the data is fresh
- whether related context supports it
- whether the opportunity is still available
- whether the alert or signal actually matters to your workflow

