Consolidate scene and normalization prompt instructions

assets/dnd/locations/normalize/prompts/instructions.md

@@ -0,0 +1,6 @@
+Use candidate names and their cited transcript windows to determine whether
+candidates identify the same physical place. Do not treat matching names,
+nearby evidence, nested places, or generic labels as sufficient. Keep parent
+and child places, similarly named places, and uncertain aliases separate.
+
+When selecting a canonical display name, prefer the clearest established name.

assets/dnd/locations/normalize/prompts/prompt.yaml

@@ -12,7 +12,7 @@ messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
   - role: user
-    content_file: ./task.md
+    content_file: ./instructions.md
   - role: user
     content_file: ./sharedassets/common-dnd-entity-reconciliation.md
     cache_control:

assets/dnd/locations/normalize/prompts/task.md

@@ -1,8 +0,0 @@
-Review location candidates and cited transcript context. Group candidates only
-when the evidence clearly identifies one physical place.
-
-Do not group candidates solely because their names match, their evidence is
-nearby, one place is nested inside another, or their labels are generic. Keep
-parent and child places, similarly named places, and uncertain aliases
-separate. For an accepted group, select the supplied candidate with the
-clearest established display name as canonical.

assets/dnd/npcs/normalize/prompts/instructions.md

@@ -0,0 +1,10 @@
+Use candidate aliases and their cited transcript windows to determine whether
+candidates refer to the same individual. Preserve distinct individuals even
+when their names are similar.
+
+When selecting a canonical display name, prefer a complete, stable proper name
+over an abbreviation. Prefer an unadorned proper name over that name plus a
+contextual class, role, title, or relationship descriptor unless the transcript
+establishes the descriptor as part of the person's name. A longer display name
+is not inherently more canonical; for example, do not prefer `Captain Aria`
+over `Aria` solely because it includes the contextual title `Captain`.

assets/dnd/npcs/normalize/prompts/prompt.yaml

@@ -12,7 +12,7 @@ messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
   - role: user
-    content_file: ./task.md
+    content_file: ./instructions.md
   - role: user
     content_file: ./sharedassets/common-dnd-entity-reconciliation.md
     cache_control:

assets/dnd/npcs/normalize/prompts/task.md

@@ -1,13 +0,0 @@
-Review NPC candidates and their cited transcript context to identify aliases
-that refer to the same individual. Propose only groups supported by the
-transcript, and preserve distinct individuals even when their names are
-similar.
-
-For every accepted group, choose as canonical only a supplied candidate from
-that evidence-supported duplicate group. Prefer a complete, stable proper name
-over an abbreviation. Prefer an unadorned proper name over that name plus a
-contextual class, role, title, or relationship descriptor unless the transcript
-establishes the descriptor as part of the person's name. A longer display name
-is not inherently more canonical; for example, do not prefer `Captain Aria`
-over `Aria` solely because it includes the contextual title `Captain`. Do not
-invent, edit, or combine display names.

assets/dnd/scene-descriptions/prompts/instructions.md

@@ -1,4 +1,9 @@
-Choose exactly one kind:
+Describe exactly one accepted Dungeons & Dragons scene from the supplied
+transcript chunk. The complete chunk is the evidence boundary: do not split it
+into multiple scenes or use facts that are not supported by it.
+
+Return one kind, one concise title, and one concise summary. Choose exactly one
+kind:
 
 - combat: active combat materially organizes the scene, including
   initiative-like exchanges or sustained hostile action. Planning a fight or
@@ -39,6 +44,3 @@ outcome established within the accepted chunk. Do not add analysis, inferred
 motives, hidden state, future consequences, relationship claims, or facts from
 outside the chunk. Campaign references may disambiguate names but never add
 events or lore.
-
-Do not return identifiers, source identifiers, source ranges, unit identifiers,
-participants, confidence, or any fields besides kind, title, and summary.

assets/dnd/scene-descriptions/prompts/prompt.yaml

@@ -27,8 +27,6 @@ messages:
     content_file: ./sharedassets/common-dnd-transcript-chunk.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/scene-descriptions/prompts/task.md

@@ -1,5 +0,0 @@
-Describe exactly one accepted Dungeons & Dragons scene from the supplied
-transcript chunk. The complete chunk is the evidence boundary: do not split it
-into multiple scenes or use facts that are not supported by it.
-
-Return one kind, one concise title, and one concise summary.

assets/dnd/scenes/prompts/instructions.md

@@ -1,8 +1,19 @@
-Cover the complete provided transcript from its first source unit to its last
-source unit. Return scenes in source-unit order with no gaps or overlaps. Use
-only positive integer source-unit IDs from the transcript, and give every scene
-one inclusive `start_unit_id` and one inclusive `end_unit_id`.
+Divide the complete provided transcript into coherent Dungeons & Dragons scenes
+for the `dnd/scenes` chunk module.
 
-Return exactly one JSON object and no explanatory text. The object must contain
-only a non-empty `scenes` array. Each scene object must contain only
-`start_unit_id` and `end_unit_id`.
+A scene is a coherent unit of play. Start a new scene when the transcript
+establishes a meaningful change in location, objective, threat, activity,
+encounter, or mode of play. Good reasons include a material move, beginning or
+ending combat, a substantially different encounter phase, a shift between
+combat, exploration, social interaction, planning, travel, rest, or downtime,
+a change in the central NPC, faction, threat, or objective, or a sustained
+table-level interruption that materially changes the activity.
+
+Do not split a scene merely because a speaker or combat round changes, a
+routine turn occurs, or the table briefly digresses. Prefer fewer coherent
+scenes over speculative or fine-grained boundaries.
+
+Cover the complete transcript from its first source unit to its last. Return
+scenes in source-unit order with no gaps or overlaps. Use only positive integer
+source-unit IDs from the transcript, and give every scene one inclusive
+`start_unit_id` and one inclusive `end_unit_id`.

assets/dnd/scenes/prompts/prompt.yaml

@@ -21,8 +21,6 @@ messages:
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
   - role: user

assets/dnd/scenes/prompts/task.md

@@ -1,18 +0,0 @@
-Divide the provided transcript into coherent Dungeons & Dragons scenes for the
-`dnd/scenes` chunk module.
-
-A scene is a coherent unit of play. Start a new scene when the transcript
-establishes a meaningful change in location, objective, threat, activity,
-encounter, or mode of play. Good reasons include a material move, beginning or
-ending combat, a substantially different encounter phase, a shift between
-combat, exploration, social interaction, planning, travel, rest, or downtime,
-a change in the central NPC, faction, threat, or objective, or a sustained
-table-level interruption that materially changes the activity.
-
-Do not split a scene merely because a speaker or combat round changes, a
-routine turn occurs, or the table briefly digresses. Prefer fewer coherent
-scenes over speculative or fine-grained boundaries.
-
-Return only inclusive `start_unit_id` and `end_unit_id` endpoints for each
-scene. Do not return titles, modes, participants, summaries, boundary notes,
-confidence, caveats, final chunk IDs, or chunk indexes.