A practical reading method
Reduce Working-Memory Load in a Large-Cast Novel
Create an entry only when a character becomes active, starting with first entrance page and one stable identifier. Update current relation only when the text changes it and attach the changing page. Keep one unresolved question; archive the entry when the character has been inactive long enough to stop affecting orientation.
Use this when a large cast makes reading stop-and-search work more frequent than the story itself. An encyclopedia-sized character list creates a second reading task. Three fields preserve orientation while letting old details leave the active view.
Use case
When this method helps
Use this when a large cast makes reading stop-and-search work more frequent than the story itself.
An encyclopedia-sized character list creates a second reading task. Three fields preserve orientation while letting old details leave the active view.
Method
Build the note
1. Create an entry only when a character becomes active, starting with first entrance page and one stable identifier.
2. Update current relation only when the text changes it and attach the changing page.
3. Keep one unresolved question; archive the entry when the character has been inactive long enough to stop affecting orientation.
Example
See the boundary in practice
Nadia—first seen page 12, currently Mara's supervisor, live question: why does she recognize the seal on page 88?
Quality check
Before you trust the note
Each active entry should fit on one line and every relationship change should have a page anchor.