> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Product glossary

> Definitions for Entelligence products, concepts, controls, patterns, automations, mappings, and deployment terms.

| Term                       | Meaning                                                                                            |
| -------------------------- | -------------------------------------------------------------------------------------------------- |
| Ask Ellie                  | Conversational interface for answers and permitted actions across connected context                |
| AutoDocs / Documentation   | Repository documentation generation and synchronization product                                    |
| Balanced                   | Model Router quality-and-savings mode                                                              |
| Codebase Context           | Repository Markdown files enabled as Code Review context                                           |
| Code Reliability           | Beta product containing Incident Knowledge and Observability Audit                                 |
| Confidence score           | Code Review 1–5 merge-confidence signal                                                            |
| Connector                  | Authorized link between Entelligence and an external system                                        |
| Detection                  | Production event used by Incident Knowledge                                                        |
| Eco                        | More cost-focused Model Router mode                                                                |
| EKU                        | Error Knowledge Unit; CLI term for a recurring incident pattern                                    |
| Exclusion                  | File pattern or built-in group skipped by Code Review                                              |
| Guideline                  | Review standard assigned to repositories                                                           |
| Hosted Proxy               | Entelligence-hosted Model Router billing and request path                                          |
| Learning                   | Feedback-derived Code Review context intended to reduce repeated unhelpful findings                |
| Linked codebase            | Related repository supplied as cross-codebase context                                              |
| Mapping                    | Association between external and Entelligence user, team, project, repository, service, or channel |
| MCP                        | Model Context Protocol connection for compatible AI clients                                        |
| Observability Audit        | Repository analysis of observability issues, coverage, and recommendations                         |
| Pattern                    | Recurring production behavior derived from detections                                              |
| Pulse                      | Scheduled Ellie report or message                                                                  |
| Reactor                    | Slack-event automation with instructions and inclusion/exclusion rules                             |
| Shared engineering context | Authorized context combined across Entelligence workflows; not a separate product                  |
| Source Mapping             | Association between an incident/observability source and repository                                |
| Wrapped                    | Personal coding-agent usage summary generated by the CLI                                           |
| BYOK                       | Customer-provided model-provider credentials where supported                                       |

## Naming rules

* Use **Ask Ellie**, not Ali.
* Use **Entelligence Code Review**, not a competitor product name.
* Use **Entelligence CLI** and the `entelligence` command.
* Use **Code Reliability** with a Beta label.
* Use **shared engineering context** for the underlying cross-product concept.

## Next step

Check the [metrics glossary](/reference/metrics) or [availability](/reference/availability).