> For the complete documentation index, see [llms.txt](https://peeps-2.gitbook.io/peeps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/technical/architecture.md).

# architecture

The final PEEPS architecture should be documented from deployed, verified source code.

## Proposed contract modules

```
PEEPS Web App
   │
   ├── Launchpad Factory / Registry
   │      ├── Token Contract
   │      ├── Curve or Launch Contract
   │      └── Fee Share Contract
   │
   ├── Trading Router
   ├── Graduation Manager
   ├── DEX Pool / Position
   ├── Fee Distributor
   └── MBI / Metadata Registry
```

## Frontend

The web application reads chain state, prepares transactions and displays indexed activity. It should not be treated as the source of truth where it conflicts with verified contract state.

## Smart contracts

Smart contracts determine token creation, trading, fees, graduation and claims. Publish verified source code for all production contracts.

## Indexing

An indexer may be used for search, rankings, charts and activity feeds. Indexer downtime may affect display without affecting the underlying blockchain.

## Storage

Images and metadata may be stored through decentralized storage, centralized infrastructure or both. The final storage method and mutability should be disclosed.


---

# 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://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/technical/architecture.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.