team-narrative

Game narrative orchestration aligns multiple narrative roles into a single cohesive delivery, preventing disconnected writing, lore, and level storytelling. It produces story briefs, lore entries, dialogue lines, and level trigger integration points concurrently.

Yes, you can generate localization-ready dialogue by enforcing i18n constraints during the drafting phase. The orchestration pipeline flags internationalization risks and applies string-key and formatting constraints to ensure dialogue is translation-ready.

The best way to plan story beats and faction canon is using a phased agent delegation pipeline with approval checkpoints. This approach concurrently produces faction and location history while defining narrative triggers for the specified level.

Yes, narrative pipeline orchestration includes consistency gates that review voice and lore alignment. It performs targeted consistency reviews to ensure dialogue and world lore entries match established canon before finalizing file outputs.

Yes, YAML-defined discovery metadata is required to run narrative orchestration tasks. The pipeline parses this YAML metadata and arguments to select review modes and delegate phased narrative generation to subagents.

A limitation of phased agent delegation is that it requires explicit user approval at each phase transition. Additionally, deterministic file writes are delegated to subagents, meaning output depends strictly on the initial YAML discovery metadata provided.