> For the complete documentation index, see [llms.txt](https://whitepaperlist.gitbook.io/baby-penguin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaperlist.gitbook.io/baby-penguin/mission-and-vision.md).

# Mission & Vision

### Mission

PenguinSwap’s mission is to provide accessible financial opportunities for the (crypto) masses through transparency, security, and support.&#x20;

### Vision

To decentralize traditional finance to create a fair global economy through a sustainable, community-driven DAO.&#x20;

### Values

**Accessibility:** We create tools for users to leverage DeFi opportunities, regardless of background, wealth, or experience.

**Transparency:** We build together through community-driven governance and transparent processes that ensure our users understand our collective goals.

**Security:** Our highest priority is to maximize the safety of our users' funds, our partner projects, and our community. Check out the Security section of this documentation for more information.


---

# 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://whitepaperlist.gitbook.io/baby-penguin/mission-and-vision.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.
