> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/colibri/overview/about-colibri/dictionary-of-colibri-terms.md).
# Dictionary of Colibri Terms
| Term | Definition |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Scenario Table** | The **table** (like the MEL) in which the exercise is built |
| **Chapter** | A **tab to organise** sections of the exercise |
| **Serial** | Sits within a chapter to split into further **sections** |
| **Row** | A row within the scenario table which contains **exercise content** |
| **Step** | The **exercise content** (like an inject) that sits within a row |
| **Question** | A type of step that requires **player interaction** |
| **Narrative** | A type of step that requires **no player action** |
| **Action** | A type of step that can be **participatory or automatic** |
| **Narrative Block** | An expanded step which contains **narrative content** (and a final question) |
| **Archetype** | A way of defining different types of personas and the roles they fulfill in exercises
(Boss, Sidekick, Antagonist, Subordinate, Colleague, Expert, Customer, Neutral)
|
| **Branching** | Splitting the story into **different paths** based on player choice |
| **Smartwords** | Dynamic **placeholders that act like variables**, automatically pulling in data |
| **Self-paced exercise** | An exercise that runs based on **player interaction** instead of a facilitator |
| **Decision point** | A moment where players must make a choice that influences the scenario
|
| **Data point** | Attached to a question, a way of collecting data about **player responses** |
| **Inciting incident** | The **first disruptive event** that kicks off the crisis scenario and drives players into action |
{% hint style="info" %}
For more in-depth information on any of these terms, use the search bar in the right-hand corner
{% 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://helpdocs.conducttr.com/colibri/overview/about-colibri/dictionary-of-colibri-terms.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.