> 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/public-record.md). # Public record Souless builds a durable history around markets and participants. ## On-chain record Launch ID, creator and governance wallet, token, canonical pool, official LP positions, referral terms, Community Mode registration, launch-time Community policy, fee movements, stake custody, governance actions, finalized epoch roots, and claims can be verified from contracts and events. ## Souless-indexed record Descriptions, images, narrative classifications, charts, public-profile presentation, portfolio/activity history, external-account attribution, reputation summaries, Mindshare rankings and social-feed context, contributor badges, and reconstructed activity are indexed for usability. They can be unavailable, re-indexed, moderated, or corrected without changing chain ownership. Public profiles are scoped to the active Souless network and can combine registered identity, indexed wallet/portfolio history, launches, holdings, staking/community activity, and other supported public sections. A profile view is a read model, not a new custody or ownership layer. Mindshare likewise combines indexed X activity, market associations, derived ranking/score data, verified social-to-wallet attribution, and on-chain-informed badges. Feed visibility and Mindshare presentation are not equivalent to finalized InfoFi reward eligibility; finalized claims remain anchored to the relevant epoch record. Every public page should distinguish canonical chain state from indexed or derived data. Corrections should preserve source, timestamp, network, and classification/calculation version rather than silently rewriting history. --- # 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/public-record.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.