> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/qna/interactive-q-and-a-inspection.md).
# Interactive Q\&A inspection
## Rationale
With Clause9, you have almost limitless possibilities to configure interactions and clauses. In fact, you can easily go so far that you scratch your head wondering why a certain clause/card/question is currently having a certain behaviour.
Within Design Q\&A, we therefore offer a possibility to inspect the current state of each condition of a card/question/predefined answer and change-set.
## Functionality
To start inspecting a Q\&A, check the “Inspect” checkbox in the lower right corner. You will then see something similar to the following:
Each card, question, predefine and change-set will have a circle in front of it:
{% hint style="info" %}
A predefine can even show two circles next to each other, when it contains a *switch condition* that defines when the predefine will get selected
{% endhint %}
When you want to check why a certain condition is (not) met, you can click on the red or green circle. For example, the following question happens to have a red circle, because both of its conditions must be met, while in fact only the upper condition is met.
When you change an answer, you will see that the red/green lights will immediately change to reflect the (possibly updated) state of the document. This way, you really simulate what happens to your document.
---
# 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://help.clause9.com/qna/interactive-q-and-a-inspection.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.
