# Drafts

### What Appears Here

Each row represents a prompt with at least one draft. The page shows:

| Column        | Meaning                                                         |
| ------------- | --------------------------------------------------------------- |
| Slug + folder | Prompt identity and location, with a direct link to the editor. |
| Live label    | Current production version.                                     |
| Draft label   | Current in-progress version.                                    |
| Author        | Latest person to change the draft.                              |
| Updated       | Last draft change time.                                         |

Clicking a row jumps to the editor with that draft loaded.

### Why Drafts Exist

A draft version is the bridge between "I'm testing this out." and "This is live." It lets you:

* Save latest checkpoint without changing what production serves.
* Stage a version visible to `pv_test_` keys.
* Hand a prompt to a teammate without disturbing live traffic.

Drafts are mutable during an iteration, so repeated draft saves do not clutter version history with unnecessary labels.

### Resolving a Draft

| Action                  | Effect                                      |
| ----------------------- | ------------------------------------------- |
| Promote to live/staging | The draft becomes the live/staging version. |
| Delete the draft        | The draft is removed.                       |

### Activity Entries

Draft saves appear in Activity with the message from the save modal.


---

# Agent Instructions: 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:

```
GET https://aiso.gitbook.io/promptvault/documentation/dashboard/images-and-media.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.