---
title: "Save parsing and campaign history"
description: "How the Companion extracts structured facts and turns repeated saves into a timeline."
---

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

# Save parsing and campaign history

A Stellaris save is a compressed game-state document, not a ready-made story. Stellaris Companion uses a Rust parser built on Jomini to read the save and extract the domains needed by the Advisor and Chronicle.

## From file to snapshot

The extractor identifies the player empire, economy, technology, military, diplomacy, internal politics, galactic conditions, and recent event signals. The exact briefing is a bounded interpretation of those facts; it is not a copy of the entire save.

Each successful ingestion creates a timestamped snapshot in a local SQLite archive. Comparing snapshots lets the Companion identify direction:

- a deficit that is shrinking or accelerating;
- a fleet that is rebuilding after losses;
- a diplomatic relationship that changed;
- territory, population, technology, and policy changes;
- events that belong in a Chronicle chapter.

## What it does not do

The parser does not write to the `.sav` file. It does not run the game, issue console commands, or simulate an outcome. Advice is an interpretation of recorded state, not a guarantee about the next event roll.

Source: https://galacticfilingcabinet.com/docs/how-it-works/save-parsing-and-history/index.mdx