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]`,

docs/internal/llm.md

@@ -134,8 +134,8 @@ reusable content follows it.
 
 Accordingly, the common prefix of all three extraction prompts is system,
 extraction evidence, identity, and campaign references. The NPC prompt then
-renders task, instructions, and transcript. Spell renders immediate resolution,
-NPC registry, catalog, task, instructions, and transcript. Combat renders
+renders task, instructions, and transcript. Spell renders the NPC registry,
+catalog, task, instructions, and transcript. Combat renders
 immediate resolution, NPC registry, task, instructions, and transcript. The
 scene chunker is not an extraction lane: it retains its separate system,
 transcript, campaign-reference, task, and instruction order and marks its

docs/internal/modules.md

@@ -207,16 +207,13 @@ failures therefore stop construction before source parsing or an LLM call;
 campaign references remain separate disambiguation inputs and never become
 source evidence.
 
-The prompt limits each cast to its declaration and immediate resolution; it
-does not follow summoned creatures, persistent effects, or other downstream
-consequences through the scene. Shared extraction-evidence and identity rules
-require transcript-supported factual claims and the most specific in-world
-caster identity, while campaign references only disambiguate source text.
-Effects describe the session as played: model rules knowledge cannot supplement
-or correct the transcript, and nonstandard adjudication is attributed to the GM
-or table rather than stated as a universal rule. Structural source validation
-remains deterministic; semantic claim completeness is enforced through
-extraction policy and evaluation.
+The prompt includes only actual casting events and unambiguous declared casting
+attempts. Spell mentions, plans, rules discussion, and catalog matches without
+a casting event are excluded. Shared extraction-evidence and identity rules
+require transcript-supported caster and spell facts, while the catalog,
+campaign references, and NPC names only disambiguate source text. Structural
+source validation remains deterministic; semantic evidence sufficiency is
+enforced through extraction policy and evaluation.
 
 Both the extractor and deterministic catalog validator expose
 the effective base-plus-overlay semantic digest as scoped prepared-component
@@ -224,23 +221,23 @@ checkpoint identity. Raw overlay provenance independently covers file-byte
 changes, while the semantic digest also invalidates reuse when the embedded
 catalog or catalog composition changes. The extractor additionally fingerprints
 its complete prompt assets and private response schema, so either semantic
-contract changing invalidates previously recorded extraction checkpoints. The separate
-`internal/modules/dnd/codec/spells` package
+contract changing invalidates previously recorded extraction checkpoints. The
+separate `internal/modules/dnd/codec/spells` package
 owns the durable schema and stable JSON representation for artifact kind
 `dnd/spell-list`. The runner keeps the result typed through validators and later
 stages, using the codec only for checkpoint, debug, and output boundaries.
-Shared D&D helpers keep prompt input
-names and source-unit reference conversion consistent with the scene chunker.
+Shared D&D helpers keep prompt input names and source-unit reference conversion
+consistent with the scene chunker.
 
 The extractor also declares the optional `npcs` registry slot and consumes the
 immutable registry boundary from `internal/modules/dnd/npcs/registry`. An
 external registry is prepared before execution; a generated registry is
-validated and supplied at operation time. External bindings may add only
-`npc_registry_digest` and `npc_count` to module metadata and an
-`npc_registry` checkpoint fingerprint. Generated bindings are represented by
+validated and supplied at operation time. Bound external registries add only
+the full `npc_registry_digest` and `npc_count` to module metadata. The local
+`npc_registry` checkpoint fingerprint always covers the names-only projection,
+including its exact unbound value. Generated bindings are represented by
 framework handoff provenance and dependency fingerprints. The unbound prompt
-input is exactly `{"npcs":[]}`, has a projection fingerprint, and has no
-registry provenance.
+input is exactly `{"npcs":[]}` and has no registry provenance.
 The shared NPC grounding fragment is placed immediately after the common
 campaign reference message and is included in the spell prompt fingerprint.
 
@@ -321,9 +318,9 @@ scoped warnings for each mutation or unresolved name.
 After those per-cast changes, it collapses only casts with the same canonical
 spell, case-folded and whitespace-normalized caster, and complete non-empty
 valid source-reference set. It retains the first occurrence and its caster,
-effect, narrative description, and stable order. Unknown names, empty or
-invalid evidence, and adjacent or overlapping but different ranges remain
-unchanged for validation.
+source references, and stable order. Unknown names, empty or invalid evidence,
+and adjacent or overlapping but different ranges remain unchanged for
+validation.
 
 The normalizer exposes the effective catalog digest as its independently scoped
 `effective_catalog` checkpoint fingerprint and reports catalog base ID, digest,
@@ -378,11 +375,11 @@ codec bytes according to its target context. Neither validator calls the LLM.
 ## D&D Spell Validators
 
 All four validators receive `dnd.SpellList` directly. The shape validator
-rejects missing or empty spell fields and empty reference lists. The catalog
-validator defers when shape is invalid, then checks every non-empty spell name
-against the immutable effective SRD and overlay catalog. It accepts normalized
-canonical names and aliases without rewriting the artifact; unknown names
-reject the complete result with bounded, stable index/name diagnostics. The
+rejects a missing list, blank caster or spell names, and empty reference lists.
+The catalog validator defers when shape is invalid, then checks every non-empty
+spell name against the immutable effective SRD and overlay catalog. It accepts
+normalized canonical names and aliases without rewriting the artifact; unknown
+names reject the complete result with bounded, stable index/name diagnostics. The
 source-reference validator defers malformed shapes, validates every cited
 range, and reports all range defects through a bounded aggregate while
 preserving `invalid_source_refs`. The relatedness validator resolves all cited

docs/internal/overview.md

@@ -115,11 +115,13 @@ this package. Domain-neutral prompt filesystem composition lives in
 The `dnd/npcs/registry` package owns the optional `npcs` registry boundary.
 External references are strictly decoded and identity-validated during
 preparation; generated references are decoded and identity-validated at the
-ordered step handoff. Both paths emit canonical registry JSON to operation-time
-spell and combat prompt or normalization requests. The framework records
-generated identity and bounded producer provenance, while the raw external
-reference remains independently tracked by pipeline provenance. An absent
-registry is represented only by the empty prompt value `{"npcs":[]}`. Spell
+ordered step handoff. Both paths retain canonical registry JSON for provenance
+and emit a names-only projection to operation-time spell and combat prompts.
+Combat normalization uses the canonical registry for exact actor lookup. The
+framework records generated identity and bounded producer provenance, while
+the raw external reference remains independently tracked by pipeline
+provenance. An absent registry is represented only by the empty prompt value
+`{"npcs":[]}`. Spell
 and combat consumers use this shared boundary without changing their public
 module contracts.