> For the complete documentation index, see [llms.txt](https://docs.canhav.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.canhav.com/token-launch/deploy-paths.md).

# Deploy paths

**Available now** on Robinhood Chain Testnet.

There are two ways to launch a token through `/launch`. Both use TokenFactory v4. They differ in what `journeyHash` means and how the token page labels the launch.

## Quick deploy (no design record)

Use `/launch` without a design id.

1. You fill the launch form (name, ticker, supply, journey, optional vesting).
2. The launch commits a classic **JourneyDoc** hash as `journeyHash` (and stores the journey blob).
3. On `/launch/t/[address]`, when that hash resolves in the journeys table, the page shows:

**Quick deploy, no design record**

That label means this token was launched without a published Projects token design snapshot. There is no ideation design page to attach by default.

## Design deploy

Use `/launch?design=<id>` from a **published** token design (or an equivalent entry point that passes the design id).

1. The form prefills from the design (name, ticker, supply, and team vesting months where applicable).
2. Step 2 becomes a design commitment card instead of a free-form journey editor.
3. The launch commits the design **snapshot hash** as `journeyHash`. The journeys POST for a classic JourneyDoc is skipped.
4. On success, attach-deploy links the on-chain token to the design (server re-verifies via indexer `journeyHash` match).
5. On `/launch/t/[address]`, when that hash resolves in `ideation_snapshots`, the page shows **Design committed on-chain** and links to the design.

Publishing a design does not deploy. Deploying is a separate wallet transaction.

## How journeyHash discriminates the path

| Path          | What journeyHash is                      | Where it resolves              |
| ------------- | ---------------------------------------- | ------------------------------ |
| Quick deploy  | Hash of the v1 JourneyDoc                | `launchpad.journeys`           |
| Design deploy | Content-addressed ideation snapshot hash | `launchpad.ideation_snapshots` |

The table the hash resolves in is the path discriminator. No separate on-chain flag is required.

If the hash resolves in neither table, the token page shows that there is no design record (and no verified journey blob).

## Why the Quick deploy label exists

Readers should not confuse a free-form journey launch with a published, snapshotted token design. The label makes the missing design record visible instead of silent.

## Related

* [Create a token](/token-launch/create-a-token.md)
* [Journey and credibility](/token-launch/journey-and-credibility.md)
* [Public pages](/public-pages/public-pages.md)
* [Token track](/token-track-ideation/token-track.md)
* [Enforced versus stated](/token-track-ideation/enforced-vs-stated.md)


---

# 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://docs.canhav.com/token-launch/deploy-paths.md?ask=<question>&goal=<endgoal>
```

`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.