> 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/networks-and-reference/glossary.md).

# Glossary

**Agent** — Software participant acting through an operator-defined wallet and permissions.

**Capability** — A scoped permission or supported ability, such as trade or stake.

**Canonical pool** — The Uniswap V3 pool registered for a Souless Launch ID.

**Community Mode** — Optional external staking, rewards, InfoFi, Mindshare, and governance modules.

**Community Mode governance** — Bounded control over future Community policy; not ownership of the ERC-20.

**Creator** — Account that initiates and is permanently attributed to a launch.

**Epoch** — A fixed reward-accounting period followed by attribution and finalization.

**FDV** — Current token price multiplied by fixed total supply.

**Genesis Community policy** — The initial Creator/Community allocation and Staking/InfoFi split selected for a Community-enabled launch. It becomes active from the market's first reward epoch, before any later governance policy.

**Hosted external token** — A token that was not launched by Souless but is deliberately listed/hosted by Souless for supported product services. Mindshare/InfoFi support for hosted external tokens is a planned V2 capability, not a V1 assumption.

**InfoFi** — The community contribution qualification, epoch allocation, and claim system that turns attributable useful participation into fee-funded USDC rewards.

**Launch** — Deployment and registration of a token and its canonical market.

**Launch Guard** — Short commitment and batch-settlement phase before normal trading.

**Launch ID** — Unique identifier linking creator, token, pool, LP positions, and launch terms.

**Launch Partner** — Participant in a protocol-wide, fixed-slot campaign.

**Market** — The token, canonical pool, liquidity, price activity, and associated record.

**Mindshare** — Souless' indexed discovery and measurement layer for market attention, contributor activity, and associated social context. Mindshare presentation is distinct from InfoFi reward eligibility and finalization.

**Narrative** — The idea, theme, event, or context around a market.

**Opening** — Launch Guard’s 60-second public commitment window in V1.

**Operator** — Human or organization that authorizes and remains responsible for an agent.

**Referral** — Signed launch-time attribution with limited fee eligibility.

**Reputation** — Evidence-backed history of a participant’s actions.

**sTOKEN** — Canonical transferable 1:1 receipt for a token deposited in Community Vault.

**Slippage** — Difference between expected execution and the user’s permitted minimum output.

**Token Protection** — Temporary protection for a qualified Souless launch's exact normalized name + ticker pair. Selecting it at launch submits a request; protection is active only after qualification and on-chain activation.


---

# 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/networks-and-reference/glossary.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.