> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/pulse-predictions/from-signal-to-trade.md).
# From Signal to Trade
**A short checklist for turning a Pulse signal into an executed position without skipping the parts that matter.**
Pulse is fast — fast is good for spotting, dangerous for acting. The flow below is the workflow used by experienced predictors. Take the few seconds.
## The five-step flow
1. **Spot the signal in Pulse.** A row catches your eye — sudden volume in Active, a fresh row in New that matches a thesis, a late-edge in Closing Soon.
2. **Click the row to open the market page.** Don't trust the Pulse summary blindly — the market page shows the chart, the order book, the outcomes, and the resolution methodology.
3. **Read the order book.** Is the price you would pay supported by real depth? A 51% Yes with $2 in the book is not a 51% market — it's a $2 market.
4. **Size the order.** Pick an amount your wallet can absorb cleanly. Default presets `0.01 / 0.05 / 0.1 / 1` are fine for testing; use the typed input for real positions.
5. **Pick a speed.** Slow is the default. Switch to Fast or Turbo only when latency matters more than fee economy. See [Speed Presets](/graphdex-docs/trading-predictions/speed-presets.md).
Hit Up or Down.
## When to skip step 2 and trade from Pulse directly
The Pulse row's Up/Down buttons use your existing presets and submit straight to the same execution path as the market page. Skipping the click into the market is reasonable when:
* You already opened that market today and reviewed depth.
* The amount is small enough that depth doesn't matter.
* The market is a recurring short-window cycle you've traded before.
In every other case, the click into the market page is two seconds well spent.
## When to NOT trade a Pulse signal
* The market is in **Closing Soon** with very thin recent volume — you may be the only buyer, and your fill price will be ugly. See [Execution Risks](/graphdex-docs/trading-predictions/execution-risks.md).
* Volume in the Active lane spiked once and then went flat — it was a single big order, not real flow.
* The implied probability is at an extreme (97% Yes) — the upside is small and the resolution risk is asymmetric.
## Pre-trade checklist
* [ ] You opened the market page or you have already reviewed depth on this market today.
* [ ] The amount fits your position-sizing rules.
* [ ] You picked the right Speed preset for this market's urgency.
* [ ] You are okay with the worst-case scenario — wrong side, slow resolution, partial fill.
{% hint style="warning" %}
Pulse makes it easy to fire orders. That is the feature, and it is also the danger. A bad trade fires just as fast as a good one.
{% endhint %}
## FAQs
Can I cancel an order I placed by mistake from Pulse?
Limit orders that haven't filled can be cancelled from [Wallet → My Orders](/graphdex-docs/wallet-predictions/wallet-overview.md). Market orders that have already filled cannot be undone — they are an executed trade.
What if my fill is much worse than the row showed?
The Pulse row shows the current top-of-book; your fill depends on depth available at submit time. Use Limit orders (see [Limit Orders](/graphdex-docs/trading-predictions/limit-orders.md)) when you need price certainty.
Do I need to read every market page before trading?
No, but you should know which markets you trust to trade without re-checking. Build that list — and don't extend it under time pressure.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://graphdex-1.gitbook.io/graphdex-docs/pulse-predictions/from-signal-to-trade.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.