# Introduction

LoopDesk is the approval layer for AI workflows. AI drafts, humans decide — but only when humans actually need to.

This documentation covers what human-in-the-loop is, how LoopDesk implements it as a routing layer rather than a workflow tool, and how to integrate it end-to-end.

## Where to start

* **New to HITL?** Read [Why HITL](/hitl-docs/human-in-the-loop/why-hitl.md), then [The LoopDesk model](/hitl-docs/human-in-the-loop/hitl.md).
* **Integrating?** Jump to the [Quick start](/hitl-docs/getting-started/quick-start.md) and the [Integration guide](/hitl-docs/guides/integration.md).
* **Reviewing items?** The [Reviewer handbook](/hitl-docs/guides/reviewer-handbook.md) is short and worth reading once.
* **Tuning a live system?** See [Tuning thresholds](/hitl-docs/guides/tuning-thresholds.md) and [Patterns & anti-patterns](/hitl-docs/human-in-the-loop/patterns.md).
* **Looking up an endpoint?** [Public API](/hitl-docs/api/public-api.md), [Webhooks](/hitl-docs/api/webhooks.md), [Schema](/hitl-docs/architecture/schema.md).

Use the sidebar for the full table of contents.


---

# Agent Instructions: 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:

```
GET https://hitl-01.gitbook.io/hitl-docs/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.