> For an agent: the map of this documentation is at https://escouade.io/en/docs/llms.txt; every page exists in Markdown, at the same address with `.md` appended.

# Ingestion

> Ingestion is the path that turns an email or a document into knowledge about your company: it arrives, it is read, sorted, linked to its records, then remembered. What Escouade cannot settle on its own becomes a proposal, which awaits your decision.

The module opens from the "Ingestion" entry of the menu. Its bar follows the path of an email: **Overview**, then **Sources › Rules › Decision model › LLM analysis › To review**, then **Health** and **Settings** for those allowed.

## Sources

The Sources page shows where data comes from:

- from Escouade: each mailbox you read, each Google Drive of the workspace, uploads to the Library;
- from connected applications and services: Meet, whose minutes arrive through the family relay, or supplier invoice software.

For each source: its status, what it brought today and over seven days, and its last arrival. A silent mailbox goes to the top. A mailbox is connected in Settings › Accounts, where its ingestion is switched on: see [Connectors](https://escouade.io/en/docs/connecteurs.md).

## Sorting, in a cascade

Every email goes down three levels, in order, and stops at the first one that can settle it:

1. **Rules**: the ingestion rules and the decision tree (what is decided for each email, its outcomes, the catch-up). A rule settles without hesitation what always comes back the same way.
2. **Decision model**: a model that learns from your past decisions, with two thresholds per question, set on its screen. It learns from the decisions, ground truths, datasets and extractions the screen shows.
3. **LLM analysis**: a language model votes three times; the decision is taken when the quorum is reached. The screen shows how far the vote agrees with history.

What no level settles goes to **To review**. The Overview shows, over a period, who settled things: the rules, the model, the analysis, or a member of the team ("Human approvals").

## To review: the control centre

To review gathers everything that awaits a human decision: **proposals**, **documents to re-read**, **questions** and the **review queue**. The badge in the menu shows the count.

A proposal is a change an agent wants to make:

- create a record, update a field;
- link an email to its deal, classify a document;
- create a task, complete a timeline.

Each one says why, cites the email or document that gave rise to it, and gives a confidence score. **Approve** applies it; **reject** sets it aside. An applied proposal can be undone, and the control centre keeps track of what was decided.

## Rules, when the answer is always the same

When a proposal keeps coming back and you always approve it, make it an "Always apply" rule. It stays visible, and you can remove it.

Some filing operations apply without waiting: filing an attachment in its folder, linking an email to its deal.

## Health

Health holds the ingestion alerts. The "Silent mailbox" alert counts in working hours: a mailbox that is quiet in the evening or at the weekend does not ring; "Critical" is reserved for a synchronisation that has truly failed.