# Digital Platforms

EAPES operates a set of digital platforms designed to support access, interaction, and participation within the EAPES ecosystem. These platforms consist primarily of a public-facing website and a decentralized application (dApp), each serving a distinct role within the ecosystem architecture.

The official website functions as an informational interface, providing structured and up-to-date content related to the project, its ecosystem components, and ongoing developments. Content is updated progressively to reflect platform evolution without reliance on fixed timelines or prescriptive roadmaps.

The decentralized application (dApp) serves as the functional interaction layer of the ecosystem. It enables on-chain interaction with EAPES digital assets and applications through access-based and participation-oriented mechanisms defined at the application level.

Through the dApp, users may view and manage their digital assets, access application-specific features, and interact with ecosystem functionalities designed around participation and usage rather than financial activity. The platform also provides visibility into interaction status and participation indicators relevant to supported applications.

Together, these digital platforms provide a unified and consistent user experience, enabling structured interaction across the EAPES ecosystem while remaining aligned with its non-financial, utility-driven design principles.


---

# Agent Instructions: 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:

```
GET https://wp.eapes.com/whitepaper/project-initiatives/digital-platforms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
