> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/5-introducing-fanpass/5.5-the-architecture.md). # 5.5 The Architecture FanPass is built across three layers. FanPass is the product layer, consist ing of the identity a fan carries. FanScore is the reputation layer, a computation system that turns verified activity into reputation, user cohorts, and eligibility. The FanPass SDK is the integration layer, which is the toolset that allows clubs, brands, apps, and developers to embed identity, scoring, and consent into their own products without building the full identity stack themselves. Every fan receives an embedded identity and asset wallet, created automatically and designed to require no technical crypto knowledge. The identity wallet holds reputation, credentials, attestations, permissions, and data-sharing controls. The asset wallet holds value, including tokens and digital assets. The wallet design deliberately separates identity from assets because a fan’s identity should not be priced, traded, or lost in the same way as a token or collectible. Data follows the same principle. Sensitive personal records remain off-chain. On-chain records are used for proofs, attestations, consent records, and verification anchors. Instead of unrestricted access to raw user data, partners receive permissioned data views – scope slices of context that the fan has explicitly agreed to share and can revoke at any time. The long-term direction is an open football identity protocol. FanPass is the first product and adoption layer for that protocol, turning portable identity and reputation into infrastructure for the football ecosystem to build on. --- # 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.onefootballclub.com/5-introducing-fanpass/5.5-the-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.