> For the complete documentation index, see [llms.txt](https://docs.tryflox.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryflox.xyz/concepts/why.md). # Why Flox exists Three problems stack on top of each other in tokenized markets. Flox is built around the third; the first two are what it measures. ## Supply arrives before price reacts When tokens are minted, bridged in, or released from a vesting cliff, someone eventually has to buy them. If that incoming supply is larger than the order book can absorb, the price moves. By the time the chart shows it, the move already happened. Most tools watch price. Flox watches the supply that is about to hit price — issuance, redemptions, tokens moving onto sell venues, and scheduled unlocks weighted by how soon they land. ## Most agents only ever say yes An agent judged on activity finds a reason to act. Ask a language model whether a trade looks good and it will usually produce a confident-sounding case, because agreeing is what the training rewards. An agent that cannot refuse is not managing risk — it is rationalizing. Flox refuses. Its verdict comes from a rule, not a model, and the rule returns `REFUSE` whenever the numbers say so, regardless of how the request was framed. ## Track records are editable A screenshot of a good call proves nothing. If the losing calls can be quietly deleted, every published record is a selection of the wins — it tells you nothing about the process that produced them. This is the problem Flox is actually built around. Every call it makes, including every refusal, is committed to a hash chain and anchored on Robinhood Chain. The refusals are the point: anyone can publish wins, but a record you can't edit is the only one worth trusting. --- # 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://docs.tryflox.xyz/concepts/why.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.