> For the complete documentation index, see [llms.txt](https://docs.algenta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algenta.ai/concepts.md). # Concepts - [How the engine works](https://docs.algenta.ai/concepts/engine.md): How Algenta integrates deterministic compiled compute, validates every request, and fails closed without exposing runtime lifecycle to users. - [The governed decision lifecycle](https://docs.algenta.ai/concepts/decision-service.md): How Algenta turns enterprise data and operating models into governed, versioned, reproducible decisions instead of one-off chat answers - [Governed data & query](https://docs.algenta.ai/concepts/governed-data.md): Governed data is data Algenta queries under a typed, schema-validated, deterministic, auditable contract — sources, datasets, connectors, and the resolve to query flow. - [The capability plane](https://docs.algenta.ai/concepts/capability-plane.md): The unified router that turns an objective into the right provider and skill, then executes it — discovery, routing, execution, adapters, and fail-closed execution ownership. - [Simulation models & distributions](https://docs.algenta.ai/concepts/simulation-models.md): The simulation algorithms and input distributions Algenta runs — auto vs expert mode, when to pick each engine, and how a seed makes every run reproducible. - [Decision memory](https://docs.algenta.ai/concepts/decision-memory.md): Decision memory is the persisted log of decisions, the real-world outcomes recorded against them, and the review loop that lets the engine learn which decision types are over- or under-confident. - [Execution ownership & fail-closed](https://docs.algenta.ai/concepts/execution-ownership.md): Who runs a capability — algenta\_managed (the engine executes) vs client\_managed (your adapter executes) — and why an unresolved or unsupported owner fails closed. - [Deployment modes & privacy](https://docs.algenta.ai/concepts/deployment-modes.md): How ALGENTA\_DEPLOYMENT\_MODE selects a privacy profile — cloud, telemetry, metering, and egress defaults — and how the engine fails closed on outbound network in air-gapped runs. --- # 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.algenta.ai/concepts.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.