# CVEI III

As a final note - CVEI is a convention for which order to pick for a typical task.

The advantage of using these particular orders isn't as much functional as it is conventional. In fact, the order you assign is just an integer value.

```python
import pyblish.api

class MyValidator(pyblish.api.ContextPlugin):
  order = pyblish.api.ValidatorOrder  # == 1
```

The benefits of sticking with CVEI are two-fold.

1. The ordering provides a common language with which to discuss publishing.
2. And under the hood, they allow Pyblish to make assumptions about your plug-ins, such as when to abort.

This language fuels our community, and the assumptions are what fuels the mechanics of Pyblish.

With this in mind, saving plug-ins are typically named after what they are.

```yaml
plugins
├── collect_my_assets.py
├── validate_normals.py
├── extract_alembic.py
└── integrate_ftrack.py
```


---

# 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://learn.pyblish.com/13-cvei-iii.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.