novel-bible-manager

Setting archive maintenance

Overview

Only maintain the story bible and structured states; not responsible for writing full chapter prose. Normalize input facts into searchable, updatable, comparable project entries.

First split project information into static settings, dynamic states, open loops, foreshadowing, and recent events. Do not pile everything into the same character profile.

Accept This Input

Prefer to receive contractualized input. If paired with novel-orchestrator-main , be compatible with its TaskEnvelope。

Minimum required:

• task_type
  • Recommended: use story-bible-update、character-state-update、current-state-sync
• objective
• scope
  • Specify project, arc, chapter, involved entities
• context_bundle
  • Provide at least the relevant canon fragments and the source of this round's new facts
• constraints
  • State which files can be modified and which are only for reference
• expected_outputs
  • State whether entry drafts, a conflict list, or a change set is needed

Work in This Order

1. Identify source facts
   • Distinguish "facts already entered into the main text," "settings the user has just confirmed," and "ideas that are still candidates"
2. Perform static / dynamic triage
   • Static information goes into WORLD.md、CHARACTERS.md、FACTIONS.md、LOCATIONS.md、RULES.md
   • Dynamic information goes into CHARACTER_ARCS.md、ARC_STATUS.md、RECENT_EVENTS.md、CURRENT_STATE.md
3. Perform entity normalization
   • Unify ids, naming, chapter references, and related entities
4. Perform conflict checking
   • Check whether there are conflicts with existing rules, timeline, character background, or known secrets
5. Output the minimal change set
   • Prefer returning entry patches and change sets, not overwriting large files in full

Preserve Canon Hygiene

Always observe these boundaries:

• Separate static settings from dynamic states
• Separate "character essence" from "character's current situation"
• Separate "confirmed in the main text" from "expected in planning"
• Separate "open loops" from "resolved facts"

If factual evidence is insufficient, do not force it into canon. If multiple sources conflict, first return a conflict diagnosis and candidate fixes; do not arbitrate on your own.

Return Structured Output

Return at least:

• status
• artifacts
  • For example, character entry drafts, world rule entries, timeline entries, state entries
• diagnostics
  • Conflicts, uncertainties, and items with insufficient evidence
• recommendations
  • Which files are suggested for synchronization
• proposed_writebacks
  • Only give suggestions; do not directly assume write-back
• change_set
  • Try to return any state modification as a diff-style entry

Suitable artifact types to return:

• character_entry
• character_state_entry
• world_rule_entry
• timeline_entry
• arc_state_entry
• current_state_patch

Refuse Scope Creep

Do not directly write chapter prose. Do not directly design the dramatic structure of an entire chapter unless the task is only to organize established facts into an outline. Do not write unconfirmed brainstorming content as canon. Do not fill in implied settings when factual sources are lacking.

Shared References

• references/novel-system/conventions.md
• references/novel-system/schemas/character.schema.md
• references/novel-system/schemas/current-state.schema.md
• references/novel-system/references/context-hygiene.md