> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/getting-started/first-generation-workflow.md).

# First generation workflow

A guided walkthrough that takes you from an empty workspace to a configured, deployed project.

The canonical generation path is:

`request → validate → reserve → dispatch → callback merge → completed/failed → settle/refund`

## Before dispatch

* Validate authentication and tenant ownership.
* Validate input fields and any public URL.
* Resolve the required credit amount in atomic units.
* Create or reuse the idempotent operation record.
* Reserve credits.

## During provider execution

Persist the provider job identity and treat callbacks as merge events, not replacements. A callback may contain only one track or an earlier stage than a callback already processed.

## Terminal handling

* **Completed:** verify final output, then settle the reservation once.
* **Failed/cancelled:** release/refund the reservation once.
* **Ledger transition failure:** retry the financial transition without redispatching generation.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/getting-started/first-generation-workflow.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.