> For the complete documentation index, see [llms.txt](https://docs.fortunaway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortunaway.com/core-products/core-product-architecture.md).
# Core Product Architecture
An overview of FortunaWay’s identity-driven product architecture and core system flows.
{% hint style="success" %}
FortunaWay’s core product architecture is organized into three connected flows: Identity Entry, Cultural Participation Execution, and Credential, Reputation & Membership Settlement.
Users enter through a wallet and create a Fortuna ID profile. The Quest Engine reads identity context from Fortuna ID to determine campaign access, eligibility rules, and participation conditions.
When users complete quests or campaigns, the Verification Engine validates their actions through API checks, manual review, partner proof, or other verification methods. Once verified, the Reward Dispatcher writes the verified output into Fortuna Points and Fortuna Credentials.
These records are then processed by the Reputation Engine to generate trust signals. The Role Controller uses those signals to manage membership states and access rules, while the Dashboard aggregates identity, points, credentials, reputation, and membership status into a user-facing interface.
{% endhint %}
---
# 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.fortunaway.com/core-products/core-product-architecture.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.
