> 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/intelligence-and-identity/narratives.md). # Narrative intelligence A narrative is the idea or context around a market. Souless uses narratives to help users discover related markets and understand how attention and market activity cluster over time. Classification can consider public text, links, imagery, creator-supplied context, and market relationships. A token can have a primary narrative and additional relationships. The public record may expose labels, evidence, confidence or uncertainty, version, and update time where supported. ``` Token metadata + public signals │ ▼ Narrative classification │ ▼ Narrative pages │ ▼ Related markets, volume, and activity ``` Classification is discovery metadata, not an endorsement or guarantee. A label may be corrected or reclassified as evidence changes; historical versions should remain traceable. Souless publishes taxonomy, outputs, broad signal categories, uncertainty, and change history. It does not publish abuse-sensitive prompts, thresholds, provider internals, or exact classifier transformations. Optional namespace protection is separate from classification. It can quote a higher fee for a protected duplicate; the accepted on-chain policy determines its holder/protocol split. --- # 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/intelligence-and-identity/narratives.md?ask=&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.