Skip to main content

·3 min read·The Aegis Brightsmark team

How The Living Chronicle Works

Every morning, thousands of players wake to a new chapter of a story they wrote the day before. Here is how that loop actually works — votes, investigations, factions, and a ten-step AI pipeline.

  • game design
  • AI
  • narrative

The daily ritual

The Living Chronicle is built around a very simple promise: a new chapter lands every single day, and what is in that chapter is shaped by what players did the day before. The ritual is short on purpose — five minutes in the morning, one chapter, a handful of decisions, and a long tail of discussion that runs all day inside covens and on social channels.

Everything that happens on the publishing side is invisible to the reader. From inside the app it feels like waking up to a novel that has quietly rewritten itself overnight. From the inside of our pipeline, it is a much more deliberate process.

Votes, investigations, and faction operations

Three kinds of player action feed into the next chapter:

  1. Votes on open questions that the last chapter left dangling. Each vote is weighted by the size of the player's faction, their recent activity, and whether they have skin in the question being asked. Majorities usually get what they ask for, but influence matters, and so do minority coalitions with the right rank.
  2. Investigations are player-initiated: you spend Action Points to dig into a character, a rumor, a ruin, or a relationship. Outcomes are drawn against a rarity table with a published pity mechanic, and anything rare or better becomes canon.
  3. Faction operations are coordinated actions run by covens — sabotage, reconnaissance, diplomacy, occupation. These play out asynchronously and their outcomes feed directly into the DM step of the pipeline, so the next chapter reacts to them.

Taken together, these three inputs describe what the community wants the story to do. The pipeline decides what it will actually do.

The ten-step pipeline

Every chapter goes through ten steps. Each step is either a deterministic service or an AI agent with a pinned prompt:

  1. Collect. Gather votes, investigations, and operations from the last 24 hours.
  2. Community detection. Scan the narrative graph for plot clusters that are heating up.
  3. Retrieve. Pull the relevant sub-graphs from Neo4j so the writer only sees what matters.
  4. Plan. The orchestrator drafts the chapter outline.
  5. Simulate. The DM agent resolves mechanics — investigation rarities, operation outcomes, rank changes.
  6. Validate. The rules referee checks the draft against world canon and tone constraints.
  7. Update graph. State changes land in the database.
  8. Write. The writer produces the prose.
  9. Edit. The editor polishes voice and pacing.
  10. Publish. After a human curator signs off, the chapter goes live.

No step publishes without the curator. That is deliberate.

Why daily, not weekly

Weekly is the obvious cadence for a serialized narrative, but it does not fit how people use phones. Daily turns the Chronicle into a ritual the same way Wordle did — short, predictable, shareable, and just novel enough that missing a day feels like missing something real. And a daily cadence means player input never has time to go stale: you vote on something on Tuesday, you see its consequences on Wednesday.

What is next

In the weeks ahead we will share more about the graph that powers the referee, the decisions we have made around AI transparency, and the design philosophy behind making a dark-fantasy game you actually want to open first thing in the morning.

Until then: the next chapter drops in a few hours. Come shape it.

← More posts
How The Living Chronicle Works — The Living Chronicle | The Living Chronicle