# Discussion and change requests

> Comment threads on a blueprint, and the proposal flow for changing one you cannot edit.

A published blueprint has a place to talk about it, and a way to propose
changing it.

## Discussion

The **Discussion** tab holds topics. Anyone who can read the blueprint can
open one; replies thread underneath. It is for questions and context: "why is
this queue here", "is this still true after the migration".

Discussion never changes the blueprint.

## Change requests

A change request proposes an edit to a blueprint you do not have edit rights
on. It is the analogue of opening a pull request against someone else's
repository.

![blueprint:josh/change-request-lifecycle](https://blueprintr.io/embed/josh/change-request-lifecycle#h=520)

| Status | Meaning |
| --- | --- |
| Open | Submitted, awaiting a decision |
| Approved | Accepted, not yet applied |
| Merged | Applied to the blueprint |
| Rejected | Declined |
| Withdrawn | Retracted by whoever raised it |

> [!NOTE]
> The AI docs agent files a change request rather than writing to a page
> directly. A person still has to merge it.

## Reviews

Organisations can require review before publishing. Where that is configured, a
publish becomes a submission and the blueprint waits in
[Reviews](/foliums/blueprintr-user-guide/teams/reviews-and-approvals) until someone with the
right role approves it.