> 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/infrastructure.md). # How it works From launch configuration to wallet execution, verification and public discovery A launch moves through configuration, transaction preparation, wallet execution and public verification. Programmable records these steps separately so a prepared request, a confirmed transaction and an indexed coin have clear meanings. ## Module Mode The builder reads the active engine and module catalog, validates the selected configuration and prepares the launch transaction. The native launcher creates the coin and records its identity, engine, creator and module configuration. The coin's runtime applies its bonding curve and selected module behavior. An indexer verifies the canonical launcher events and getters against the published engine release. It does not require a Custom Launch stamp for a Module Mode coin. The [Module Mode indexing guide](/docs/developers/module-mode-indexing.md) defines this source contract. ## Custom Launch The client packages one exact source and deployment plan. The chain-specific API checks the package, permissions, economics and execution evidence required by its profile. A returned wallet handoff binds the transaction to the intended controller, chain and launch. The API key cannot sign for that wallet. The controller reviews and signs the authorized transaction. The appropriate Launch Stamp Router records the deployed project and its components. Source verification, transaction finality and public indexing each have their own result. The [API quickstart](/docs/developers/custom-launch-quickstart.md) explains the sequence and how to recover from a rejected or incomplete request. ## Classic on Ethereum Classic creates a fixed supply token, initializes its ETH pool, locks the initial liquidity position and completes the initial buy through the selected launcher. The deployed version determines its creator fees, rewards and custody. Read the [Classic reference](/docs/tokens/classic.md) for the exact model. ## Public discovery The website publishes verified launch identities and adds market data when available. A coin is identified by its chain and token address. Its source record explains which launcher or Router created it and which version-specific verifier applies. Price, liquidity, chart data and trading support are separate from launch identity. A missing chart does not remove a valid launch. A launch stamp does not prove that another trading application supports the hook. [Index launches](/docs/developers/indexing.md) describes the common ingestion rules and links to each source. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://programmable.market/docs/infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.