> For the complete documentation index, see [llms.txt](https://docs.census.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.census.de/using-census-data/data-in-the-census-records/postclassical-work-records/description.md).

# Description

Under **Description**, the Postclassical Work is described in more detail with information, for example, concerning the medium, method of representation, and dimensions. These fields are described below.

**Dimensions:** Here, you will find measurements of the monument. In **Measurements,** these are given as a free text (e.g., height: 203 cm). 

**Watermark**: if the Postclassical Work is a work on paper with a watermark, information about the watermark is given here. 

**Type of Work**: this field provides information on the type of work, such as book of drawings.

Depending on whether the type of work is textual or visual, further specifications are given under **Media (textual)** (for example, inventory, itinerary, or letter) or **Media (visual)** (for example, drawing or print)**.**


---

# 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.census.de/using-census-data/data-in-the-census-records/postclassical-work-records/description.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.