> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/requirements.md).

# Requirements

Violet's <mark style="color:purple;">**Requirements**</mark> module activates your requirements and verifications with real data - from component specs or test results to real-time outputs from native [Scripts](/features/scripts.md).

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FJW3nKdFwHBv6f7G8DiBw%2FRequirements.png?alt=media&amp;token=a2c949a6-0163-41fe-97e0-6ce46109fec5" alt=""><figcaption></figcaption></figure>

Violet requirements are **math aware** and **data aware.** This means you can:

* Define a requirement mathematically, including its **operator** and **value**
* Relate this value to the actual **property** of the system or component the requirement describes, such as a mass or a performance spec
* Link actual **verifications** to their corresponding requirements, which automatically surfaces the verification owner, activity and result

With this framework, Violet enables a **real-time traceability matrix** with no extra reporting.

### Need to migrate existing requirements?

You can also ingest requirements from tools like [Jama](/apps/j/jama.md), [Flow](/apps/f/flow.md), [Valispace](/apps/v/valispace.md), [DOORS](/apps/d/doors.md), [Innoslate (Coming Soon)](/apps/i/innoslate-coming-soon.md), [Visure (Coming Soon)](/apps/v/visure-coming-soon.md) and [Polarion (Coming Soon)](/apps/p/polarion-coming-soon.md). Head to [Import & export](/features/requirements/import-and-export.md) to learn more.

### Getting started

Head to [Getting started](/features/requirements/getting-started.md) for instructions on creating, managing and viewing requirements. Or navigate to [Best practices](/features/requirements/best-practices.md) for recommendations on how to best use Violet's Requirement functionality for your team.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.violetlabs.com/features/requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.