Document ordered pipeline operations and retire sequential examples

docs/integrations/dnd-npc-artifacts.md

@@ -85,23 +85,43 @@ checks. Relatedness emits bounded warnings when an NPC canonical name or
 alias is not present near its cited transcript text; opaque campaign
 references may explain such a warning but do not become evidence.
 
-## Manifest And Sequential Consumption
+## Manifest And Artifact Handoff
 
 The NPC extractor records prompt and response-schema identities. The durable
 codec records only `npc_count`; raw names, aliases, descriptions, source
 references, and payload bytes stay in the lane file rather than manifest
-metadata. The normalized lane is independently reusable as a file reference:
+metadata. The normalized lane can be consumed by a later ordered step through
+the registered canonical codec:
 
-```sh
-go run ./cmd/notarius run dnd-spells \
-  --config examples/dnd-npc-spell-sequential.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --reference spells.extract.npcs=./npc-output/<run-id>/lanes/npcs.json
+```yaml
+steps:
+  - id: identify-npcs
+    artifacts:
+      npcs:
+        extract: dnd/npcs
+        normalize: dnd/npcs
+  - id: grounded-events
+    references:
+      npcs:
+        artifact:
+          step: identify-npcs
+          lane: npcs
+    artifacts:
+      spells:
+        extract: dnd/spells
+        normalize: dnd/spells
+      combat:
+        extract: dnd/combat-turns
+        normalize: dnd/combat-turns
 ```
 
-The spell extractor strictly decodes and identity-validates this file, accepts
-source references belonging to another session as registry provenance, and
-uses only canonical names and aliases for caster grounding. Those NPC source
-references are never accepted as spell evidence. The spell run's manifest
-keeps raw file provenance under `references` and records only the prepared
-registry's semantic digest and count in extractor metadata.
+The framework hands only an accepted normalized artifact across the barrier. It
+validates the canonical bytes against each consumer slot and clones the
+operation-time reference for the spell and combat consumers. Generated
+provenance records the artifact kind, schema identity, media type, canonical
+digest, size, and producer step/lane/module, but not names, aliases, source
+ranges, or payload bytes. External normalized files remain supported as
+explicit references and retain their file provenance.
+
+NPC source references are registry provenance and are never accepted as spell
+or combat evidence. Current transcript units remain the only event evidence.