> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.loreos.app/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.loreos.app/_mcp/server.

# Why LoreOS

Most character products start as prompts. LoreOS starts as state.

A prompt-wrapped character can feel convincing for one turn. Over time, the hard parts
show up: memory drift, flattened personality, repeated motifs, inconsistent backstory,
private-plan leakage, one-off images, delivery failures, unclear model cost, and no easy
way to inspect why a reply happened.

LoreOS is the managed runtime for long-running AI characters. It keeps behavior grounded
in typed ledgers and compiled state projection: persona, memory, character facts,
relationship state, user agency, world context, Story Room outputs, visual readiness,
delivery, metering, and observability.

## What makes it different

### State projection, not one long prompt

LoreOS compiles current character behavior from source-of-truth ledgers instead of
asking one prompt to remember everything forever.

### Story Room, not one-turn improvisation

Characters should not wake up only when the user sends a message. LoreOS can prepare
daily-life context: routines, obligations, social contact, quiet days, small frictions,
and safe context the chat actor can reference later.

### Safe runtime context, not private-plan leakage

The runtime keeps a boundary between:

* **private state** — plans, forecasts, hidden character-fact candidates, and internal reasoning;
* **committed state** — facts and events that are accepted into the character's world;
* **safe runtime context** — the subset the chat actor may use in a reply.

Models can imagine. Code decides what becomes true.

### Visual identity, not one-off image generation

LoreOS manages identity images, reusable visual assets, readiness checks, and probes so
characters can appear consistently over time.

### Delivery and observability, not background jobs you rebuild

When a character behaves strangely, LoreOS should show you why: session events, runs,
delivery status, usage, readiness, and traces are part of the platform.

## Who it is for

Primary use cases:

* consumer companion apps;
* fictional characters with memory and visual identity;
* Telegram character bots, including managed child bots for B2C relationships;
* games and interactive story apps;
* social products with persistent AI characters.

Secondary use cases:

* persona-heavy tutors;
* guides or assistants where continuity, relationship state, and delivery matter.

LoreOS is in preview while the platform is being hardened. Start with a no-login
demo sandbox key or self-serve account access depending on whether you need a
persistent app. Read [Authentication](https://docs.loreos.app/getting-started/authentication),
then use the [Quickstart](https://docs.loreos.app/getting-started/quickstart) to create
your first character session.