Document ordered pipeline operations and retire sequential examples

docs/integrations/dnd-combat-turn-artifacts.md

@@ -92,6 +92,9 @@ chunk-scoped transcript plus the existing `players`, `party`, and `glossary`
 inputs, and optionally the deprecated `roster` reference through the shared
 party mapping. The optional `npcs` reference is an approved normalized NPC
 artifact used only for identity grounding; it never supplies combat evidence.
+An external file is validated during preparation. In an ordered pipeline, the
+same slot may receive the producer's canonical generated artifact at the step
+handoff.
 
 The private response envelope has the same fields and JSON types as the durable
 turn/action shape except that source references contain only `start_unit_id`
@@ -130,8 +133,10 @@ schema, combat shape, source references, then source relatedness.
 The standalone normalizer uses key `dnd/combat-turns`, requires `merged`,
 provides `normalized`, accepts no options, and accepts only the optional
 structured `npcs` reference. Campaign references are LLM extraction context and
-are not normalizer inputs. The NPC registry is resolved during preparation;
-runtime normalization uses that immutable prepared view.
+are not normalizer inputs. For an external file, the NPC registry is resolved
+during preparation; for a generated binding, it is resolved at the operation-
+time handoff. Runtime normalization uses that immutable prepared or handed-off
+view.
 
 Normalization policy is `dnd.combat_turns.normalize.v1`. It display-normalizes
 actor, summary, declarations, targets, and non-null resolutions; canonicalizes
@@ -143,9 +148,11 @@ merging its actions or prose. Invalid evidence is never eligible for duplicate
 collapse. Every mutation and collapse emits a bounded warning using the merged
 input index in its scope.
 
-The normalizer reports `normalization_policy` and `identity_policy` metadata and
-fingerprints, plus `npc_registry_digest`, `npc_count`, and `npc_registry` only
-when a registry is bound. The normalized-invariants validator is
+The normalizer reports `normalization_policy` and `identity_policy` metadata
+and fingerprints. An external registry may additionally contribute
+`npc_registry_digest` and `npc_count`; generated registry identity is retained
+in framework handoff provenance and dependency fingerprints. The
+normalized-invariants validator is
 `normalize/dnd/combat-turns/invariants`; it defers shape and source-reference
 failures, then checks display normalization, target identity uniqueness,
 canonical evidence ordering, chronology, and duplicate identity. It rejects
@@ -162,9 +169,10 @@ merge validator chain.
 
 The selectable lane uses extractor and normalizer key `dnd/combat-turns`,
 `appendorder` for the typed merger, and the durable codec above. A bound `npcs`
-reference contributes raw-file provenance to the run manifest. Prepared combat
-extractor and normalizer metadata and checkpoint fingerprints contain only the
-NPC registry's semantic digest and count; the registry content, path, and NPC
-source ranges are not copied into combat output. The normalized lane is emitted
-as `lanes/<lane-id>.json` by the JSON output module, and warnings and rejection
-summaries remain in their shared companion files.
+reference contributes raw-file provenance to the run manifest. A generated
+binding contributes artifact kind, schema identity, media type, canonical
+digest, size, and bounded producer provenance. Consumer metadata and checkpoint
+fingerprints contain no registry names, aliases, content, paths, or NPC source
+ranges. The normalized lane is emitted as `lanes/<lane-id>.json` by the JSON
+output module, and warnings and rejection summaries remain in their shared
+companion files.

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.

docs/integrations/dnd-spell-artifacts.md

@@ -97,18 +97,20 @@ addressable through `source_refs`.
 ## Optional NPC Grounding
 
 The `dnd/spells` extractor accepts an optional `npcs` reference containing one
-normalized NPC artifact as `application/json`, up to 1 MiB. Preparation uses
-the approved NPC codec and identity policy to validate the file, re-encodes
-canonical durable JSON, and supplies that JSON as a spell-owned prompt input.
-It helps the model prefer canonical caster names and recognize aliases; it
-does not establish that a spell was cast.
+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, and supply that JSON as an operation-time
+spell prompt input. It helps the model prefer canonical caster names and
+recognize aliases; 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
 spell cast's `source_refs`; every spell evidence range must still identify the
-current transcript. When the slot is absent, the prompt receives exactly
-`{"npcs":[]}` and the run has no NPC reference provenance or NPC checkpoint
-fingerprint.
+current transcript. Generated provenance records producer and canonical
+artifact identity without payload content or a path. When the slot is absent,
+the prompt receives exactly `{"npcs":[]}` and the run has no NPC reference
+provenance or NPC checkpoint fingerprint.
 
 ## Normalization Behavior
 
@@ -190,15 +192,20 @@ identity fields when that module is selected. Overlay origin, media type, byte
 size, and raw digest are recorded separately in the manifest's reference
 provenance; see the [JSON output contract](json-output.md#manifestjson).
 
-The `npc_registry_digest` and `npc_count` fields in the example are present only
-when the optional NPC registry is bound. They contain no NPC names, aliases,
-source references, paths, or raw bytes.
+The `npc_registry_digest` and `npc_count` fields in the example are present for
+an external NPC registry when the extractor publishes its prepared module
+metadata. They contain no NPC names, aliases, source references, paths, or raw
+bytes. A generated registry's identity is instead represented by the framework
+handoff provenance and dependency fingerprint, so the consumer module metadata
+does not duplicate it.
 
 The extractor's prompt hash, private response-schema hash, and effective catalog
 digest also contribute independently scoped semantic checkpoint fingerprints.
 Changing any of those prepared contracts intentionally produces a cold
 checkpoint miss. Fingerprints contain only digests, never prompt, schema,
 catalog, or reference content. When an NPC registry is bound, its semantic
-digest contributes an additional local `npc_registry` fingerprint; the
-manifest metadata contains only that digest and `npc_count`. Raw NPC file
-provenance remains independently recorded in the manifest's `references` list.
+digest contributes an additional local `npc_registry` fingerprint for an
+external binding; the manifest metadata contains only that digest and
+`npc_count`. Raw NPC file provenance remains independently recorded in the
+manifest's `references` list. Generated bindings contribute the canonical
+artifact dependency fingerprint and bounded producer provenance instead.