Direct answer
Start by reviewing the extracted chapters, character records, relationships, and timeline signals. Correct obvious extraction mistakes, then choose one revision question and use grounded answers or continuity views to locate the scenes that need decisions.
Why it matters
A calm first pass helps LoreVia become a working revision system instead of another place where notes pile up.
A simple way to handle it
- Confirm the chapter structure and import boundaries look right.
- Review the highest-value story memory: main characters, relationships, and open threads.
- Ask one concrete question about the draft before making edits.
Do not try to solve the whole book immediately
A manuscript import gives you a lot of surfaces at once. If you jump between every character, timeline event, note, and answer, the session can feel busy without becoming useful.
Pick the area with the most revision pressure. If you are worried about continuity, start there. If the emotional arc is unstable, start with relationships and character history.
Make the system more trustworthy
Review the records that matter most and fix anything obviously stale or misread. The point is not to perfect the database on day one. It is to make the parts you plan to use this week accurate enough to support real decisions.
Once the import looks reliable, ask a grounded question and follow the answer back to the manuscript. That closes the loop between analysis and editing.
- Correct names and aliases for major characters.
- Check whether chapter labels match the manuscript.
- Turn one answer into one specific revision action.

