Characters / SAGALITH editorial
Build a character database that helps you write scenes
A character database should answer writing questions quickly. A profile full of trivia is less useful than a small record of what the character wants and who stands in the way.
Record the details that affect decisions
For each recurring character, begin with role, goal, obstacle and a relationship under pressure. Those details explain why they enter a scene and what they might do when the scene turns against them.
For a fictional navigator, the goal might be to reopen a forbidden route, the obstacle a guild oath, and the strained relationship an archivist who knows the route's history. That gives you material for action. Eye color can wait until it matters to the description.
Link relationships rather than repeating them
If a character belongs to a faction, connect the character entry to that faction. Put the organization's general history in the faction entry and the character's personal reason for joining in their profile. This avoids several conflicting versions of the same background.
Family relationships can be viewed as a tree, while other connections can be explored through linked entries. In SAGALITH, the character archive also has search and filters, so a growing cast does not have to become an unstructured scroll of names.
- One stable entry per recurring character.
- A concise summary you can recognize in the archive.
- Links to important people, places and factions.
- A clear distinction between public information and spoilers.
Update continuity at the end of a scene
When a scene establishes a new fact, update the relevant profile while the decision is fresh. Record a change in allegiance, an injury or a revealed history where you will find it next time. Do not ask your memory to serve as the version history of an entire cast.
Use a timeline for events whose order matters, and avoid duplicating long chronology inside every biography. The profile should lead you to the right event or relationship rather than contain the whole world.
Treat visual references as supporting material
An uploaded portrait or a generated reference can help you maintain the character's visual identity. Keep a concise written appearance description too, because it remains searchable and useful when an image is ambiguous.
SAGALITH Visual Studio can use a locked identity and an anchor image to guide later generations. Review the result instead of assuming perfect consistency. The character's choices and voice still belong in the written profile and manuscript.