> For the complete documentation index, see [llms.txt](https://stewardship-fractalization.gitbook.io/project-planning/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stewardship-fractalization.gitbook.io/project-planning/system-architecture-design.md).

# System Architecture Design

**Stewardship dApp with Blockchain Smart Contracts, DAO Governance and Stewardship Tokens**

<figure><img src="/files/9npr0uXYuiAxHPx4lHay" alt=""><figcaption></figcaption></figure>

* The User interacts with a web/mobile dApp Frontend
* The Frontend makes calls to the Backend
* The Backend writes data to the Blockchain and reads blockchain state
* The Backend requests generated content from the Generative AI and ML module
* The Backend runs ML Agos and creates Stewardship Visualization Dashboards to display in the dApp

**The key integration points are:**

* The Backend integrating the blockchain for state management
* The Backend using Generative AI, ML Algo and blockchain data to create Stewardship insights, proposals and collaboration opportunities


---

# 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://stewardship-fractalization.gitbook.io/project-planning/system-architecture-design.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.