---
title: "Chronicle generation"
description: "How campaign events become eras, chapters, current-era prose, and editable local history."
---

> Stellaris Companion documentation
> Complete index: https://galacticfilingcabinet.com/llms.txt

# Chronicle generation

Chronicle turns the campaign archive into a narrative layer. It selects event clusters and state changes, then asks the configured model to produce prose in the chosen voice.

## Chapters and the current era

Finalized chapters describe completed arcs. The current era is a living section that can change as new saves arrive. Existing chapters stay readable even when the selected AI provider is offline because the generated text is cached locally.

Chronicle generation receives extracted events and bounded campaign context, not the raw `.sav` file.

## Editing from an AI client

A connected MCP client can read the cached Chronicle and request source material for a new passage. Drafting and revision should happen in chat first.

Write-back is deliberate:

- save current-era text;
- update an existing chapter;
- create a chapter;
- undo a Chronicle edit.

These actions affect the local Chronicle cache only. They do not edit game state, call the in-app provider, or declare the campaign history final.

Source: https://galacticfilingcabinet.com/docs/how-it-works/chronicle-generation/index.mdx