> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/cadd/cloud-cadd.md).

# Revision Cloud

A **Revision Cloud** is a closed scalloped boundary used to mark a region of a drawing that has been revised. Standard drafting convention: when you issue a revised drawing, every change since the last issue is enclosed in a cloud and labeled with a triangle revision marker matching an entry in the title block's revision table.

## Drawing the cloud

To draw, sketch the boundary of the revised region — the cloud follows the boundary as a series of small connected arcs. The cloud is closed automatically when you finish.

## Style

**Thickness:** Cloud line weight. Match to your project's revision-cloud convention (typically heavier than dimension lines, lighter than cut lines).

**Color:** Cloud color. Often red on screen for visibility, then plotted as black or as the project's revision color.

**Level:** Layer assignment. Route to a "Revisions" level that matches your project's revision conventions.

## Placement

After drawing, drag the cloud's outline handles to refine the boundary. Add a Pin or Note inside or beside the cloud with the revision number to complete the marker — clouds without revision numbers are ambiguous.

## Notes

Each issued revision typically gets its own Revision Cloud level (or its own assigned color), so revisions from issue 1 vs issue 2 can be visually distinguished. After a revision is issued, it's standard practice to leave the previous issue's clouds visible (so reviewers can see the revision history) and add new clouds only for changes since.

Revision clouds aren't dimensioned — they're a visual marker only. Don't try to use them for region boundaries that need precise definition; for that, draw a Container or a Line with the right vertices.


---

# 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://docs.openbrim.org/templates/cadd/cloud-cadd.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.