> For the complete documentation index, see [llms.txt](https://safeforge.gitbook.io/safeforge-v1.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safeforge.gitbook.io/safeforge-v1.0/safeforge-overview/ecosystem.md).
# Ecosystem
## **Overview of the Ecosystem**
Safeforge creates a harmonious ecosystem where long-term investments meet dynamic portfolio optimisation. At the heart of this ecosystem are two core components: the Forger and the Storer, each playing a pivotal role in the continual growth and optimisation of the investment landscape within Safeforge.
## **Core Components: Forger and Storer**
### **Forger:**
* Forge ahead with creating a diversified portfolio, or add collateral to others' portfolios.
* Take on the challenge of outperforming the master portfolio and reap the rewards of a management fee over a certain period.
### **Storer:**
* By purchasing and holding $SAFF tokens, Storers invest in a token backed by a master portfolio designed to outperform $ETH. It’s crypto investment made simple and rewarding.
### **The $SAFF Token**
The $SAFF token is the cornerstone of the Safeforge project, embodying the long-term investment ethos that Safeforge promotes. By purchasing $SAFF, Storers are essentially buying into a master portfolio whose performance is continually optimised to ensure sustained growth.
The master portfolio’s strategy, grounded in Hierarchical Risk Parity (HRP), has historically outperformed $ETH. Even in scenarios where HRP might falter, the master portfolio can pivot to a 100% $ETH composition, ensuring its performance remains at par with $ETH at the very least.
---
# 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://safeforge.gitbook.io/safeforge-v1.0/safeforge-overview/ecosystem.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.