> For the complete documentation index, see [llms.txt](https://docs.harvest.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harvest.finance/how-it-works/harvest-contracts/strategies.md). # Strategies Strategies are a key component in the Harvest machinery that define the ways in which vault funds can be utilized with 3rd party protocols to generate yield. Because strategies are directly moving user's tokens, they are strictly scrutinized and tested prior to their deployment. Strategies become associated with a vault through a 'timelock' mechanism, meaning that the change is first announced, then a period of time must elapse (currently 12 hours) before the change is made official and the new strategy can access funds. While the specifics of each strategy may differ based on the farming opportunity being taken advantage of, all strategies use a function called `doHardWork()` to compound their tokens with the following steps: 1. Collect reward tokens accumulated by the farmed tokens. 2. Liquidate the rewards into the farming token. 3. Reutilize the new tokens in the farming opportunity. > During liquidation, a performance fee (8-15%) is taken from the rewards and used to buy FARM on the market, which is then distributed to those who have staked FARM in Profitsharing. Whenever `doHardWork()` is called, the price of each share of the associated vault increases. Most vaults are harvested every 12-48 hours, depending on the liquidity of their associated token. If you notice that a vault has failed to harvest in more than 48 hours, please let a mod know in the Harvest community discord server. The following is an example of what this 'harvest' transaction via `doHardWork()` looks like: --- # 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.harvest.finance/how-it-works/harvest-contracts/strategies.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.