> 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/start-here/getting-started.md).
# Getting started
## Essentials
Conducttr is a crisis exercise platform. At its heart is a simulation **space**.
In order to interact with the simulation space we provide three key components:
* **Editor**: This is where you design and build your exercises
* **Facilitator Dashboard**: This is where the facilitator controls the exercise and monitors player activity
* **Virtual Desktop**: This is where players (the training audience) experience a first-person view of your exercise.
### End-to-End Process
This document site and our advice is structured around four key stages from exercise planning through to reporting.
Below we'll explain these stages.
{% stepper %}
{% step %}
### Planning Your Exercise
* **Draft Your Concept**: Before jumping into design, outline the key objectives, metrics, outcomes, and scenarios you want your exercise to address
* **Use Conducttr's Planning Tools**
We have an area called AXS (Active eXercise System) here you'll find a number of ways to quickly develop an exercise:
* **ASSISTANTS** are chatbots designed to help write better exercises. E.g. LISA will quickly create a Master Events List (MEL)
* **CANVAS** is a one-page overview of your exercise. It allows you to explore ideas and present them to clients for sign-off
* **FIEMA** stands for *Framework for Information Environment Measurement and Analysis*. It's Conducttr's methodology for defence exercises and is built around measurement of effects. The FIEMA tool in AXS can be used to identify audiences and their beliefs
{% content-ref url="/pages/ffPpbXPMrjUGQLPYkORr" %}
[Active eXercise System (AXS)](/feature-documentation/planning/active-exercise-system-axs.md)
{% endcontent-ref %}
We also have a purple sidebar in the Editor called Sidekick which houses:
* **LISA** where she can write directly into the MEL
* **Scenario Idea Generator** where you can brainstorm focused and realistic scenario ideas by identifying plausible vulnerabilities for an organisation
* As well as many more assistants!
{% content-ref url="/pages/t8KowZqED0vvaMfJBhTj" %}
[Sidekick](/feature-documentation/designing-and-running/exercise-editor/sidekick.md)
{% endcontent-ref %}
{% endstep %}
{% step %}
### Designing your exercise
There are two ways to think of this:
1. The **conceptual**
2. The **practical**
Conceptually you need to consider "SME" (Story, Mechanics and Environment) and how your crisis unfolds.
{% hint style="info" %}
This is explained in the CONCEPTS area:
{% endhint %}
{% content-ref url="/pages/yizgySz1mPkdpjA4BjFp" %}
[Designing](/concepts/designing.md)
{% endcontent-ref %}
Here we'll consider **the practical**. The diagram below shows the common elements of your exercise:
{% hint style="info" %}
You can find out more about each of those elements by searching this site.
{% endhint %}
{% endstep %}
{% step %}
### Running your exercise
To run the exercise, **you must publish it to a simulation space**. This is when the exercise transfers from the Editor (where it's passive) to the Space (where it's now active).
The exercise can now be controlled to some degree by the Facilitator using the Facilitator Dashboard.
{% hint style="info" %}
Find out more about running exercises on the page below:
{% endhint %}
{% content-ref url="/pages/WtwWpqjVxhO7idwaGP2o" %}
[Facilitator Dashboard](/feature-documentation/designing-and-running/facilitation/facilitator-dashboard.md)
{% endcontent-ref %}
{% endstep %}
{% step %}
### Reporting
Conducttr provides several reporting tools but the results you see are affected by the design stage. When you're creating an exercise, **think ahead about how you'll measure and assess performance**.
{% hint style="info" %}
Check the Reporting section for all the options:
{% endhint %}
{% content-ref url="/pages/5Jy6mRPBhOOSVlYhFcKq" %}
[Reporting](/feature-documentation/reporting.md)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}
---
# 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/start-here/getting-started.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.