> For the complete documentation index, see [llms.txt](https://docs.rumi.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rumi.systems/rumi-management/concepts.md).

# Concepts

This section covers the key concepts behind Rumi Management.

* [Architecture](/rumi-management/concepts/architecture.md) — how the management components relate and the two architectural flows (CnC and telemetry).
* [Deployment Lifecycle](/rumi-management/concepts/deployment-lifecycle.md) — what a System is; the lifecycle verbs (provision → deploy → configure → launch → shutdown → deprovision); invocation via script DSL, interactive mode, or REST.
* [Deployment Model](/rumi-management/concepts/deployment-model.md) — the Controller's in-memory model of discovered containers, services, and their bus connections, built from lifecycle events and queryable by embedders.
* [Command and Control](/rumi-management/concepts/command-and-control.md) — ad-hoc operations against running systems, directed at apps, engines, the JVM, or the host.
* [Scripting](/rumi-management/concepts/scripting.md) — the script DSL as a language: nouns, verbs, control flow, examples, and ways to run scripts.
* [Telemetry Model](/rumi-management/concepts/telemetry-model.md) — the three signal types (telemetry, lifecycle events, alerts), their dispositions, the session and passive modes, and stat categories.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rumi.systems/rumi-management/concepts.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.