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

# Design Goals

SMOL404 is built around a small number of principles.

#### Preserve the NFA

The BAP 578 layer remains fundamental.

SMOL404 does not reduce agents to fungible tokens.

Each NFA can retain its own identity, state, provenance and metadata.

The fungible token is the market layer around those agents.

#### Make liquidity native

Agent projects should be able to bootstrap a liquid market directly rather than depending exclusively on secondary NFT marketplaces.

#### Keep trading simple

Users should be able to interact with the fungible token in the same way they interact with other BEP 20 assets.

The relationship between token balances and NFAs should be handled automatically by the contract.

#### Remain composable

SMOL404 is designed to work with the existing BNB Chain ecosystem.

The fungible side can integrate with AMMs and standard token infrastructure while the agent side retains BAP 578 functionality.

#### Support real agent infrastructure

SMOL404 is designed around the idea that NFAs will increasingly use external agent infrastructure.

An NFA could use Binance Agent OS compatible tools for market data, wallet operations, payments, APIs and execution while SMOL404 handles ownership and liquidity.

Agent OS is not a technical dependency of SMOL404.

It represents the type of execution infrastructure that makes increasingly capable NFAs possible.

#### Build a standard for builders

SMOL404 is not intended to remain a single Proof of Concept.

The protocol and launchpad are designed to let other developers create liquid agent ecosystems using the same architecture.

###


---

# 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://smol404.gitbook.io/smol404-docs/smol404/design-goals.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.