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

# Introduction

> **Status: LIVE** · Souless is deployed on Arc Mainnet and remains available on Arc Testnet.

Souless is launch infrastructure for narrative-native markets. It gives people and software agents a shared way to launch, discover, trade, support, and govern token markets built around an idea, story, or community.

Souless is not a bonding-curve launchpad. A launch creates a fixed-supply ERC-20 and a direct Uniswap V3 market. The official liquidity positions are permanently held by protocol lockers. The token remains permissionless: it can be held or traded outside the Souless app.

## Why narrative-native markets?

A narrative is the idea that gives a market context—such as an event, technology, culture, or emerging theme. Generic launch tools deploy assets. Souless also records why a market exists, connects related markets, and makes participation visible through community activity, staking, governance, and public history.

## Humans and agents

Humans are the primary launch participants today. The protocol is designed so agents can use the same market and identity primitives under explicit operator permissions. Agent launching, autonomous trading, and developer interfaces remain under development unless a page says otherwise.

```
Human creator ──→ Launch configuration ──→ Launch Guard opening
                                                   │
                                                   ▼
                                      ERC-20 + Uniswap V3 market
                                         │                    │
                                         ▼                    ▼
                              Permissionless trading    Community Mode
                                                            │
                                          ┌─────────────────┼──────────────┐
                                          ▼                 ▼              ▼
                                    Liquid staking    InfoFi rewards   Governance

Agent participation follows the same market path as capabilities are released.
```

## Design principles

* Fixed-supply, non-upgradeable launch tokens with no post-launch mint, tax, blacklist, or pause controls.
* Direct AMM liquidity; no bonding curve or graduation step.
* Permanent custody of official LP positions.
* Every distributable fee unit has exactly one destination.
* Community features sit outside the ERC-20, so markets do not depend on Souless to keep trading.
* Public economic rules, on-chain results, and claims; private anti-abuse details where disclosure would invite gaming.
* Mainnet and Testnet use separate deployments; always verify the selected network before signing.

{% hint style="warning" %}
Souless markets are experimental. Token prices can move quickly, transactions can fail, and losses are possible. Mainnet assets can carry real monetary value; Testnet assets have no intended monetary value.
{% endhint %}

Start with [How Souless works](/how-it-works.md), then use [Launch a token](/launching/launch-a-token.md) or the [developer overview](/developers/overview.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.souless.fun/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.