> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/introduction/about-this-guide.md).

# About this guide

This guide covers AMIE from first sign-in to day-to-day use. It is written for the administrators who set the system up and the people who use it to look after a fleet.

## How it is organized

| Section                     | Read it when                                                                                                 |
| --------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Introduction**            | You are new to AMIE and want to know what it is and how it fits together                                     |
| **Planning and Deployment** | You are deploying AMIE for the first time, or moving to it from the previous console                         |
| **Using the platform**      | You are using the console. One page per screen: what it shows, what you can do, and how to read it           |
| **Metrics reference**       | You want to know exactly how a figure is calculated, what it includes and excludes, and where it can mislead |
| **Charts reference**        | You want to know how to read a kind of chart that appears on several screens                                 |

## Conventions

* Names of things you see on screen — buttons, headings, column titles, menu items — are in **bold**, exactly as they appear.
* Where an action depends on your role, the page says so: "Requires the **Admin** or **Owner** role", or "Grayed out? Your role does not include this." What each role can do is on [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md).
* Screenshots are taken from a test system. The numbers and names you see will differ from yours.
* Callouts mark two kinds of note:

{% hint style="info" %}
Something useful to know that is not obvious from the screen.
{% endhint %}

{% hint style="warning" %}
Something that is easy to misread, or that behaves differently from what you might expect.
{% 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.spectralink.net/amie-advanced/introduction/about-this-guide.md?ask=<question>&goal=<user_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.