> For the complete documentation index, see [llms.txt](https://prismnetwork.gitbook.io/prismnetwork-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prismnetwork.gitbook.io/prismnetwork-docs/3.-prism-network-solution/3.3-user-journey.md).

# 3.3 User Journey

* Discover Strategies: Users browse subscribable Flux strategy accounts on Prism Network, reviewing historical performance, risk ratings, and subscriber counts.
* Subscribe and Configure: Users select a strategy that matches their risk profile, set investment amount, risk preference (Conservative / Balanced / Aggressive), and strategy runtime.
* Automated Execution: The Flux strategy account runs automatically within the user's authorized parameters — no manual research of odds, cross-platform comparison, or 24/7 monitoring required.
* Results and Feedback: The system records every execution, delivering profit reports, transaction details, and strategy review analytics to users.


---

# 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://prismnetwork.gitbook.io/prismnetwork-docs/3.-prism-network-solution/3.3-user-journey.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.