Skip to main content

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
The goal is not to overwhelm users with more information. The goal is to help users see the right information faster.

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 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
Nerve is meant to act like a prioritization layer across the product.

Example workflow

A user opens Lurk. Instead of manually checking every page, Nerve may help answer:
What changed?
What matters?
What should I look at first?
Why is this being surfaced?
What context do I need before acting?
A typical Nerve-assisted workflow could look like:
  1. A market moves.
  2. A related Arb Scanner opportunity appears.
  3. Divergent View shows the spread may be caused by real cross-venue disagreement.
  4. Signal Search finds new context around the event.
  5. A Threshold Alert triggers.
  6. Nerve prioritizes the item because it connects across multiple signals.
  7. 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
Nerve helps organize the workflow around relevance.

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
Nerve does not exist to make decisions for users. It exists to help users decide what deserves attention.

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
The best use of Nerve is not blind trust. The best use is faster triage.

Common issues

“Why is Nerve showing me this?”

Nerve may surface something because it connects to market movement, scanner activity, alerts, saved context, Signal Search results, or other relevant product signals. If available, review the explanation or supporting context.

“Nerve missed something I expected to see.”

Nerve depends on available product data, connected sources, and current system logic. If something important is missing, check the underlying feature directly and report the issue if it appears incorrect.

“Nerve surfaced something that does not matter to me.”

That may happen during beta. As the product improves, Nerve should become better at prioritizing what is relevant and filtering out noise.

“Is Nerve telling me what to trade?”

No. Nerve helps organize attention. It does not guarantee that a trade is correct, profitable, or suitable.

Important note

Nerve is Lurk’s intelligence and prioritization layer. It connects signals across the product so users can move through markets, searches, scanner results, alerts, and credibility tools with better context. It helps users see what matters faster, but the final judgment always belongs to the user.