> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-an-attestation-cycle.md).
# Managing an Attestation Cycle
Acknowledge that you are aware of new or updated documentation before it is published.
The **attestation cycle** is an awareness step that ensures key stakeholders are informed about new or updated documentation. It helps confirm that the appropriate parties are aware of changes **before** the documentation is published.
{% hint style="warning" %}
Attestation is **optional** and can only be triggered automatically if an approval cycle is configured beforehand. Without an approval cycle in place, the attestation cycle **will not run**.
{% endhint %}
***
## How to Configure & Manage an Attestation Cycle
In **Phase 1**, governance cycle management is not yet available in the platform. All setup and administration must be performed in EPC.
For detailed instructions on managing attestation cycles in EPC, refer to the following topic:
* [Attestation Cycle](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/7-6-attestation)
***
## Completing Attestation Tasks
While you cannot manage attestation cycles in the platform, you can complete attestation tasks assigned to you. See the guides below to get started:
---
# 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://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-an-attestation-cycle.md?ask=&goal=
```
`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.
.png?alt=media&token=eb58f3cb-9a8a-4694-b49f-4ee337616143){kind=link}
