Minimize D&D spell extraction contracts

docs/integrations/dnd-spell-artifacts.md

@@ -47,12 +47,10 @@ Each spell cast contains exactly these required fields:
 
 - `caster`: in-world character or creature casting the spell;
 - `spell`: spell name;
-- `effect`: concise spell effect in the scene;
-- `narrative_description`: short description of the spell cast in context;
 - `source_refs`: transcript source references with extractor-assigned source
   IDs and evidence unit ranges. It must contain at least one entry.
 
-All four string fields must be non-empty. `caster` is the canonical in-world
+Both string fields must be non-empty. `caster` is the canonical in-world
 caster, not the human player, transcript speaker, or GM when the associated
 character or creature can be identified. Player and party references may
 disambiguate that identity, but do not independently establish that a cast
@@ -60,16 +58,10 @@ occurred. The `spell` value must resolve through the effective SRD-plus-overlay
 catalog as either a canonical name or alias. Catalog validation accepts aliases
 but does not rewrite them; unknown fields are rejected.
 
-`effect` and `narrative_description` record the casting declaration and its
-immediate resolution as established by the transcript. They do not follow
-summoned creatures, persistent spell effects, or other downstream consequences
-through the rest of the scene. They also do not correct the table from
-published D&D rules or supplement the transcript with model knowledge. When the
-transcript contains a nonstandard or disputed ruling, the artifact may preserve
-the immediate observed resolution and attribute relevant reasoning to the GM or
-table; it must not present that reasoning as a universal game rule. The spell
-catalog is name-recognition policy, not evidence for spell mechanics or
-outcomes.
+The artifact includes an actual casting event or an unambiguous declared
+casting attempt. Spell mentions, hypothetical plans, rules discussion, and
+catalog matches without a casting event are excluded. The spell catalog is a
+name-recognition policy and never evidence that a cast occurred.
 
 ## Source References
 
@@ -79,17 +71,11 @@ The unit IDs must be positive integers present in the input, and the start unit
 must not appear after the end unit. Unknown fields are rejected.
 
 For each cast, the complete `source_refs` collection identifies the transcript
-evidence for every factual claim in `caster`, `spell`, `effect`, and
-`narrative_description`. A cast declaration and its immediate resolution may be
-cited with separate narrow ranges when intervening units are unrelated. A
-reported target, roll, amount, condition, interruption, or immediate outcome
-must be supported by the cited units; otherwise the artifact describes only the
-supported attempt or declaration. Later behavior by summoned creatures,
-recurring effects, and other downstream consequences are outside the cast
-artifact's evidence scope. The deterministic validators establish that ranges
-are structurally valid and that the spell name is related to cited text.
-Semantic claim completeness is an extraction policy and remains subject to
-evaluation rather than deterministic proof.
+evidence for the caster, spell name, and occurrence of the cast or declared
+attempt. The deterministic validators establish that ranges are structurally
+valid and that the spell name is related to cited text. Semantic evidence
+sufficiency is an extraction policy and remains subject to evaluation rather
+than deterministic proof.
 
 Reference slot keys and accepted file types are defined in
 [Configuration](../config.md#implemented-production-modules). References are
@@ -103,8 +89,9 @@ normalized NPC artifact as `application/json`, up to 1 MiB. An external file is
 validated during preparation; an ordered generated binding is validated at the
 step handoff. Both paths use the approved NPC codec and identity policy,
 re-encode canonical durable JSON for registry provenance, and supply only the
-registry's ordered names as the operation-time spell prompt input. It helps the model prefer canonical
-caster names; it does not establish that a spell was cast.
+registry's ordered names as the operation-time spell prompt input. It helps the
+model prefer canonical caster names; it does not establish that a spell was
+cast.
 
 NPC source references may identify the run that produced the registry or any
 other session. They remain registry provenance and are never copied into a
@@ -130,10 +117,9 @@ does not synthesize references or change their boundaries.
 After those per-cast changes, duplicate identity requires the same canonical
 spell name, the same caster after case folding and whitespace normalization,
 and the same complete, non-empty set of source references valid for the source
-document. Only the first occurrence is retained, in stable order. Its caster,
-effect, narrative description, and canonical references are preserved without
-prose merging or source union. Unknown names, empty or invalid evidence, and
-casts with different evidence remain separate.
+document. Only the first occurrence is retained, in stable order. Its caster
+and canonical references are preserved. Unknown names, empty or invalid
+evidence, and casts with different evidence remain separate.
 
 Mutation and duplicate decisions are returned through the normal warnings
 surface. Warning scopes use the merged input index, such as `spell_casts[0]`,