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

# Modes & Lifecycle

How OM1 organizes behavior into modes and manages their lifecycle.

OM1 structures robot behavior into **modes** — distinct operational states such as social interaction, exploration, patrol, or autonomous navigation — and governs how the system moves between them.

This section covers:

* [**Modes**](https://docs.openmind.com/build/modes_lifecycle/modes.md) — what modes are and how each one shapes perception, input handling, and task priorities.
* [**Mode Selection**](https://docs.openmind.com/build/modes_lifecycle/mode_selection.md) — the different ways to switch modes: context-aware, time-based, input-triggered, or manual.
* [**Transition Rules**](https://docs.openmind.com/build/modes_lifecycle/transition_rules.md) — how and when the robot moves between modes, defined as prioritized rule objects.
* [**Lifecycle**](https://docs.openmind.com/build/modes_lifecycle/lifecycle.md) — the activation-to-termination boundaries of a mode, ensuring predictable, safe transitions.


---

# 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.openmind.com/build/modes_lifecycle.md?ask=<question>&goal=<user_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.
