> For the complete documentation index, see [llms.txt](https://programmable.market/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://programmable.market/docs/developers/machine-readable/trust.md).

# Verification and risk

What launch checks establish and what remains to verify

A source check, simulation and confirmed transaction answer different questions. Use the result relevant to the decision you are making.

| Check            | What it establishes                                                                    |
| ---------------- | -------------------------------------------------------------------------------------- |
| Source and build | The submitted source and compiler inputs match the verified artifacts                  |
| Simulation       | The exact transaction can execute in the tested state                                  |
| Finality         | The transaction has reached the chain confirmation level required by its launch source |
| Launch record    | The token came from the recorded Programmable launcher or Router                       |
| Market data      | The price, liquidity or activity observed by that provider                             |

Changed source, settings or transaction bytes may need fresh checks. Simulation does not cover every future contract interaction. A valid launch record does not guarantee liquidity, sellability or terminal support.

## Wallet authority

An API key allows specific API requests. It cannot sign for a wallet. The controller reviews the authorized transaction's network, destination, value and effects before signing.

## Security review

The public Programmable contracts have not undergone an external audit or public security contest. Internal review, tests and reproducible builds do not replace an independent audit. A launch stamp is a record of origin, not a security endorsement.

Report vulnerabilities through the affected repository's private security reporting channel. Keep credentials, signatures and unpublished exploit details out of public issues.


---

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

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

```
GET https://programmable.market/docs/developers/machine-readable/trust.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 `build a script that syncs our docs to a CMS` 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.