> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/build-security/build-attestations.md).
# Build Security User Interface
The **Build Security page** offers a thorough overview of your project's build process integrity.
{% hint style="info" %}
You can reach the **Build Security page** by selecting **Build Security** in the **Navigation Bar**.
{% endhint %}
The top chart shows the timeline frequency for the number of Valid, Invalid, and Unverifiable
The table below displays attestations filtered by your selections.
Clicking on the  icon of each attestation will allow you to download the attestation.
Clicking on the  icon of every attestation will open a slide with detailed information of the attestation.
In the detail slide you can view details about the **running environment context** of the build, **details** about the **artifact produced** in that build as well as a **link to the build**.
{% hint style="info" %}
Please visit the [Build Security](/xygeni-products/build-security.md) documentation for further information.
{% endhint %}
---
# 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.xygeni.io/xygeni-products/build-security/build-attestations.md?ask=&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.
