> For the complete documentation index, see [llms.txt](https://illuminance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://illuminance.gitbook.io/docs/why-illuminance-emerged/limitations-of-the-modern-financial-system/limitations-of-manual-trading.md).

# Limitations of Manual Trading

Traditional trading is commonly built around the idea of an individual who:

* monitors the market
* analyzes charts
* identifies entry and exit points
* evaluates news
* manages risk and emotions

This model is heavily dependent on the human factor:

* limited time
* limited speed of information processing
* psychological and emotional constraints
* inability to track multiple variables simultaneously

In the cryptocurrency market, these limitations are amplified:

* the market operates 24/7
* liquidity is distributed across multiple venues
* price discrepancies appear and disappear within seconds
* outcomes depend directly on reaction speed

***

As a result, manual trading becomes increasingly inefficient in environments where speed, scale, and continuous operation are critical.


---

# 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://illuminance.gitbook.io/docs/why-illuminance-emerged/limitations-of-the-modern-financial-system/limitations-of-manual-trading.md?ask=<question>&goal=<endgoal>
```

`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.