> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/review-collaboration/locking-a-version-and-handing-off-to-programming-pm.md).

# Locking a version & handing off to programming

The version-status control sits next to the project name in the document header, e.g. **Draft · Editable working copy**. In this state, edits and tracked changes accumulate into what will become the next version.

**Hand off to Programming** freezes the current state as a numbered version (e.g. **V1**) and passes it to the SP. The dialog tells you how many approved changes will be sent, how many pending ones stay in the working copy, and how many client threads are still open — and lets you choose **Send approved only** or **Send all changes**.

![Handing off: the header control, the hand-off dialog with its send-approved-only or send-all choice, the cut running, and the V1 handed off confirmation](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FBXs8QXWrgGZ6ug8xTmWj%2Fpm-handoff-v2.gif?alt=media)

{% hint style="info" %}
A locked version becomes a read-only snapshot — useful for seeing exactly what changed from the prior version — while further live editing and commenting happens in a new working copy. Comments cannot be added on a read-only snapshot; the page will offer **Open Live to comment**.
{% endhint %}


---

# 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://help.metaforms.ai/review-collaboration/locking-a-version-and-handing-off-to-programming-pm.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.