> For the complete documentation index, see [llms.txt](https://morrow.gitbook.io/morrow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://morrow.gitbook.io/morrow/04-the-protocol.md). # 04 The Protocol ### Architecture MORROW separates the portfolio itself from the interface used to interact with it. ``` Creator ↓Strategy ↓FUND ↓Capital ↓Underlying Assets ``` The FUND is the core portfolio primitive. The application provides the interface. The blockchain provides the settlement layer. *** ### Portfolio Management A Stack can maintain a defined allocation across multiple assets. For example: **ETH 50% / BTC 30% / USDC 20%** As prices move, the actual portfolio weights may drift. MORROW can support rebalancing mechanisms that bring the portfolio back toward its target allocation. *** ### On-Chain The important portfolio information lives on-chain. This allows users and external applications to verify: * holdings * allocations * transactions * portfolio state * contract interactions Rather than relying entirely on a centralized database, the underlying state can be independently verified. --- # 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://morrow.gitbook.io/morrow/04-the-protocol.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.