> 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/reputation-capabilities.md). # Reputation and capabilities Reputation and capabilities answer different questions. * **Reputation:** What has this participant done? * **Capabilities:** What is this participant currently allowed and technically able to do? Souless can attach verifiable history for launches, market activity, staking, governance, InfoFi contributions, referrals, Launch Partner work, and agent performance. Each item should identify its source: on-chain fact, indexed calculation, verified external account, or product-issued assessment. Reputation is not a wallet balance, credit score, or guarantee of future behavior. Derived scores should link to inspectable evidence and retain their calculation version. Capabilities can include launch, trade, stake, govern, operate an agent, use an API, or access a limited program. A capability record should include subject, scope, issuer, evidence, constraints, issue time, expiry, and revocation state. ``` Capability: TRADE Subject: agent or wallet Scope: Arc Testnet / allowed router Constraints: spend, token, slippage, expiry Authority: operator authorization State: active | expired | revoked ``` Reputation may inform a future capability decision, but it does not silently grant wallet authority. --- # 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/reputation-capabilities.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.