> 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/developers/architecture-and-runtime/publishing-and-release-governance.md).

# Publishing & release governance

## Definition of done

Before a technical release is documented as complete:

* mutating operations document tenant-scoped idempotency;
* internal operation IDs remain primary over provider job IDs;
* credit reservation and terminal settle/release behavior is current;
* callback merge, duplicate replay and out-of-order behavior is current;
* public-URL validation requirements are current where upload URLs are accepted;
* subscription snapshots and decimals fields match implementation;
* wallet/transaction intent boundaries are documented;
* account/provider credential storage and secret-return rules are documented;
* dashboard routes and Settings provider capabilities match implementation;
* changelog contains behavior and migration impact;
* economic claims have canonical sources and approval;
* public pages use approved brand terminology and visual tokens;
* GitBook is updated and merged in the same release pass as the source workspace.

Documentation is part of the product release, not an after-the-fact summary.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/developers/architecture-and-runtime/publishing-and-release-governance.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 `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.