# Project documentation standards

<table><thead><tr><th width="138">Check ID</th><th>DEV_0003</th></tr></thead><tbody><tr><td>Category</td><td>Standards</td></tr><tr><td>Summary</td><td>This check will ensure that your model is documented to the minimum levels that you configure.</td></tr><tr><td>Options</td><td>See the table below for all available options. </td></tr><tr><td>Pass</td><td>The documentation property of the element is filled.</td></tr><tr><td>Fail</td><td>The documentation property of the element is not filled.</td></tr></tbody></table>

### Documentation Standards <a href="#id-73.mxom_checks.policycheck.groupbox1_fag_294_header" id="id-73.mxom_checks.policycheck.groupbox1_fag_294_header"></a>

<table><thead><tr><th width="182">Option Name</th><th>Details</th></tr></thead><tbody><tr><td>Complex Microflows</td><td>If TRUE, microflows with more than 25 actions must be documented.</td></tr><tr><td>Complex Pages</td><td>If TRUE, pages with more than 25 widgets must be documented.</td></tr><tr><td>Large Entities</td><td>If TRUE, entities with more than 10 attributes must be documented.</td></tr></tbody></table>


---

# 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://docs.bluestorm.io/checks/development/dev_0003.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.