Consolidate grounded event extraction instructions

assets/dnd/enemy-events/prompts/instructions.md

@@ -1,14 +1,25 @@
+Extract Dungeons & Dragons enemy events from the supplied combat transcript.
+An `engaged` event requires direct establishment that a subject is actively
+opposing the party in combat. A `killed`, `fled`, `captured`, or
+`incapacitated` event requires explicit establishment of that outcome. An
+outcome may share evidence with an engagement, and a later engagement or
+outcome for the same subject remains a separate observation. Emit at most one
+`engaged` observation for the same subject in this combat scene.
+
+For `killed`, direct death or killing is required. For `fled`, the subject
+must explicitly escape, retreat, or leave combat to avoid continued engagement.
+For `captured`, the subject must be explicitly taken prisoner or secured
+under the party's control. For `incapacitated`, the subject must be explicitly
+unable to continue acting without being established as killed or captured.
+
+When the transcript identifies a named NPC, use its normalized registry
+spelling. A hostile creature without a registry entry is allowed. For unnamed
+individuals or groups, use only the narrowest transcript-grounded label, such
+as `Orcs`, `One orc`, or `Remaining orcs`; never invent member names, IDs,
+or quantities.
+
 Exclude party members, allies, neutral observers, mentioned-but-absent enemies,
 hazards, traps, environmental effects, uncertain allegiance, table talk,
 planning, hypotheses, recaps outside this passage, and downstream inference.
-
 Do not infer an engagement or outcome from initiative, turn absence, damage,
-defeat, movement, a scene ending, combat-opponent grounding, or any auxiliary
-artifact. Auxiliary inputs can guide attention but cannot prove or supply an
-event. Cite only narrow current-transcript ranges that establish each event.
-
-Return the `events` array even when no enemy event is established. Every event
-must contain only `name`, `kind`, and `source_refs`. Use exactly one kind:
-`engaged`, `killed`, `fled`, `captured`, or `incapacitated`. Each source range
-uses integer `start_unit_id` and `end_unit_id`; omit `source_id` because
-Notarius assigns the current source identity.
+defeat, movement, or a scene ending.

assets/dnd/enemy-events/prompts/prompt.yaml

@@ -42,8 +42,6 @@ messages:
     content_file: ./sharedassets/common-dnd-npcs.md
   - role: user
     content_file: ./combat-grounding.md
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/enemy-events/prompts/task.md

@@ -1,20 +0,0 @@
-Extract Dungeons & Dragons enemy events from the supplied combat transcript.
-
-Return an `engaged` event only when the transcript directly establishes that a
-subject is actively opposing the party in combat. Return `killed`, `fled`,
-`captured`, or `incapacitated` only when the transcript explicitly establishes
-that outcome. An outcome may share evidence with an engagement, and a later
-engagement or outcome for the same subject remains a separate observation.
-Emit at most one engagement for the same subject in this combat scene.
-
-For `killed`, direct death or killing is required. For `fled`, the subject must
-explicitly escape, retreat, or leave combat to avoid continued engagement. For
-`captured`, the subject must be explicitly taken prisoner or secured under the
-party's control. For `incapacitated`, the subject must be explicitly unable to
-continue acting without being established as killed or captured.
-
-Use a normalized NPC registry spelling when the transcript identifies that
-named NPC. A hostile creature without a registry entry is allowed. For unnamed
-individuals or groups, use only the narrowest transcript-grounded label, such
-as `Orcs`, `One orc`, or `Remaining orcs`; never invent member names, IDs, or
-quantities.

assets/dnd/location-occurrences/prompts/instructions.md

@@ -1,8 +1,24 @@
-Return the occurrences array even when no occurrence is established. Every
-record must contain location_id, name, kind, and source_refs. Copy location_id
-and name from one supplied registry record, and cite only narrow transcript
-ranges that support both that location and its classified occurrence.
+Extract Dungeons & Dragons location occurrences from the supplied transcript.
+Include an occurrence only when the transcript establishes one supplied
+location, one occurrence kind, and a coherent passage supporting both.
 
-Do not summarize location descriptions, infer a missing registry record, or
-use registry context as evidence. Omit source_id; Notarius assigns the current
-transcript source identity.
+Use exactly one kind per occurrence:
+
+- visited: party members are physically present, arrive, remain, or depart;
+- planned: the party explicitly proposes, intends, or agrees to future travel;
+- recalled: the transcript explicitly recounts an earlier party visit; or
+- mentioned: the location is explicitly referenced without stronger support,
+  including non-actionable speculation or a mere hypothetical reference.
+
+A mere hypothetical or speculative reference is not planned unless the
+transcript also establishes an actual proposal, intention, or agreement to
+travel. When the hypothetical explicitly names a supplied location, it may be
+mentioned.
+
+For overlapping support, visited outranks planned, recalled, and mentioned;
+planned outranks recalled and mentioned; recalled outranks mentioned. A passage
+may produce multiple records when it independently establishes separate facts,
+such as recalling an earlier visit while planning a return. Omit inferred,
+unstated, uncertain, or unsupported places and occurrences. Do not infer a
+location or occurrence from surrounding events when the transcript does not
+state it. Do not summarize location descriptions.

assets/dnd/location-occurrences/prompts/prompt.yaml

@@ -34,8 +34,6 @@ messages:
     content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./location-registry.md
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/location-occurrences/prompts/task.md

@@ -1,29 +0,0 @@
-Extract Dungeons & Dragons location occurrences from the supplied transcript.
-
-Include an occurrence only when the transcript establishes one supplied
-location, one occurrence kind, and a coherent passage supporting both. Use
-only the exact ID and name pair from the supplied location registry. Return an
-empty occurrences array when no supplied location has an evidenced occurrence
-in this transcript passage.
-
-Use exactly one kind per occurrence:
-
-- visited: party members are physically present, arrive, remain, or depart;
-- planned: the party explicitly proposes, intends, or agrees to future travel;
-- recalled: the transcript explicitly recounts an earlier party visit; or
-- mentioned: the location is explicitly referenced without stronger support,
-  including non-actionable speculation or a mere hypothetical reference.
-
-A mere hypothetical or speculative reference is not planned unless the
-transcript also establishes an actual proposal, intention, or agreement to
-travel. When the hypothetical itself explicitly names a supplied registry
-location, it may be mentioned using the narrow passage that supports that
-reference.
-
-For overlapping support, visited outranks planned, recalled, and mentioned;
-planned outranks recalled and mentioned; recalled outranks mentioned. A passage
-may produce multiple records when it independently establishes separate facts,
-such as recalling an earlier visit while planning a return. Omit inferred,
-unstated, uncertain, or unsupported places and occurrences. Do not infer a
-location or occurrence from surrounding events when the transcript does not
-state it.

assets/dnd/npc-interactions/prompts/instructions.md

@@ -1,6 +1,13 @@
-Return the interactions array even when no interaction is established. Every
-record must contain name, kind, and source_refs. Cite transcript ranges that
-support both the NPC identity and the interaction kind.
+Extract Dungeons & Dragons NPC interaction occurrences from the supplied
+transcript. Include an occurrence only when the transcript establishes one
+supplied NPC, one interaction kind, and a coherent passage supporting both.
+Use only names from the supplied NPC registry.
+
+Do not summarize, infer relationships, sentiment, factions, motives, aliases,
+or persistent state. Do not identify player characters, anonymous groups, or
+invented NPCs. Keep occurrences within this transcript chunk. Split records
+when an NPC's interaction kind changes, when combat alignment changes, or when
+an NPC is first mentioned and later becomes present.
 
 Use exactly one kind per occurrence:
 

assets/dnd/npc-interactions/prompts/prompt.yaml

@@ -34,8 +34,6 @@ messages:
     content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./sharedassets/common-dnd-npcs.md
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/npc-interactions/prompts/task.md

@@ -1,16 +0,0 @@
-Extract Dungeons & Dragons NPC interaction occurrences from the supplied
-transcript.
-
-Include an occurrence only when the transcript establishes one supplied NPC,
-one interaction kind, and a coherent passage supporting both. Use only names
-from the supplied NPC registry. The registry helps ground identity but never
-proves that an interaction occurred.
-
-Do not summarize, infer relationships, sentiment, factions, motives, aliases,
-or persistent state. Do not identify player characters, anonymous groups, or
-invented NPCs. Return an empty interactions array when no supplied NPC has an
-evidenced interaction in this transcript passage.
-
-Keep occurrences within this transcript chunk. Split records when an NPC's
-interaction kind changes, when combat alignment changes, or when an NPC is
-first mentioned and later becomes present.