Prepare the v0.4.0 release

.gitignore

@@ -2,6 +2,7 @@
 notarius
 notarius-output
 workspace/
+.codebase-memory/
 
 # ---> Go
 # If you prefer the allow list template instead of the deny list, see community template:
@@ -73,4 +74,3 @@ Icon
 Network Trash Folder
 Temporary Items
 .apdisk
-

.woodpecker/release.yml

@@ -0,0 +1,33 @@
+when:
+  - event: tag
+
+steps:
+  - name: validate-release
+    image: golang:1.25.5
+    commands:
+      - |
+        set -eu
+
+        version="$CI_COMMIT_TAG"
+        release_note="docs/releases/$version.md"
+
+        if ! printf '%s\n' "$version" | grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null; then
+          printf '%s\n' "invalid release tag: $version" >&2
+          exit 1
+        fi
+        if [ ! -s "$release_note" ]; then
+          printf '%s\n' "missing release note: $release_note" >&2
+          exit 1
+        fi
+        if ! grep -F -x "# Notarius $version" "$release_note" >/dev/null; then
+          printf '%s\n' "release note heading does not match $version" >&2
+          exit 1
+        fi
+        for heading in '## Summary' '## Compatibility' '## Upgrade' '## Changes'; do
+          if ! grep -F -x "$heading" "$release_note" >/dev/null; then
+            printf '%s\n' "release note is missing heading: $heading" >&2
+            exit 1
+          fi
+        done
+
+        ./scripts/check-release-source.sh "$version"

README.md

@@ -1,34 +1,62 @@
 # Notarius
 
-Notarius is a Go CLI for extracting structured artifacts from source material
-with explicit, configurable pipeline modules.
+Notarius is a Go CLI for turning source material into structured artifacts with
+configured extraction pipelines. The implemented D&D workflow reads Seriatim
+transcript JSON and can produce NPC, location, and item registries; their
+source-grounded occurrences; scene descriptions, combat turns, enemy events,
+and spell casts.
 
-The current implementation reads Seriatim transcript JSON, chunks the source
-units, extracts D&D spell-cast artifacts with a Scriptorium-backed LLM runtime,
-and writes JSON output. Add `--debug` when a per-run inspection bundle is
-needed.
+## Quickstart
 
-```sh
-OPENROUTER_API_KEY=... \
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json
-```
+Provide an OpenRouter API key through the environment, then run the maintained
+minimal example:
 
-This invocation uses the maintained example configuration and input. See the
-configuration and operations references for profile selection, credentials, and
-run artifacts.
+~~~
+OPENROUTER_API_KEY=your-api-key \
+  go run ./cmd/notarius run dnd-session \
+    --config examples/dnd-minimal.config.yml \
+    --input examples/seriatim-minimal-transcript.json
+~~~
 
-Useful references:
+The command publishes a JSON output bundle. Its command syntax and exit
+behavior are documented in the [CLI reference](docs/cli.md); configuration,
+credentials, and module selection are owned by the
+[configuration reference](docs/config.md).
 
-- [CLI reference](docs/cli.md)
-- [Configuration reference](docs/config.md)
-- [Operations](docs/operations.md)
-- [Seriatim input contract](docs/integrations/seriatim.md)
-- [JSON output contract](docs/integrations/json-output.md)
-- [D&D spell artifact contract](docs/integrations/dnd-spell-artifacts.md)
-- [Developer guide](docs/development.md)
-- [Internal implementation docs](docs/internal/overview.md)
-- [Minimal D&D configuration](examples/dnd-minimal.config.yml)
-- [Complete D&D configuration](examples/dnd-complete.config.yml)
-- [Maintained example input](examples/seriatim-minimal-transcript.json)
+For the complete ordered D&D workflow, use
+[the complete configuration](examples/dnd-complete.config.yml) with
+[its synthetic transcript](examples/dnd-complete-transcript.json). It
+demonstrates all implemented D&D lanes and the supporting campaign references.
+
+## Install A Source Release
+
+Install a pinned source release with Go:
+
+~~~
+GOWORK=off go install \
+  gitea.maximumdirect.net/eric/notarius/cmd/notarius@<tag>
+~~~
+
+Replace `<tag>` with a stable release tag such as `vMAJOR.MINOR.PATCH`. The
+installed command's diagnostic version is described in the [CLI
+reference](docs/cli.md); maintainers preparing a release should follow [Source
+Releases](docs/release.md).
+
+## Documentation
+
+- [CLI reference](docs/cli.md) — commands, flags, output streams, and exits.
+- [Configuration reference](docs/config.md) — configuration files, profiles,
+  validation, and module selection.
+- [Operations](docs/operations.md) — output, state, recovery, and debug
+  handling.
+- [Integration contracts](docs/integrations/) — Seriatim input and published
+  artifact formats.
+- [Subprocess consumer guide](docs/consumers/subprocess.md) — invoke Notarius
+  from an orchestrator and consume a published result.
+- [Complete D&D consumer guide](docs/consumers/dnd-pipeline.md) — run the full
+  D&D pipeline as a subprocess and discover its structured artifacts.
+- [Internal overview](docs/internal/overview.md) — implemented component map
+  for maintainers.
+- [Developer guide](docs/development.md) — contributor orientation and
+  validation guidance.
+- [Future work](docs/roadmap/future.md) — unimplemented ideas and priorities.

assets/dnd/combat-turns/prompts/instructions.md

@@ -0,0 +1,18 @@
+Extract Dungeons & Dragons combat-turn artifacts from the supplied transcript.
+Include a record only when the transcript establishes that an in-world
+participant takes a combat turn or performs a discrete interrupting combat
+event. Keep events in transcript chronology; place an interrupting event where
+it occurs.
+
+Exclude initiative setup without a turn or combat event, tactical planning,
+table talk, rules lookup, hypothetical events, abandoned intentions, recaps
+outside the current passage, and downstream consequences. Do not infer combat
+events from Dungeons & Dragons rules knowledge. Preserve the session as played
+and attribute relevant nonstandard rulings to the GM or table. Unmatched actors
+remain permitted.
+
+Treat each record as one turn-level event and keep its supporting transcript
+evidence together. Use `turn` for a regular combat turn, `reaction` for an
+off-turn reaction, `legendary_action` for a legendary action,
+`lair_action` for a lair action, and `other` for another discrete combat
+event that does not fit those categories.

assets/dnd/combat-turns/prompts/prompt.yaml

@@ -1,6 +1,6 @@
 id: dnd.combat_turns
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -14,36 +14,32 @@ inputs:
   - name: glossary
     required: false
     content_type: text/plain
-  - name: npcs
+  - name: npc_registry
     required: false
     content_type: application/json
 messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
-  - role: user
-    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./sharedassets/common-dnd-npcs.md
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-npc-registry.md
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
 output:
   format: json
   validation_mode: json_schema
   schema_path: dnd_combat_turns_llm.v1.json
-  repair_attempts: 0
+  repair_attempts: 1

assets/dnd/enemy-events/prompts/combat-grounding.md

@@ -0,0 +1,12 @@
+Compact combat grounding is supplied below. It can guide attention and
+disambiguation, but it is not evidence. Do not derive an event, subject,
+outcome, or source range from either list. The current transcript alone must
+directly establish every returned event.
+
+Combat-turn grounding:
+
+{{ input "combat_turns" }}
+
+Named combat-opponent grounding:
+
+{{ input "npc_occurrences" }}

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

@@ -0,0 +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, or a scene ending.

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

@@ -0,0 +1,53 @@
+id: dnd.enemy_events
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: transcript
+    required: true
+    content_type: application/json
+  - name: players
+    required: false
+    content_type: text/plain
+  - name: party
+    required: false
+    content_type: text/plain
+  - name: glossary
+    required: false
+    content_type: text/plain
+  - name: npc_registry
+    required: true
+    content_type: application/json
+  - name: combat_turns
+    required: true
+    content_type: application/json
+  - name: npc_occurrences
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-identity.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-references.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-npc-registry.md
+  - role: user
+    content_file: ./combat-grounding.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: dnd_enemy_events_llm.v1.json
+  repair_attempts: 1

assets/dnd/enemy-events/schemas/dnd_enemy_events_llm.v1.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "notarius.dnd.item_events.llm",
+  "$id": "notarius.dnd.enemy_events.llm",
   "type": "object",
   "additionalProperties": false,
   "required": ["events"],
@@ -14,18 +14,15 @@
         "properties": {
           "name": {"type": "string"},
           "kind": {"type": "string"},
-          "quantity": {"type": "integer"},
-          "from": {"type": "string"},
-          "to": {"type": "string"},
           "source_refs": {
             "type": "array",
             "items": {
               "type": "object",
               "additionalProperties": false,
-              "required": ["start_segment", "end_segment"],
+              "required": ["start_unit_id", "end_unit_id"],
               "properties": {
-                "start_segment": {"type": "integer"},
-                "end_segment": {"type": "integer"}
+                "start_unit_id": {"type": "integer"},
+                "end_unit_id": {"type": "integer"}
               }
             }
           }

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

@@ -0,0 +1,30 @@
+Extract meaningful Dungeons & Dragons item and currency occurrences: discoveries and changes
+in party possession established by the transcript. This is an occurrence history,
+not an inventory or ledger: do not calculate balances, resolve item identity
+across records, or infer ownership that the transcript does not establish.
+
+For every occurrence, use the supplied canonical item `name`. Record a stated
+quantity as an integer and leave it null when the transcript does not state
+one. Preserve the stated currency denomination through the selected canonical
+registry name.
+
+Use `discovered` when the party learns of or encounters an item without
+establishing possession. Use `acquired` when the party or a party member gains
+possession. Use `lost` when party possession ends through a gift, sale, payment,
+theft, abandonment, or destruction not caused by intended use. Use `consumed`
+when intended use depletes an expendable item. Monetary spending, purchases, and
+payments are always `lost`, not `consumed`. Classify currency as `consumed` only
+when the transcript explicitly describes it being physically destroyed or
+expended as a non-payment component. Use `transferred` only when possession
+moves between two distinct named party members.
+
+Return both `from` and `to` for every occurrence, using `null` when a holder does not
+apply. For `discovered`, set both holders to `null`. For `acquired`, set `from`
+to `null` and provide `to`; for `lost` and `consumed`, provide `from` and set
+`to` to `null`; and for `transferred`, provide both holders. Use `party` only
+for collective or unresolved party possession, never for either side of a
+transfer. Do not emit a transfer for a gift, sale, or payment outside the party.
+
+Ordinary non-depleting use is not an occurrence. Do not infer acquisition from a
+discovery, or discovery from an acquisition: emit both only when each is
+independently established.

assets/dnd/item-occurrences/prompts/item-registry.md

@@ -0,0 +1,6 @@
+Use the supplied item registry only to ground each occurrence. Every record
+must use one registry item's canonical `name`; do not invent, rename, merge,
+or infer registry items. The registry is not transcript evidence: cite only the
+current transcript chunk in `source_refs`.
+
+{{ input "item_registry" }}

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

@@ -1,6 +1,6 @@
-id: dnd.npc_interactions
+id: dnd.item_occurrences
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -14,36 +14,32 @@ inputs:
   - name: glossary
     required: false
     content_type: text/plain
-  - name: npcs
+  - name: item_registry
     required: true
     content_type: application/json
 messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
-  - role: user
-    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./sharedassets/common-dnd-npcs.md
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
+  - role: user
+    content_file: ./item-registry.md
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
 output:
   format: json
   validation_mode: json_schema
-  schema_path: dnd_npc_interactions_llm.v1.json
-  repair_attempts: 0
+  schema_path: dnd_item_occurrences_llm.v1.json
+  repair_attempts: 1

assets/dnd/item-occurrences/schemas/dnd_item_occurrences_llm.v1.json

@@ -0,0 +1,36 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "notarius.dnd.item_occurrences.llm",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["occurrences"],
+  "properties": {
+    "occurrences": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["name", "kind", "quantity", "from", "to", "source_refs"],
+        "properties": {
+          "name": {"type": "string"},
+          "kind": {"type": "string"},
+          "quantity": {"type": ["integer", "null"]},
+          "from": {"type": ["string", "null"]},
+          "to": {"type": ["string", "null"]},
+          "source_refs": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["start_unit_id", "end_unit_id"],
+              "properties": {
+                "start_unit_id": {"type": "integer"},
+                "end_unit_id": {"type": "integer"}
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}

assets/dnd/item-registry/extract/prompts/instructions.md

@@ -0,0 +1,12 @@
+Extract only items established by the provided Dungeons & Dragons transcript.
+
+Include named unique items, concrete reusable item types, and stable unique
+designations. Record each currency denomination separately when it is
+established, such as copper pieces, silver pieces, gold pieces, or platinum
+pieces. Do not use capitalization as an eligibility test. Keep distinct names
+and designations as separate candidates; do not merge aliases or invent
+qualifiers.
+
+Do not record vague categories such as "loot", "treasure", or "some gear";
+generic weapons; inferred properties; quantities; or inferred uniqueness. Omit
+uncertain or unsupported items.

assets/dnd/item-registry/extract/prompts/prompt.yaml

@@ -1,6 +1,6 @@
-id: dnd.npcs
+id: dnd.item_registry
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -17,26 +17,24 @@ inputs:
 messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
-  - role: user
-    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
 output:
   format: json
   validation_mode: json_schema
-  schema_path: dnd_npcs_llm.v1.json
-  repair_attempts: 0
+  schema_path: dnd_item_registry_llm.v1.json
+  repair_attempts: 1

assets/dnd/item-registry/extract/schemas/dnd_item_registry_llm.v1.json

@@ -0,0 +1,32 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "notarius.dnd.item_registry.llm",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["items"],
+  "properties": {
+    "items": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["name", "source_refs"],
+        "properties": {
+          "name": {"type": "string"},
+          "source_refs": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["start_unit_id", "end_unit_id"],
+              "properties": {
+                "start_unit_id": {"type": "integer"},
+                "end_unit_id": {"type": "integer"}
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}

assets/dnd/item-registry/normalize/prompts/instructions.md

@@ -0,0 +1,9 @@
+Determine whether candidates identify the same item type or unique designation
+using their contextual labels and cited transcript windows. Do not treat nearby
+evidence, similar objects, or a shared owner as sufficient.
+
+Keep currency denominations and materially different item types separate. Keep
+uncertain aliases separate. Do not infer an item property or uniqueness.
+
+When selecting a canonical display name, choose one supplied candidate name
+that is the clearest established designation.

assets/dnd/item-registry/normalize/prompts/prompt.yaml

@@ -1,6 +1,6 @@
-id: dnd.npcs.normalize
+id: dnd.item_registry.normalize
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: candidates
     required: true
@@ -12,21 +12,19 @@ messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
   - role: user
-    content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
-  - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/protocol.md
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./candidates.md
+    content_file: ./sharedassets/candidates.md
   - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
+    content_file: ./sharedassets/transcript-windows.md
+    cache_control:
+      type: ephemeral
 output:
   format: json
   validation_mode: json_schema
-  schema_path: dnd_npcs_normalize_llm.v1.json
-  repair_attempts: 0
+  schema_path: semantic_reconciliation_llm.v1.json
+  repair_attempts: 1

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

@@ -0,0 +1,34 @@
+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 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.
+
+A generic phrase in the current chunk may refer to a supplied named registry
+location only when the chunk's context supports that coreference. It must not
+create a registry location, and registry content or provenance must never
+replace current-chunk evidence.
+
+For every occurrence, return the exact selector from the location registry:
+the canonical `name`, plus an empty `registry_refs` array for a unique name or
+the complete ordered `registry_refs` array for a repeated name. Registry ranges
+and context identify the location only; they are not occurrence evidence.
+
+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/location-registry.md

@@ -0,0 +1,11 @@
+A contextual location registry is provided below for identity grounding. It may
+be empty. Every record supplies a canonical display name. A name that appears
+once is selected with that name and an empty `registry_refs` array. A repeated
+name is selected only by copying both its name and its complete, ordered
+`registry_refs` array exactly as supplied.
+
+Registry content is context, not occurrence evidence. Do not derive an
+occurrence or `source_refs` range from the registry. Do not invent a location
+or selector that is absent from it.
+
+{{ input "location_registry" }}

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

@@ -0,0 +1,45 @@
+id: dnd.location_occurrences
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: transcript
+    required: true
+    content_type: application/json
+  - name: players
+    required: false
+    content_type: text/plain
+  - name: party
+    required: false
+    content_type: text/plain
+  - name: glossary
+    required: false
+    content_type: text/plain
+  - name: location_registry
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-identity.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-references.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
+  - role: user
+    content_file: ./location-registry.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: dnd_location_occurrences_llm.v1.json
+  repair_attempts: 1

assets/dnd/location-occurrences/schemas/dnd_location_occurrences_llm.v1.json

@@ -0,0 +1,45 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "notarius.dnd.location_occurrences.llm",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["occurrences"],
+  "properties": {
+    "occurrences": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["name", "registry_refs", "kind", "source_refs"],
+        "properties": {
+          "name": {"type": "string"},
+          "registry_refs": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["start_unit_id", "end_unit_id"],
+              "properties": {
+                "start_unit_id": {"type": "integer", "minimum": 1},
+                "end_unit_id": {"type": "integer", "minimum": 1}
+              }
+            }
+          },
+          "kind": {"enum": ["visited", "planned", "recalled", "mentioned"]},
+          "source_refs": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["start_unit_id", "end_unit_id"],
+              "properties": {
+                "start_unit_id": {"type": "integer"},
+                "end_unit_id": {"type": "integer"}
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}

assets/dnd/location-registry/extract/prompts/instructions.md

@@ -0,0 +1,13 @@
+Extract only physical places established by the provided Dungeons & Dragons
+transcript that have a stable proper name or unique in-world designation. This
+includes named planes, regions, settlements, districts, buildings, rooms,
+landmarks, routes, and geographic features.
+
+Do not create a registry location for generic, temporary, relative, or merely
+descriptive phrases, including "the room", "the bar", "the hallway",
+"outside", and "upstairs". Do not use capitalization as an eligibility test.
+Keep aliases and nested places when the transcript identifies them; do not merge
+or invent qualifiers for similarly named places.
+
+Exclude people, creatures, objects, organizations, abstract concepts, and
+places merely inferred from an event. Omit uncertain or unsupported places.

assets/dnd/location-registry/extract/prompts/prompt.yaml

@@ -1,6 +1,6 @@
-id: dnd.item_events
+id: dnd.location_registry
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -17,26 +17,24 @@ inputs:
 messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
-  - role: user
-    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
 output:
   format: json
   validation_mode: json_schema
-  schema_path: dnd_item_events_llm.v1.json
-  repair_attempts: 0
+  schema_path: dnd_location_registry_llm.v1.json
+  repair_attempts: 1

assets/dnd/location-registry/extract/schemas/dnd_location_registry_llm.v1.json

@@ -0,0 +1,32 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "notarius.dnd.location_registry.llm",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["locations"],
+  "properties": {
+    "locations": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["name", "source_refs"],
+        "properties": {
+          "name": {"type": "string"},
+          "source_refs": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["start_unit_id", "end_unit_id"],
+              "properties": {
+                "start_unit_id": {"type": "integer"},
+                "end_unit_id": {"type": "integer"}
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}

assets/dnd/location-registry/normalize/prompts/instructions.md

@@ -0,0 +1,8 @@
+Determine whether candidates identify the same physical place using their
+contextual labels and cited transcript windows. Do not treat matching names,
+nearby evidence, nested places, or generic labels as sufficient.
+
+Keep parent and child places separate, as well as similarly named places and
+uncertain aliases.
+
+When selecting a canonical display name, prefer the clearest established name.

assets/dnd/location-registry/normalize/prompts/prompt.yaml

@@ -0,0 +1,30 @@
+id: dnd.location_registry.normalize
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: candidates
+    required: true
+    content_type: application/json
+  - name: transcript
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/protocol.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/candidates.md
+  - role: user
+    content_file: ./sharedassets/transcript-windows.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: semantic_reconciliation_llm.v1.json
+  repair_attempts: 1

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

@@ -1,6 +1,14 @@
-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 occurrences from the supplied
+transcript. Include an occurrence only when the transcript establishes one
+supplied NPC, one occurrence kind, and a coherent passage supporting both.
+Use the supplied canonical NPC `name`; never invent or substitute a similar
+name. Cite current-transcript evidence for every occurrence.
+
+Do not summarize, infer relationships, sentiment, factions, motives, aliases,
+or persistent state. Do not identify player characters, anonymous groups, or
+invented NPCs. Split records when an NPC's occurrence 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-occurrences/prompts/prompt.yaml

@@ -0,0 +1,45 @@
+id: dnd.npc_occurrences
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: transcript
+    required: true
+    content_type: application/json
+  - name: players
+    required: false
+    content_type: text/plain
+  - name: party
+    required: false
+    content_type: text/plain
+  - name: glossary
+    required: false
+    content_type: text/plain
+  - name: npc_registry
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-identity.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-references.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-npc-registry.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: dnd_npc_occurrences_llm.v1.json
+  repair_attempts: 1

assets/dnd/npc-occurrences/schemas/dnd_npc_occurrences_llm.v1.json

@@ -1,11 +1,11 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "notarius.dnd.npc_interactions.llm",
+  "$id": "notarius.dnd.npc_occurrences.llm",
   "type": "object",
   "additionalProperties": false,
-  "required": ["interactions"],
+  "required": ["occurrences"],
   "properties": {
-    "interactions": {
+    "occurrences": {
       "type": "array",
       "items": {
         "type": "object",

assets/dnd/npc-registry/extract/prompts/instructions.md

@@ -0,0 +1,19 @@
+Extract the individually identifiable Dungeons & Dragons non-player characters
+established by the provided transcript.
+
+Include an in-world non-PC only when the transcript factually establishes a
+proper name or a stable, individually distinguishing title or alias. A factual
+third-party mention establishes that identity even when the NPC is not
+physically present, does not speak, and takes no direct action in this chunk.
+Record only the NPC identity and the transcript evidence that establishes it;
+do not infer or classify a separate occurrence.
+
+Exclude human players, transcript speakers, and the GM as out-of-world people;
+player characters identified by the player or party references; names used only
+in hypothetical, speculative, or imagined examples; corrected transcription
+mistakes; anonymous or generic roles; indistinguishable crowds or groups;
+invented descriptive labels; and temporary summoned creatures or spell effects
+without a persistent individual identity.
+
+Preserve observed display spelling. Do not invent a label for an anonymous
+creature, crowd, or generic role.

assets/dnd/npc-registry/extract/prompts/prompt.yaml

@@ -0,0 +1,40 @@
+id: dnd.npc_registry
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: transcript
+    required: true
+    content_type: application/json
+  - name: players
+    required: false
+    content_type: text/plain
+  - name: party
+    required: false
+    content_type: text/plain
+  - name: glossary
+    required: false
+    content_type: text/plain
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-identity.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-references.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: dnd_npc_registry_llm.v1.json
+  repair_attempts: 1

assets/dnd/npc-registry/extract/schemas/dnd_npc_registry_llm.v1.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "notarius.dnd.npcs.llm",
+  "$id": "notarius.dnd.npc_registry.llm",
   "type": "object",
   "additionalProperties": false,
   "required": ["npcs"],

assets/dnd/npc-registry/normalize/prompts/instructions.md

@@ -0,0 +1,11 @@
+Determine whether candidates refer to the same individual using their
+contextual labels and cited transcript windows. Preserve distinct individuals
+even when their names are similar or their contextual descriptions are
+identical.
+
+When selecting a canonical display name, prefer a complete, stable proper name
+over an abbreviation. Prefer an unadorned proper name over that name plus a
+contextual class, role, title, or relationship descriptor unless the transcript
+establishes the descriptor as part of the person's name. A longer display name
+is not inherently more canonical; for example, do not prefer `Captain Aria`
+over `Aria` solely because it includes the contextual title `Captain`.

assets/dnd/npc-registry/normalize/prompts/prompt.yaml

@@ -0,0 +1,30 @@
+id: dnd.npc_registry.normalize
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: candidates
+    required: true
+    content_type: application/json
+  - name: transcript
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/protocol.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./sharedassets/candidates.md
+  - role: user
+    content_file: ./sharedassets/transcript-windows.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: semantic_reconciliation_llm.v1.json
+  repair_attempts: 1

assets/dnd/profiles/dnd-extraction.yaml

@@ -0,0 +1,5 @@
+id: dnd-extraction
+backend: openrouter
+model: openai/gpt-5.6-luna
+timeout_seconds: 240
+service_tier: flex

assets/dnd/scene-descriptions/prompts/instructions.md

@@ -1,4 +1,9 @@
-Choose exactly one kind:
+Describe exactly one accepted Dungeons & Dragons scene from the supplied
+transcript chunk. The complete chunk is the evidence boundary: do not split it
+into multiple scenes or use facts that are not supported by it.
+
+Return one kind, one concise title, and one concise summary. Choose exactly one
+kind:
 
 - combat: active combat materially organizes the scene, including
   initiative-like exchanges or sustained hostile action. Planning a fight or
@@ -37,8 +42,4 @@ must not invent a proper noun.
 The summary must briefly state the main activity and material transition or
 outcome established within the accepted chunk. Do not add analysis, inferred
 motives, hidden state, future consequences, relationship claims, or facts from
-outside the chunk. Campaign references may disambiguate names but never add
-events or lore.
-
-Do not return identifiers, source identifiers, source ranges, unit identifiers,
-participants, confidence, or any fields besides kind, title, and summary.
+outside the chunk.

assets/dnd/scene-descriptions/prompts/prompt.yaml

@@ -1,6 +1,6 @@
 id: dnd.scene_descriptions
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -19,22 +19,20 @@ messages:
     content_file: ./sharedassets/common-dnd-system.md
   - role: user
     content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
 output:
   format: json
   validation_mode: json_schema
   schema_path: dnd_scene_descriptions_llm.v1.json
-  repair_attempts: 0
+  repair_attempts: 1

assets/dnd/scenes/prompts/instructions.md

@@ -1,5 +1,5 @@
-Divide the provided transcript into coherent Dungeons & Dragons scenes for the
-`dnd/scenes` chunk module.
+Divide the complete provided transcript into coherent Dungeons & Dragons scenes
+for the `dnd/scenes` chunk module.
 
 A scene is a coherent unit of play. Start a new scene when the transcript
 establishes a meaningful change in location, objective, threat, activity,
@@ -13,6 +13,7 @@ Do not split a scene merely because a speaker or combat round changes, a
 routine turn occurs, or the table briefly digresses. Prefer fewer coherent
 scenes over speculative or fine-grained boundaries.
 
-Return only inclusive `start_unit_id` and `end_unit_id` endpoints for each
-scene. Do not return titles, modes, participants, summaries, boundary notes,
-confidence, caveats, final chunk IDs, or chunk indexes.
+Cover the complete transcript from its first source unit to its last. Return
+scenes in source-unit order with no gaps or overlaps. Use only positive integer
+source-unit IDs from the transcript, and give every scene one inclusive
+`start_unit_id` and one inclusive `end_unit_id`.

assets/dnd/scenes/prompts/prompt.yaml

@@ -1,6 +1,6 @@
 id: dnd.scenes
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -17,20 +17,18 @@ inputs:
 messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript-full.md
+    cache_control:
+      type: ephemeral
 output:
   format: json
   validation_mode: json_schema
-  schema_path: dnd_scenes.v1.json
-  repair_attempts: 0
+  schema_path: dnd_scenes_llm.v1.json
+  repair_attempts: 1

assets/dnd/scenes/schemas/dnd_scenes_llm.v1.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "notarius.dnd.scenes",
+  "$id": "notarius.dnd.scenes.llm",
   "type": "object",
   "additionalProperties": false,
   "required": ["scenes"],

assets/dnd/shared/prompts/common-dnd-extraction-evidence.md

@@ -0,0 +1,6 @@
+Transcript units are the only evidence for extracted events and factual claims.
+Every reported factual claim must be supported by cited transcript units. Use
+integer `start_unit_id` and `end_unit_id` values from the transcript.
+
+When supporting evidence is non-contiguous, use multiple narrow ranges rather
+than a broad range that bridges unrelated conversation.

assets/dnd/shared/prompts/common-dnd-npc-registry.md

@@ -7,4 +7,4 @@ participants, effects, or source references from the registry. Registry source
 references describe registry provenance and may belong to another session; they
 are never evidence for the current transcript.
 
-{{ input "npcs" }}
+{{ input "npc_registry" }}

assets/dnd/shared/prompts/common-dnd-system.md

@@ -0,0 +1,5 @@
+You process Dungeons & Dragons gameplay transcripts.
+
+As input, you will receive one or more portions of a transcript. The transcript may contain transcription errors, repeated lines, incomplete sentences, and misheard proper nouns.
+
+Return exactly one JSON object that conforms to the configured response schema, with no explanatory prose.

assets/dnd/shared/prompts/common-dnd-transcript-chunk.md

@@ -0,0 +1,3 @@
+One extraction chunk from a Dungeons & Dragons gameplay transcript is provided below. Report and infer only what is within this chunk. Its unit IDs retain their source-wide meaning.
+
+{{ input "transcript" }}

assets/dnd/shared/prompts/common-dnd-transcript-full.md

@@ -0,0 +1,3 @@
+The complete ordered transcript of this Dungeons & Dragons gameplay session is provided below.
+
+{{ input "transcript" }}

assets/dnd/spells/prompts/instructions.md

@@ -0,0 +1,14 @@
+Extract Dungeons & Dragons spell-cast artifacts from the provided transcript.
+Include an actual casting event or an unambiguous declared casting attempt.
+Exclude spell mentions, hypothetical plans, rules discussion, and catalog
+matches that do not establish a casting event in the transcript.
+
+For every extracted cast, the transcript evidence must collectively support the
+in-world caster, the spell, and the fact that the cast or declared attempt
+occurred.
+
+Attribute every cast to its in-world caster. Map first-person player speech to
+the associated player character, and attribute a spell narrated by the GM to
+the in-world creature that casts it. If the caster cannot be resolved, use only
+the most specific in-world identity supported by the transcript; do not invent
+a name.

assets/dnd/spells/prompts/prompt.yaml

@@ -1,6 +1,6 @@
 id: dnd.spells
 version: "v1"
-default_profile: gemini-2-flash
+default_profile: dnd-extraction
 inputs:
   - name: transcript
     required: true
@@ -17,38 +17,34 @@ inputs:
   - name: glossary
     required: false
     content_type: text/plain
-  - name: npcs
+  - name: npc_registry
     required: false
     content_type: application/json
 messages:
   - role: system
     content_file: ./sharedassets/common-dnd-system.md
-  - role: user
-    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
     content_file: ./sharedassets/common-dnd-identity.md
-    cache_control:
-      type: ephemeral
   - role: user
     content_file: ./sharedassets/common-dnd-references.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./sharedassets/common-dnd-npcs.md
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
     cache_control:
       type: ephemeral
   - role: user
-    content_file: ./catalog.md
+    content_file: ./sharedassets/common-dnd-extraction-evidence.md
   - role: user
-    content_file: ./task.md
+    content_file: ./sharedassets/common-dnd-npc-registry.md
+  - role: user
+    content_file: ./spell-catalog.md
   - role: user
     content_file: ./instructions.md
     cache_control:
       type: ephemeral
-  - role: user
-    content_file: ./sharedassets/common-dnd-transcript.md
 output:
   format: json
   validation_mode: json_schema
   schema_path: dnd_spells_llm.v1.json
-  repair_attempts: 0
+  repair_attempts: 1

assets/dnd/spells/prompts/spell-catalog.md

@@ -0,0 +1,6 @@
+The spell catalog for this extraction is provided below as JSON. Each entry
+lists a `canonical_name` and its recognized `aliases`. If the transcript uses
+an alias, select that entry's `canonical_name`. Return spell names using the
+canonical spelling exactly; never return an alias as a spell name.
+
+{{ input "spell_catalog" }}

assets/dnd/spells/schemas/dnd_spells_llm.v1.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "notarius.dnd.spells",
+  "$id": "notarius.dnd.spells.llm",
   "type": "object",
   "additionalProperties": false,
   "required": ["spell_casts"],

assets/generic/normalize/deduplication/prompts/candidates.md

@@ -0,0 +1,3 @@
+Candidate material:
+
+{{ input "candidates" }}

assets/generic/normalize/deduplication/prompts/instructions.md

@@ -0,0 +1,5 @@
+Identify only high-confidence duplicate entities among the supplied candidates.
+
+Preserve distinct entities even when their names are similar. Treat contextual descriptions and transcript evidence as supporting material, not as permission to merge ambiguous records.
+
+When several records are duplicates, choose as canonical the candidate with the clearest stable identity. Prefer a complete proper name over an abbreviation, and prefer an unadorned proper name over one with incidental descriptors unless the evidence establishes those descriptors as part of the name. A longer name is not inherently more canonical.

assets/generic/normalize/deduplication/prompts/prompt.yaml

@@ -0,0 +1,27 @@
+id: generic.semantic_reconciliation
+version: "v1"
+inputs:
+  - name: candidates
+    required: true
+    content_type: application/json
+  - name: transcript
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./system.md
+  - role: user
+    content_file: ./protocol.md
+  - role: user
+    content_file: ./instructions.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./candidates.md
+  - role: user
+    content_file: ./transcript-windows.md
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: semantic_reconciliation_llm.v1.json
+  repair_attempts: 1

assets/generic/normalize/deduplication/prompts/protocol.md

@@ -0,0 +1,7 @@
+Use only the positive integer `candidate_id` values supplied in the candidate material.
+
+Return a duplicate group only when the evidence supports that every selected candidate describes the same underlying entity. Each group must contain at least two distinct candidate IDs, and its `canonical_candidate_id` must be one of those IDs. A candidate may appear in at most one group.
+
+Omit uncertain matches and candidates that should remain distinct. Do not invent candidates or infer an ID from list position. An empty `duplicate_groups` array is valid.
+
+The response must conform exactly to the selected JSON schema. Return IDs only: do not copy candidate names, evidence, transcript text, source identifiers, or source ranges into the response.

assets/generic/normalize/deduplication/prompts/system.md

@@ -0,0 +1,2 @@
+You reconcile structured records that may describe the same underlying entity.
+Follow the supplied protocol and return only the requested structured result.

assets/generic/normalize/deduplication/prompts/transcript-windows.md

@@ -0,0 +1,3 @@
+Transcript evidence windows:
+
+{{ input "transcript" }}

assets/generic/normalize/deduplication/schemas/semantic_reconciliation_llm.v1.json

@@ -0,0 +1,32 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "notarius.generic.semantic_reconciliation.llm",
+  "title": "notarius_semantic_reconciliation_llm_v1",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["duplicate_groups"],
+  "properties": {
+    "duplicate_groups": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["candidate_ids", "canonical_candidate_id"],
+        "properties": {
+          "candidate_ids": {
+            "type": "array",
+            "minItems": 2,
+            "items": {
+              "type": "integer",
+              "minimum": 1
+            }
+          },
+          "canonical_candidate_id": {
+            "type": "integer",
+            "minimum": 1
+          }
+        }
+      }
+    }
+  }
+}

assets/package.go

@@ -0,0 +1,15 @@
+// Package assets exposes embedded LLM-facing content.
+package assets
+
+import (
+	"embed"
+	"io/fs"
+)
+
+//go:embed dnd generic
+var embedded embed.FS
+
+// FS returns the embedded read-only asset filesystem.
+func FS() fs.FS {
+	return embedded
+}

docs/adr/0004-package-modules-by-domain.md

@@ -1,6 +1,6 @@
 # ADR-0004: Package modules by domain, not by stage
 
-**Status:** Accepted
+**Status:** Accepted — its asset-co-location rule is superseded by [ADR-0011](0011-centralize-llm-assets.md); its domain-first module packaging decision remains accepted.
 **Date:** 2026-07-13
 
 ## Context

docs/adr/0010-workload-oriented-llm-profile-defaults.md

@@ -0,0 +1,49 @@
+# ADR-0010: Use workload-oriented LLM profile defaults
+
+**Status:** Accepted
+**Date:** 2026-08-03
+
+## Context
+
+LLM-backed D&D operations share an execution-policy choice, but repeating a
+provider or model-named profile on every module binding ties pipeline structure
+to a deployment decision. Different environments may require different model,
+backend, timeout, or reasoning settings while retaining the same workload.
+
+Notarius also needs a usable default for maintained D&D prompts without making
+an operator profile mandatory. That default must remain owned by the D&D
+family, while generic LLM infrastructure stays unaware of domain-specific
+policy.
+
+## Decision
+
+Pipelines may name one workload-oriented default profile, inherited only by
+selected LLM-backed bindings and validators. Binding-level profile IDs remain
+intentional exceptions, and the run-wide CLI profile override has highest
+precedence.
+
+The D&D family owns an embedded fallback profile named `dnd-extraction`.
+Operators may provide a complete profile with the same ID through a PromptKit
+filesystem source. PromptKit selects the higher-precedence matching definition;
+Notarius does not merge profile documents. Production, development, and local
+deployments can therefore use different execution policy behind one unchanged
+pipeline ID.
+
+## Alternatives considered
+
+- Repeat a model-named profile on every binding. This makes routine deployment
+  policy changes noisy and obscures the shared workload intent.
+- Require every deployment to install a profile file. This adds configuration
+  friction and leaves maintained D&D prompts without an application-owned
+  fallback.
+- Put D&D profile policy in generic LLM infrastructure. This breaks domain
+  ownership and makes generic code depend on one workload.
+
+## Consequences
+
+Pipeline configuration expresses workload intent rather than a specific
+provider or model. Operators can replace the complete execution policy without
+editing bindings, while binding-level and run-wide exceptions remain available.
+Profile changes affect resolved pipeline and checkpoint identity, so they may
+intentionally cause work to be recomputed. The D&D fallback becomes a
+maintained application execution-policy asset.

docs/adr/0011-centralize-llm-assets.md

@@ -0,0 +1,69 @@
+# ADR-0011: Centralize LLM-facing assets in a content-only package
+
+**Status:** Accepted
+**Date:** 2026-08-05
+
+## Context
+
+LLM prompts, private response schemas, generic schemas, and fallback profiles
+are authored and reviewed as content, but package-local embedding scattered that
+content across implementation trees. Finding all of the assets that contribute
+to a prompt family required navigating code ownership boundaries rather than a
+single discoverable content boundary.
+
+The repository must retain module ownership of prompt semantics, schema
+identities, registration, and prompt-cache behavior. Durable artifact schemas
+and non-LLM domain data have different compatibility and ownership rules, so
+they must not move merely because they are embedded files.
+
+## Decision
+
+LLM-facing content is embedded by the root `assets` package. It is a data-only
+dependency leaf: its single `FS() fs.FS` API returns the read-only embedded
+filesystem, and the package contains no business logic or internal or PromptKit
+dependencies. The accepted import path is
+`gitea.maximumdirect.net/eric/notarius/assets`; it makes repository-owned
+content available to its consumers, not a public extension contract.
+
+Consumers scope that filesystem to the subtree they own before reading or
+registering content. Modules continue to own their manifests, prompt ordering,
+private response-schema identity, and registration. Centralizing physical files
+does not centralize domain semantics or transfer those responsibilities to the
+root package.
+
+The root package contains prompt content, private LLM response schemas, generic
+LLM schemas, shared fragments, and fallback profiles. Durable artifact schemas
+and non-LLM domain data remain with their current owners. A module fingerprint
+is derived from its manifest-selected module and shared files, rather than from
+an entire asset tree. The relocation is accepted to cause a one-time checkpoint
+invalidation.
+
+This decision supersedes only the physical asset-co-location portion of
+ADR-0004's decision that places domain-specific prompt fragments and schemas
+within the domain tree. ADR-0004's domain-first packaging and registrar
+ownership decisions remain accepted.
+
+## Alternatives Considered
+
+- Keep package-local assets. This preserves physical co-location with code but
+  makes prompt-author discovery and cross-family review unnecessarily costly.
+- Use `internal/llmassets`. This would hide content from legitimate owners
+  outside the `internal` subtree and would make the root asset boundary depend
+  on implementation-layer placement.
+- Build a behavioral central registry. This would mix content discovery with
+  prompt selection and registration behavior, moving module semantics into a
+  shared registry.
+- Use runtime filesystem overlays. This would add runtime configuration and
+  failure modes where compile-time embedded content is sufficient.
+
+## Consequences
+
+Prompt authors can find in-scope LLM content in one top-level tree while module
+packages continue to define its meaning and registration. Consumers have an
+explicit, narrow dependency on only the content they need. The root package is
+intentionally importable but must remain a stable, content-only leaf rather
+than becoming a general extension API.
+
+The initial relocation invalidates existing checkpoints once. Later checkpoint
+identity changes remain limited to the manifest-selected prompt and shared
+content, so unrelated files do not trigger recomputation.

docs/adr/0012-resolve-opaque-entity-identifiers-deterministically.md

@@ -0,0 +1,64 @@
+# ADR-0012: Resolve opaque entity identifiers deterministically
+
+**Status:** Accepted
+**Date:** 2026-08-08
+
+## Context
+
+Entity IDs in durable Notarius artifacts are application-owned, deterministic
+identifiers. They are useful to artifact consumers, but their hash-based form
+does not help a model distinguish entities and would make the model reproduce
+an opaque implementation detail. A plain name is likewise insufficient where
+multiple supplied records share that name.
+
+The LLM boundary must preserve the typed artifact and durable-schema ownership
+of [ADR-0003](0003-typed-interfaces-with-two-zone-data-model.md) and the distinction
+between disambiguating references and source evidence in
+[ADR-0009](0009-minimal-evidence-grounded-extraction-artifacts.md).
+
+## Decision
+
+Callers present a model with semantic selections: a canonical name when it is
+unique in the request, or a contextual descriptor containing the name and
+source coordinates when that context is needed to distinguish supplied
+records. The model returns only those supplied selections. The caller resolves
+each accepted selection against the request-local supplied records and attaches
+the opaque application ID deterministically.
+
+Source coordinates are permitted in a selection solely as identity context.
+They neither establish an occurrence fact nor replace that occurrence's
+current-transcript evidence. A selector must resolve exactly; unknown,
+ambiguous, partial, reordered, or otherwise unsafe selections are not mapped.
+Where an operation requires a complete grounded artifact, that failure rejects
+the complete artifact rather than accepting a partially mapped result.
+
+An explicitly scoped request-local short label is permitted only when a
+contextual descriptor would be impractical and the caller can deterministically
+map the label within that one request. Such a label is not a durable ID, must
+not escape the request boundary, and requires a concrete justification in its
+own module contract.
+
+## Alternatives considered
+
+- Ask the model to return durable IDs. This exposes opaque implementation
+  state, does not improve semantic disambiguation, and makes model output
+  depend on hash formatting.
+- Select by name alone. This cannot safely distinguish same-name records.
+- Make request-local labels durable identifiers. This would turn prompt
+  presentation into a public identity contract and create avoidable migration
+  pressure.
+- Let the model invent identifiers or resolve ambiguity. This makes identity
+  assignment non-deterministic and weakens validation.
+
+## Consequences
+
+Durable integration contracts retain their exact ID/name pairs while models
+operate on readable contextual selections. Calling modules must own selector
+construction, exact resolution, ambiguity handling, and conversion into their
+durable artifact type; PromptKit and its adapter remain transport-only.
+
+Some ambiguous or invalid proposals are deliberately omitted, retried, or
+rejected according to the caller's existing failure policy. Internal candidate
+keys may support deterministic request-local mapping, but they are not
+model-visible selectors or durable data. This adds local validation work while
+keeping identity assignment auditable and stable.

docs/adr/0013-use-request-local-candidate-handles-for-semantic-reconciliation.md

@@ -0,0 +1,89 @@
+# ADR-0013: Use request-local candidate handles for semantic reconciliation
+
+**Status:** Accepted
+**Date:** 2026-08-09
+
+## Context
+
+Several typed normalize stage modules need semantic reconciliation after
+deterministic preprocessing: a model can judge whether source-backed candidates
+refer to the same underlying entity, while application code remains responsible
+for constructing the normalized artifact. Requiring the model to reproduce a
+candidate's full contextual selector makes the response larger and introduces
+avoidable formatting, ordering, and transcription failure modes.
+
+Reconciliation must preserve the exact typed artifact boundary established by
+[ADR-0003](0003-typed-interfaces-with-two-zone-data-model.md), the domain-neutral
+framework and concrete-domain dependency direction established by
+[ADR-0004](0004-package-modules-by-domain.md), and the distinction in
+[ADR-0009](0009-minimal-evidence-grounded-extraction-artifacts.md) between source
+evidence and auxiliary identity context. It also needs a concrete, narrowly
+scoped application of the request-local-label exception allowed by
+[ADR-0012](0012-resolve-opaque-entity-identifiers-deterministically.md).
+
+## Decision
+
+Semantic reconciliation will be a domain-neutral framework mechanism used by
+typed normalize stage modules. A consuming artifact family will retain
+ownership of its typed records, identity rules, consolidation policy, durable
+IDs, and domain warnings; the framework mechanism will not infer those rules
+from arbitrary data.
+
+For each reconciliation request, deterministic code will assign every eligible
+model-visible candidate a contiguous, one-based integer handle. The model may
+receive the candidate's contextual label, source references, and bounded source
+context needed to judge identity, but its structured response will identify
+candidates only by those supplied handles. A handle is local to one request,
+does not represent entity identity, and must never enter a durable artifact or
+be used to derive a durable ID.
+
+The model will propose duplicate groups and select one supplied member of each
+group as canonical. Deterministic code will resolve the handles through the
+retained request mapping, validate the complete proposal, discard unsafe
+groups, and apply only validated groups through typed domain-owned policy. The
+model will not synthesize replacement records or directly mutate an artifact.
+
+Every reconciliation prompt will combine a mandatory framework-owned protocol
+and safety policy with an explicitly selected semantic policy. The semantic
+policy may be the conservative generic policy or a domain-owned policy, but it
+cannot replace the shared response protocol or deterministic safety boundary.
+
+## Alternatives considered
+
+- Return durable application IDs. Opaque IDs do not help semantic judgment,
+  expose application identity mechanics, and make model output reproduce data
+  that deterministic code already owns.
+- Return names alone or copied contextual selectors. Names can be ambiguous,
+  while reproducing labels and source ranges adds response complexity and
+  creates mismatches without adding semantic information. Request-local
+  handles preserve exact selection without either failure mode.
+- Ask the model to return synthesized canonical replacement records. This
+  would transfer typed artifact construction, provenance consolidation, and
+  durable identity policy to a probabilistic boundary.
+- Reconcile reflection-discovered fields or arbitrary JSON. This would weaken
+  the typed artifact contract and move domain semantics into generic code.
+- Hide reconciliation inside extraction or another stage. This would obscure
+  stage ownership and create cross-stage behavior outside the fixed pipeline;
+  reconciliation remains explicit normalize-stage behavior.
+- Let each domain replace the complete prompt protocol. This would duplicate
+  safety mechanics and allow domain policy to bypass the common response and
+  validation contract.
+
+## Consequences
+
+Model responses become smaller and easier to validate, while deterministic
+application code retains authority over identity, provenance, ordering, and
+typed artifact construction. The framework requires a request-local mapping,
+bounded context preparation, a private integer response contract, proposal
+assessment, and shared prompt assets. Each consuming artifact family still
+requires a typed adapter for its irreducibly domain-specific rules.
+
+Request-local handles are deliberately unsuitable for persistence, logging as
+entity identity, checkpoint contracts, or cross-request correlation. Changes
+to shared protocol and policy assets must participate in the normal prompt,
+schema, and checkpoint fingerprint mechanisms.
+
+The shared mechanism and its initial D&D registry consumers are now
+implemented. Current behavior is documented in
+[Module Internals](../internal/modules.md#semantic-reconciliation) and
+[D&D Module Internals](../internal/dnd.md#semantic-registry-reconciliation).

docs/adr/0014-feedback-aware-validation-retries.md

@@ -0,0 +1,59 @@
+# ADR-0014: Use feedback-aware validation retries
+
+**Status:** Accepted
+**Date:** 2026-08-26
+
+## Context
+
+Validation can identify a candidate defect after a producer has returned an
+otherwise well-formed result. Retrying without the validator's deterministic,
+bounded feedback wastes the useful diagnosis, while treating validator
+execution failures as defects would ask a producer to repair conditions it
+cannot control. The mechanism must preserve typed producer ownership,
+checkpoint safety, and the repository's sensitive-data boundaries.
+
+## Decision
+
+The implementation will keep three independent budgets: the producer binding's
+outer `retries` budget, PromptKit's structured-output repair budget, and each
+validator's execution-retry budget. Validators will run sequentially in their
+configured order and aggregate both rejections and execution failures before a
+candidate disposition is selected.
+
+A correction-capable producer will provide the exact single LLM response that
+controlled its candidate using the `single_response_v1` protocol. A correction
+attempt will reconstruct the ordinary request and append exactly two fresh
+messages: that latest response as `assistant`, followed by one deterministic
+aggregate correction request as `user`. Earlier turns will not accumulate.
+
+Validator failures will not recurse into correction. Pipeline policy owns
+terminal disposition, with field-by-field producer overrides over pipeline
+defaults: structural failure and semantic rejection default to `fail_run`, and
+validator execution failure defaults to `warn_continue`. Validators can report
+facts and bounded corrective guidance, but never decide disposition.
+
+Rejected and structurally invalid candidates will not advance. A candidate
+allowed through after a validator execution failure will retain explicit
+incomplete-validation provenance and will not be checkpointed. Exact response
+and correction text remain attempt-local: they are excluded from ordinary
+errors, warnings, manifests, receipts, caches, checkpoints, and default debug
+summaries.
+
+## Alternatives considered
+
+- Retry every producer after any validation outcome. This conflates producer
+  defects with validator operational failures and wastes retry budget.
+- Let validators decide whether to continue. This would distribute pipeline
+  disposition policy across validators and undermine consistent defaults.
+- Reuse the full prior conversation. Accumulated turns introduce unbounded
+  prompt growth and make correction behavior depend on incidental history.
+- Persist raw responses to simplify diagnosis. Raw model output and correction
+  guidance may be sensitive and do not belong in durable pipeline records.
+
+## Consequences
+
+The framework gains transport-neutral correction and candidate contracts,
+producer capability checks, policy resolution, aggregated validation outcomes,
+and conservative checkpoint handling. Prompt construction remains inside the
+LLM adapter, while modules remain responsible for accurately exposing the
+single response that directly controlled a candidate.

docs/cli.md

@@ -1,278 +1,187 @@
 # CLI Reference
 
 This is the canonical reference for the implemented Notarius command-line
-interface.
+interface. For the shortest successful run, see the [README](../README.md).
+Configuration fields, discovery rules, and selectable module keys are defined
+in [Configuration](config.md); runtime state and recovery procedures are
+defined in [Operations](operations.md).
 
-For the minimal end-to-end invocation, see the [README](../README.md).
+## Command Summary
 
-## Commands
-
-```text
+~~~
 notarius help
-notarius run <pipeline-id> --input path/to/source.json [--config path/to/config.yml] [--only lane-a,lane-b] [--chunk_cache auto|bypass|refresh] [--output-dir path] [--resume] [--recompute-step step-id] [--debug [--debug-dir path]] [--llm-profile id] [--session-id id] [--reference selector=path] [--without-reference selector]
+notarius --version
+notarius run <pipeline-id> --input path/to/source.json [--json] [flags]
 notarius config validate [--config path/to/config.yml] [--pipeline pipeline-id] [--only lane-a,lane-b]
 notarius pipelines list [--config path/to/config.yml] [--json]
-```
+~~~
 
-Running `notarius` with no arguments, `notarius help`, `notarius --help`, or
-`notarius -h` prints usage and exits successfully.
+Running Notarius without arguments, or with **help**, **--help**, or **-h**,
+writes the command summary to standard output and exits with status 0.
 
-## `run`
+`notarius --version` is valid only as the sole root argument. It writes exactly
+`notarius <version>` followed by a newline to standard output and exits with
+status 0. A tagged `go install` build can report its main-module stable tag,
+and controlled builds can inject a stable tag at link time through
+`gitea.maximumdirect.net/eric/notarius/internal/buildinfo.Override`; an ordinary
+unversioned checkout reports `development`. Invalid injected version content is
+a runtime error with exit status 1, while extra `--version` arguments are a
+syntax error with exit status 2. This diagnostic does not replace the
+[run-result](integrations/run-result.md) or artifact contracts for downstream
+compatibility decisions.
 
-`notarius run <pipeline-id>` executes a configured pipeline against one input
-file.
+## run
 
-Flags:
+~~~
+notarius run <pipeline-id> --input path/to/source.json [--json] [flags]
+~~~
 
-- `--input path`: required source input file.
-- `--config path`: config file path. If omitted, Notarius uses the discovery
-  rules in [Configuration](config.md#discovery).
-- `--only lane-a,lane-b`: run only the named artifact lanes. Values are
-  comma-separated and must be non-empty. This retains its existing behavior for
-  implicit single-step pipelines; explicit multi-step pipelines reject it
-  rather than inferring dependency closure.
-- `--resume`: request checkpoint reuse for this invocation. Checkpoint recording
-  must be enabled in configuration. See
-  [Operations](operations.md#checkpoint-cache) for prerequisites and reuse
-  behavior.
-- `--recompute-step step-id`: with `--resume` and checkpoint recording enabled,
-  force the named ordered step and every transitive dependent lane to execute.
-  Compatible required predecessors and unrelated lanes remain reusable. The
-  value may identify an explicit step or the implicit single-step ID `default`;
-  it cannot be combined with `--only`.
-- `--chunk_cache auto|bypass|refresh`: select chunk-plan reuse for this
-  invocation. `auto` reuses a valid plan by canonical source digest, `bypass`
-  performs no plan-cache I/O, and `refresh` regenerates and replaces a valid
-  plan only after chunk validation succeeds. See
-  [Configuration](config.md#state-surfaces) for the persistent setting, precedence,
-  and cache-root selection.
-- `--output-dir path`: output root. Defaults to `./notarius-output`.
-- `--debug`: allocate and retain one debug bundle for this invocation.
-- `--debug-dir path`: debug-bundle root override. This flag requires `--debug`.
-- `--llm-profile id`: override every effective LLM-capable pipeline module
-  binding with one Scriptorium profile ID. Validator-specific profiles are not
-  overridden.
-- `--session-id id`: pass a stable prompt session identifier through LLM-backed
-  module calls.
-- `--reference selector=path`: bind a reference path to a chunk, extractor,
-  merger, or normalizer reference slot. Repeatable.
-- `--without-reference selector`: remove a configured optional reference binding.
-  Repeatable. It accepts the same selector forms as `--reference`, without
-  `=path`.
+The **run** command executes the named pipeline for one input file. The
+pipeline ID and **--input** are required.
 
-On success, the command prints the completed pipeline ID, normalized output and
-rejected output counts, and the output directory. A debug-enabled run also
-prints `debug=<bundle-path>`. If the run completes with warnings, the warning
-count is printed to stderr.
+| Flag | Meaning |
+| --- | --- |
+| **--config path** | Use this configuration file. When omitted, configuration discovery applies; see [Configuration](config.md). |
+| **--input path** | Source input file to process. Required. |
+| **--output-dir path** | Override the configured output root for this run. |
+| **--json** | Write the successful run-result receipt as JSON to standard output. |
+| **--chunk_cache auto\|bypass\|refresh** | Override chunk-plan cache handling for this run. |
+| **--resume** | Reuse compatible recorded checkpoints when checkpoint recording is enabled. |
+| **--recompute-step step-id** | With **--resume**, recompute the selected ordered step and its dependent lanes. It cannot be combined with **--only**. |
+| **--debug** | Retain a debug bundle for this run. |
+| **--debug-dir path** | Override the debug-bundle root. Requires **--debug**. |
+| **--only lane-a,lane-b** | Run only the selected comma-separated artifact lanes when that selection is valid for the configured pipeline. |
+| **--llm-profile id** | Highest-precedence configured profile for selected LLM-backed bindings and validators; it replaces binding and [pipeline](config.md#pipelines) defaults. |
+| **--session-id id** | Override the generated prompt session identifier with a non-empty value for LLM-backed module calls. |
+| **--reasoning-effort value** | Replace the selected PromptKit profile's reasoning effort for every LLM-backed call in this run. The value must be non-empty and the flag may be specified only once. |
+| **--clear-reasoning-effort** | Clear reasoning effort inherited from the selected PromptKit profile for every LLM-backed call in this run. |
+| **--reference selector=path** | Add or replace a file reference binding. Repeatable. |
+| **--without-reference selector** | Remove a configured optional reference binding. Repeatable. |
 
-Reference flags are external file bindings resolved against selected chunk,
-extractor, merger, and normalizer targets before the run starts. Generated
-artifact bindings are configured in ordered steps and cannot be introduced by a
-CLI path flag. Flat slot names are accepted only
-when exactly one selected target declares that slot. For configured reference
-bindings, precedence, path resolution, and validation, see
-[Configuration](config.md#pipelines).
+**--chunk_cache** accepts only **auto**, **bypass**, or **refresh**.
+**--debug-dir**, **--output-dir**, **--session-id**, and
+**--reasoning-effort**, and **--recompute-step** reject explicit empty values.
+**--reasoning-effort** and **--clear-reasoning-effort** are mutually exclusive.
+When neither is present, reasoning effort comes from the selected PromptKit
+profile. These controls apply to the shared run client, including retries and
+LLM-backed validators, and do not modify configuration or profile files.
+Persistent reasoning settings remain a PromptKit profile concern.
+**--recompute-step** requires **--resume**; checkpoint requirements and reuse
+behavior are documented in [Operations](operations.md).
 
-`--reference` binds or replaces one slot for one selected target. Selectors are:
+Every run uses one effective prompt session. Without **--session-id**, Notarius
+generates a stable `notarius:v1:` identifier from the trimmed resolved input
+module key and the input file's exact raw bytes. The same module and bytes
+therefore produce the same identifier, regardless of pipeline, references,
+profile, retries, or run settings. An explicit non-empty value replaces that
+default. Session identifiers are visible to providers; they are non-secret
+correlation identifiers, not credential storage. See
+[Operations](operations.md#operational-limits) for privacy and workflow
+guidance.
 
-- `slot=path`: valid when exactly one selected target declares `slot`;
-- `chunk.slot=path`: target the chunker;
-- `merge.slot=path`: valid when exactly one selected merger declares `slot`;
-- `lane.slot=path`: valid when exactly one selected extractor, merger, or
-  normalizer in that lane declares `slot`;
-- `lane.extract.slot=path`: target a lane extractor;
-- `lane.merge.slot=path`: target a lane merger;
-- `lane.normalize.slot=path`: target a lane normalizer.
+### Reference selectors
 
-Use `slot=path` when the selected targets declare the slot unambiguously:
+Use **--reference** only for a reference slot declared by the selected
+configured target. The accepted selector forms are:
 
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --reference roster=./campaign-roster.txt
-```
+| Form | Target |
+| --- | --- |
+| slot=path | The unique selected target that declares slot. |
+| chunk.slot=path | The chunker. |
+| merge.slot=path | The unique selected merger that declares slot. |
+| lane.slot=path | The unique extractor, merger, or normalizer in lane that declares slot. |
+| lane.extract.slot=path | The extractor in lane. |
+| lane.merge.slot=path | The merger in lane. |
+| lane.normalize.slot=path | The normalizer in lane. |
 
-Use an explicit selector when multiple selected targets declare the same slot or
-when you want to target a specific target:
+**--without-reference** uses the same selector forms without =path. Slot
+names, requiredness, and configured bindings are part of the
+[configuration contract](config.md).
 
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --reference spells.extract.glossary=./campaign-glossary.txt
-```
+### Run output
 
-For the maintained ordered D&D workflow, use the explicit pipeline. The first
-step produces normalized NPC and scene-description artifacts; the second step
-receives the NPC artifact in memory for spell extraction, combat extraction, and
-combat normalization, and receives the required scene-description artifact for
-combat eligibility:
+Without **--json**, standard output contains the completed pipeline ID, counts
+of normalized and rejected outputs, and the output directory. A debug-enabled
+run also prints its debug-bundle path to standard output. A successful run with
+warnings reports the warning count to standard error. The published JSON bundle
+is defined by the [JSON output contract](integrations/json-output.md).
 
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-complete.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --output-dir ./npc-grounded-output
-```
+With **--json**, successful standard output is exactly one
+`notarius.run-result.v1` JSON document followed by a newline, with no
+human-oriented status or debug-path line. Its fields and compatibility policy
+are defined by the [run-result contract](integrations/run-result.md). A caller
+must check for exit status 0 before decoding this output; a failed write can
+leave incomplete standard-output bytes that are not a result document.
 
-The generated NPC content remains contextual grounding, not spell or combat
-evidence. It is represented in manifests and debug summaries by bounded
-identity and producer provenance, not by payload content or a filesystem path.
-The scene-description artifact is control context: combat extraction calls its
-LLM only for an exact `combat` scene match. See the
-[D&D combat-turn artifact contract](integrations/dnd-combat-turn-artifacts.md)
-for the resulting empty-output and warning behavior.
+Example:
 
-The same grammar can target chunk, merge, and normalize slots when the configured
-modules declare them:
+~~~
+OPENROUTER_API_KEY=your-api-key \
+  go run ./cmd/notarius run dnd-session \
+    --config examples/dnd-minimal.config.yml \
+    --input examples/seriatim-minimal-transcript.json
+~~~
 
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config path/to/config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --reference chunk.scene_guide=./campaign-scenes.txt \
-  --reference spells.merge.merge_notes=./merge-notes.txt \
-  --reference spells.normalize.normalization_notes=./normalization-notes.txt
-```
+## config validate
 
-Use `--without-reference` to remove a configured optional binding for a run:
+~~~
+notarius config validate [--config path/to/config.yml] [--pipeline pipeline-id] [--only lane-a,lane-b]
+~~~
 
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --without-reference glossary
-```
+This command loads and validates a configuration. With **--pipeline**, it also
+resolves that pipeline against the production module catalog. **--only** selects
+lanes during that resolution and requires **--pipeline**.
 
-Use `--session-id` when an external orchestrator needs all prompt calls from one
-run to share an identifier:
-
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --session-id campaign-17-session-04
-```
-
-When `cache.checkpoints.enabled` is `true`, runs record checkpoints whether or
-not `--resume` is present. Add the resume flag to load and reuse compatible
-recorded work; using it while checkpoint recording is disabled is an error:
-
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --resume
-```
-
-To selectively rerun one ordered step and its dependent lanes, use the step ID
-from the configuration. The selected step and dependents are reported as
-`forced_recompute`; reusable predecessors are reported as `reused`:
-
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-complete.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --resume --recompute-step extract-events
-```
-
-Checkpoint decisions use these categories: `reused`, `executed`,
-`forced_recompute`, and `dependency_invalidated`. The reason code and bounded
-detail identify the decision without exposing reference content, local paths,
-or secrets. `--recompute-step` requires checkpoint recording and `--resume`;
-unknown step IDs, empty values, and combinations with `--only` are rejected.
-The operator meanings of checkpoint reason codes are maintained in
-[Operations](operations.md#resume-and-selective-recompute).
-
-Use `--debug` to retain the redacted summary and trace bundle for one run. The
-bundle is allocated before pipeline resolution; once allocated, its path is
-also printed to stderr if the command fails. Debug-write failures cause exit
-code `1`.
-
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --debug --debug-dir ./notarius-debug
-```
-
-Use `refresh` when intentionally replacing the cached plan for the same source:
-
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --chunk_cache refresh
-```
-
-Use `bypass` for a one-off run that must not inspect or create plan-cache state:
-
-```sh
-go run ./cmd/notarius run dnd-session \
-  --config examples/dnd-minimal.config.yml \
-  --input examples/seriatim-minimal-transcript.json \
-  --chunk_cache bypass
-```
-
-`--diagnostics-dir` has been removed. For checkpoint behavior, durable output,
-debug-bundle lifecycle, and failure inspection, see [Operations](operations.md).
-
-## `config validate`
-
-`notarius config validate` loads and validates configuration.
-
-Flags:
-
-- `--config path`: config file path. If omitted, Notarius uses the discovery
-  rules in [Configuration](config.md#discovery).
-- `--pipeline pipeline-id`: additionally resolve one configured pipeline against
-  the production module catalog.
-- `--only lane-a,lane-b`: validate resolution for selected artifact lanes. This
-  flag requires `--pipeline`.
+Success is written to standard output as either config "<path>" is valid or
+config "<path>" is valid for pipeline "<pipeline-id>".
 
 Examples:
 
-```sh
-go run ./cmd/notarius config validate \
-  --config examples/dnd-minimal.config.yml
-
+~~~
 go run ./cmd/notarius config validate \
   --config examples/dnd-minimal.config.yml \
-  --pipeline dnd-session \
-  --only spells
-```
+  --pipeline dnd-session
 
-## `pipelines list`
+OPENROUTER_API_KEY=validation-placeholder \
+  go run ./cmd/notarius config validate \
+    --config examples/dnd-complete.config.yml \
+    --pipeline dnd-session
+~~~
 
-`notarius pipelines list` prints configured pipeline IDs in sorted order.
+The placeholder in the second command is sufficient only for offline
+validation; it cannot run a provider-backed pipeline.
 
-Flags:
+## pipelines list
 
-- `--config path`: config file path. If omitted, Notarius uses the discovery
-  rules in [Configuration](config.md#discovery).
-- `--json`: print `{"pipelines":[...]}` instead of one ID per line.
+~~~
+notarius pipelines list [--config path/to/config.yml] [--json]
+~~~
 
-Examples:
+This command lists configured pipeline IDs in sorted order. By default, it
+writes one ID per line to standard output. **--json** writes an object shaped as
+{"pipelines":[...]} instead.
 
-```sh
+~~~
 go run ./cmd/notarius pipelines list \
   --config examples/dnd-minimal.config.yml
+~~~
 
-go run ./cmd/notarius pipelines list \
-  --config examples/dnd-minimal.config.yml \
-  --json
-```
+## Output Streams And Exit Statuses
 
-## Exit Codes
+Successful commands write their primary result to standard output. Warnings and
+errors are written to standard error.
 
-- `0`: command succeeded.
-- `1`: command syntax was valid, but loading config, resolving modules, running
-  the pipeline, calling the provider, writing output, or writing a requested
-  debug bundle failed.
-- `2`: command syntax was invalid, a command was unknown, a required argument
-  was missing, or a flag value was malformed.
+For **run --json**, warnings remain on standard error and standard output is a
+machine-readable success result only. Syntax and runtime diagnostics remain on
+standard error. Parse the result only after the process exits with status 0.
 
-For YAML structure, defaults, Scriptorium profile sources, environment
-overrides, and selectable module and validator keys, see
-[Configuration](config.md).
+| Status | Meaning |
+| --- | --- |
+| 0 | The command completed successfully, including root help. |
+| 1 | Command syntax was valid but configuration loading or validation, pipeline resolution or execution, provider use, output, or requested debug handling failed. |
+| 2 | The command or flag syntax was invalid, including unknown commands, missing required arguments, invalid flag values, or invalid flag combinations. |
+
+The root help spellings are the supported help path. Invoking **--help** on
+**run**, **config validate**, or **pipelines list** is handled by the flag
+parser as a usage error: it writes an error to standard error and exits with
+status 2.

docs/consumers/dnd-pipeline.md

@@ -0,0 +1,208 @@
+# Consuming The Complete D&D Pipeline
+
+Use this workflow when an orchestrator runs the maintained complete D&D
+pipeline and consumes its structured JSON artifacts. The generic
+[subprocess consumer guide](subprocess.md) owns process-level responsibilities;
+this guide connects that workflow to the complete D&D configuration, its
+Seriatim input, and its artifact inventory.
+
+The [CLI reference](../cli.md), [configuration reference](../config.md),
+[run-result receipt](../integrations/run-result.md), and
+[published JSON output contract](../integrations/json-output.md) remain the
+canonical definitions of those public interfaces.
+
+## Prepare And Validate The Deployment
+
+Start from the maintained
+[complete D&D configuration](../../examples/dnd-complete.config.yml). It uses
+the `dnd-session` pipeline and demonstrates every implemented D&D lane, ordered
+artifact handoffs, campaign references, chunk-map publication, and evidence
+context.
+
+A deployment must provide its own PromptKit profile and campaign reference
+files. Use absolute paths for service and subprocess deployments. In
+particular, observe these different resolution rules:
+
+- reference paths in YAML are resolved relative to the Notarius configuration
+  file; and
+- `promptkit.profile_file` is resolved relative to the Notarius process working
+  directory.
+
+Do not copy the repository example's relative profile path into a deployment
+without also controlling that working directory. The complete path and profile
+rules are defined in [Configuration](../config.md).
+
+Preflight the deployed configuration before processing sessions and whenever
+it changes:
+
+```sh
+notarius config validate \
+  --config /absolute/path/to/notarius.yml \
+  --pipeline dnd-session
+```
+
+Provide credentials through the environment or the documented configuration
+mechanism. Do not put credentials in command arguments, generated
+configuration, or logs.
+
+## Supply The Transcript
+
+The complete pipeline consumes a Seriatim JSON document. The
+[Seriatim input contract](../integrations/seriatim.md) defines its required
+metadata, segments, and validation rules. Preserve segment IDs: D&D artifact
+citations use those segment IDs as source-unit ranges.
+
+When the caller maintains several transcript tiers, use the final trimmed JSON
+transcript so extraction operates on the same session content presented to
+later consumers. For example, Narratio identifies this implemented artifact as
+`narratio.transcript.final_trimmed` and normally stores it at
+`transcripts/final.trimmed.json`.
+
+Notarius generates a stable prompt session from the resolved input module and
+the exact input bytes. An ordinary orchestrator should not pass `--session-id`.
+Use that override only when intentionally changing the routing relationship
+between invocations; it is not a credential or output identity.
+
+## Run Notarius
+
+Invoke the pipeline with explicit absolute paths and request its
+machine-readable receipt:
+
+```sh
+notarius run dnd-session \
+  --config /absolute/path/to/notarius.yml \
+  --input /absolute/path/to/transcripts/final.trimmed.json \
+  --output-dir /absolute/path/to/notarius-output \
+  --json
+```
+
+The caller should:
+
+- capture stdout and stderr separately;
+- propagate cancellation and impose an operator-appropriate timeout;
+- wait for process completion before interpreting stdout; and
+- retain stderr for diagnosis without copying secrets or transcript content
+  into other logs.
+
+Only exit status 0 permits decoding stdout as a receipt. Ignore stdout after a
+nonzero exit because a failed receipt write can leave partial bytes. The
+[CLI reference](../cli.md#output-streams-and-exit-statuses) defines the complete
+stream and exit-status contract.
+
+## Discover The Published Bundle
+
+Decode the successful stdout document as a supported run-result schema. For
+the current contract, `schema_version` is `notarius.run-result.v1`. Tolerate
+unknown fields allowed by that version, but reject an unsupported schema
+version.
+
+Use the receipt's absolute `output_directory` as the exact run-specific bundle
+root. Do not scan the output root for its newest directory, guess a run ID, or
+construct a bundle path. Resolve `index_file` beneath `output_directory` and
+reject an absolute logical path or any result that escapes the bundle root.
+
+The complete configuration uses the application validation defaults. A caller
+that requires fully validated D&D artifacts must also require receipt
+`validation_status: approved`; a successful `incomplete` result reflects the
+configured validator-failure continuation policy and carries its bounded
+validator provenance in `validation_summaries`.
+
+Read `index.json` and locate each requested lane in `output_files` by its exact
+`lane_id`. Do not guess a lane filename. Before decoding a payload:
+
+1. resolve its descriptor's relative `file` beneath the bundle root with the
+   same confinement check;
+2. verify the descriptor's media type and schema identity against the linked
+   artifact contract; and
+3. decode the payload according to that contract.
+
+The [published JSON output contract](../integrations/json-output.md) defines
+the index and bundle layout. Treat all paths obtained from a decoded external
+document as untrusted until confined to their documented root.
+
+## Complete Artifact Inventory
+
+When every configured lane is accepted, the complete example publishes these
+lane artifacts:
+
+| Lane ID | Purpose | Canonical contract |
+| --- | --- | --- |
+| `item-registry` | Canonical registry of encountered items and currency. | [Item registry](../integrations/dnd-item-registry-artifacts.md) |
+| `npc-registry` | Canonical registry of named NPCs. | [NPC registry](../integrations/dnd-npc-registry-artifacts.md) |
+| `location-registry` | Canonical registry of named locations. | [Location registry](../integrations/dnd-location-registry-artifacts.md) |
+| `scene-descriptions` | Classification, title, and summary for each scene. | [Scene descriptions](../integrations/dnd-scene-description-artifacts.md) |
+| `item-occurrences` | Source-grounded item discovery, acquisition, use, transfer, and loss events. | [Item occurrences](../integrations/dnd-item-occurrence-artifacts.md) |
+| `spells` | Source-grounded spell casts and casters. | [Spell casts](../integrations/dnd-spell-artifacts.md) |
+| `combat-turns` | Source-grounded combat turn participation. | [Combat turns](../integrations/dnd-combat-turn-artifacts.md) |
+| `npc-occurrences` | Source-grounded NPC interaction occurrences. | [NPC occurrences](../integrations/dnd-npc-occurrence-artifacts.md) |
+| `location-occurrences` | Source-grounded location occurrences. | [Location occurrences](../integrations/dnd-location-occurrence-artifacts.md) |
+| `enemy-events` | Source-grounded enemy combat events. | [Enemy events](../integrations/dnd-enemy-event-artifacts.md) |
+
+The JSON encoder always publishes these bundle-management files:
+
+| File | Purpose |
+| --- | --- |
+| `index.json` | Discovery document for lane and pipeline-wide artifacts. |
+| `manifest.json` | Run provenance and result summaries. |
+| `rejected.json` | Rejected pipeline outputs. |
+| `warnings.json` | Accepted-output and run warnings. |
+
+The complete configuration also requests two pipeline-wide artifacts:
+
+- [`chunk-map.json`](../integrations/chunk-map.md), the accepted chunk plan and
+  chunk metadata; and
+- [`evidence-context.json`](../integrations/evidence-context.md), a reading
+  excerpt containing the union of selected cited source units and the
+  configured surrounding window.
+
+Discover both from their top-level `index.json` descriptors rather than
+treating them as lanes. Evidence context is convenient reading material, not
+authoritative provenance; citations in the normalized lane payloads remain the
+evidence contract.
+
+Every optional or lane file is published only when its corresponding artifact
+is available. A successful process does not guarantee that all configured
+lanes were accepted.
+
+## Decide What Counts As Consumer Success
+
+Exit status 0 means Notarius completed the pipeline and published its result
+bundle. The receipt or bundle may still report warnings, rejected outputs, or
+missing lane descriptors. A downstream consumer must define its own required
+artifact set explicitly.
+
+A caller that claims to consume the complete D&D workflow should normally
+require all ten lane IDs in the table and verify each descriptor's expected
+contract. If any required lane is missing, rejected, or incompatible, fail the
+caller's extraction step while retaining the Notarius bundle for diagnosis. A
+consumer that needs only a subset may define and document a narrower policy.
+
+Keep the successful receipt with the complete published bundle. Retain
+`manifest.json`, `rejected.json`, `warnings.json`, and captured process logs as
+required by the caller's provenance, diagnosis, and retention policies. Avoid
+selectively copying payload files without also preserving enough index and
+manifest information to identify their originating run and contracts.
+
+The transcript, lane artifacts, evidence context, manifest, debug data, and
+logs can all contain private campaign information. Apply the same access,
+publication, and retention controls used for the source transcript.
+
+## Consumer Checklist
+
+- Validate the deployed Notarius configuration and `dnd-session` pipeline.
+- Pass the final trimmed Seriatim JSON transcript with stable segment IDs.
+- Use absolute configuration, input, output-root, profile, and reference paths
+  in service deployments.
+- Capture stdout and stderr separately and enforce cancellation and timeout.
+- Parse stdout only after exit status 0.
+- Accept only supported receipt, index, and artifact schema versions while
+  tolerating permitted unknown fields.
+- Use the receipt's `output_directory`; never guess the run directory.
+- Confine `index_file` and every descriptor path to the published bundle root.
+- Discover lanes by `lane_id` and verify descriptor compatibility before
+  decoding payloads.
+- Enforce an explicit required-lane policy and inspect rejections and warnings.
+- Preserve the receipt and sufficient bundle provenance for every retained
+  artifact.
+- Protect all transcript-derived files and diagnostic streams as sensitive
+  campaign data.

docs/consumers/subprocess.md

@@ -0,0 +1,88 @@
+# Using Notarius As A Subprocess
+
+Use this workflow when an orchestrator runs Notarius and consumes its published
+artifacts. The [CLI reference](../cli.md) owns invocation syntax and exit
+statuses, while the [run-result receipt](../integrations/run-result.md) and
+[Published JSON Output contract](../integrations/json-output.md) own the
+durable result formats.
+
+For the maintained complete D&D workflow, including its transcript input,
+configured lane inventory, and downstream acceptance checklist, see
+[Consuming The Complete D&D Pipeline](dnd-pipeline.md).
+
+## Run And Check The Process
+
+Optionally preflight a selected configuration and pipeline before work starts:
+
+```sh
+notarius config validate --config /path/to/notarius.yml --pipeline pipeline-id
+```
+
+Invoke the run with explicit paths and machine-readable output. Capture
+standard output and standard error separately; do not combine them before
+processing the result.
+
+```sh
+notarius run pipeline-id \
+  --config /path/to/notarius.yml \
+  --input /path/to/source.json \
+  --output-dir /path/to/output-root \
+  --json
+```
+
+Use absolute paths for supplied input, configuration, output-root, and
+reference files. Notarius generates a stable prompt session for the resolved
+input module and exact input bytes. Pass **--session-id** only when intentionally
+grouping different invocations under a different session. Supply credentials
+through Notarius's documented configuration and environment mechanisms, never
+as command-line arguments or generated secret-bearing configuration. In
+particular, a session identifier is provider-visible and is not a credential
+mechanism.
+
+Wait for the process before interpreting standard output. Only an exit status
+of 0 permits decoding the receipt. On a nonzero exit, retain standard error for
+diagnosis and ignore all standard-output bytes: a failed receipt write may have
+left a partial document.
+
+## Discover Required Artifacts
+
+Decode the successful receipt and accept the schema versions supported by the
+caller. Use its `output_directory` as the bundle root. For the production JSON
+output, resolve `index_file` under that root with a confinement check and reject
+an absolute path or a result that escapes the root.
+
+Read the resulting `index.json` and locate each artifact by `lane_id`, not by a
+guessed filename. Before decoding a selected payload, verify its descriptor's
+media type and schema identity against the relevant published artifact
+contract. The JSON bundle contract links to the available lane contracts.
+
+If `index.json` has an `evidence_context` descriptor, treat it as a
+pipeline-wide artifact rather than a lane entry. Verify its six descriptor
+fields before decoding the linked file according to the [Published Evidence
+Context contract](../integrations/evidence-context.md). Decode its top-level
+source-unit array as a reading excerpt. Obtain authoritative citations and lane
+provenance from the normalized lane artifacts; the excerpt has neither and its
+nearby units do not widen a lane artifact's cited source reference.
+
+A zero exit status may still report rejected outputs, warnings, or absent
+lanes. The caller decides which lane IDs are required for its own work and
+which are optional; it should make that decision explicitly rather than infer
+failure from the receipt counts alone.
+
+When complete validation is required, also require receipt
+`validation_status: approved` and inspect `validation_summaries`. A successful
+run with `validation_status: incomplete` contains a structurally valid result
+that advanced after validator execution could not complete under the configured
+`warn_continue` policy. It is not reusable checkpoint state and should not be
+silently treated as fully reviewed by the caller.
+
+## Preserve Provenance And Handle Data Carefully
+
+Keep the receipt with the published `manifest.json`, and retain
+`rejected.json` and `warnings.json` when review or later provenance requires
+them. Treat the input, output bundle, cache, debug bundle, and captured process
+logs as potentially sensitive data. Apply the caller's access controls and
+retention policy, and avoid copying secrets into arguments, logs, or
+provenance records. An evidence-context artifact contains source-unit text and
+metadata and can cover most of an input; preserve and share it only when that
+source content is authorized for the recipient.

docs/development.md

@@ -17,12 +17,15 @@ implemented component map.
 | Application shape, package boundaries, contracts, dependency direction, runtime guarantees, or safety properties | [Architecture](policy/architecture.md) and relevant [ADRs](adr/) | Architecture defines the intended system and its invariants; ADRs preserve significant decision rationale. |
 | Any documentation addition or revision | [Documentation Policy](policy/documentation.md) | It defines canonical homes, audiences, current-behavior rules, and maintenance requirements. |
 | Adding, changing, reviewing, or deleting tests | [Testing Policy](policy/testing.md) | It defines risk-based sufficiency, durable test boundaries, test-double guidance, and criteria for retaining tests. |
+| CLI composition or command behavior | [CLI Internals](internal/cli.md) and [CLI Reference](cli.md) | The internal guide owns composition and command flow; the reference owns public syntax. |
+| Building a subprocess caller or changing its result protocol | [Subprocess Consumer Guide](consumers/subprocess.md), [Complete D&D Consumer Guide](consumers/dnd-pipeline.md), [Run Result Receipt](integrations/run-result.md), and [CLI Internals](internal/cli.md) | These separate generic caller workflow, the complete D&D workflow, the durable receipt contract, and CLI implementation behavior. |
+| Configuration loading, resolution, or user-visible configuration behavior | [Configuration Internals](internal/configuration.md) and [Configuration](config.md) | The internal guide owns loading and resolution mechanics; the reference owns the configuration contract. |
 | Pipeline resolution or execution | [Pipeline Internals](internal/pipeline.md) | It documents profiles, references, validation, retries, checkpoints, and runner behavior. |
-| Production modules or validators | [Module Internals](internal/modules.md) | It documents implemented module contracts, capabilities, assets, and registration. |
-| LLM clients, prompts, schemas, profiles, or scheduling | [LLM Runtime](internal/llm.md) | It documents the transport boundary and Scriptorium integration. |
+| Production modules or validators | [Module Internals](internal/modules.md), [D&D Module Internals](internal/dnd.md), and [D&D integration contracts](integrations/) | The generic guide owns extension mechanics, the D&D guide owns shared family conventions, and the contracts own durable output shapes. |
+| LLM clients, prompts, schemas, profiles, or scheduling | [LLM Runtime](internal/llm.md) | It documents the transport boundary and PromptKit integration. |
 | Output, cache, resume, or debug artifacts | [Run State Internals](internal/state.md), [Operations](operations.md), and [Configuration](config.md) | These separate implementation details, operator behavior, and configuration contracts. |
-| CLI or user-visible configuration behavior | [CLI Reference](cli.md) and [Configuration](config.md) | These are the canonical user and operator references. |
 | External input formats, artifact schemas, or durable output files | [Integration Contracts](integrations/) | Integration documents define external and durable data contracts. |
+| Release preparation, tagging, publication, or verification | [Source Releases](release.md) and [Documentation Policy](policy/documentation.md) | The release procedure owns maintainer guards and immutable-tag recovery; the policy assigns release-note ownership. |
 | Proposed or unimplemented behavior | [Roadmap](roadmap/) | Future work belongs only in roadmap documentation until implemented. |
 
 For an existing subsystem, also inspect its focused tests and the package-local

docs/integrations/chunk-map.md

@@ -1,83 +1,81 @@
 # Accepted Chunk Map
 
-This document defines the durable accepted chunk-map artifact that the JSON
-output encoder can write as `chunk-map.json`. It describes the exact accepted,
-materialized chunks used by a run; it is not a lane artifact and is never an
-input to later pipeline steps. Enable it with the JSON output option described
-in [Configuration](../config.md#json-output-options).
+This document defines the optional durable `chunk-map.json` artifact in a
+[published JSON bundle](json-output.md). It describes the accepted,
+materialized chunk plan used by one run. It is not a lane payload and is never
+an input to a later pipeline step.
 
-## Identity
+## Contract Identity
 
-- Artifact kind: `source/chunk-map`
-- Logical file: `chunk-map.json`
-- Schema ID: `notarius.source.chunk_map`
-- Schema name: `notarius_source_chunk_map_v1`
-- Schema version: `v1`
-- Media type: `application/json`
+| Property | Value |
+| --- | --- |
+| Artifact kind | `source/chunk-map` |
+| Logical file | `chunk-map.json` |
+| Media type | `application/json` |
+| Schema ID | `notarius.source.chunk_map` |
+| Schema name | `notarius_source_chunk_map_v1` |
+| Schema version | `v1` |
 
-The checked-in [JSON Schema](../../internal/framework/chunkmap/assets/schemas/source_chunk_map.v1.json)
-defines the strict wire shape. `chunk-map.json` is listed by the optional
-`chunk_map` descriptor in [the JSON output index](json-output.md#indexjson),
-not by the lane-oriented `output_files` collection.
+The optional `chunk_map` descriptor in `index.json` identifies this artifact.
+Export is controlled by the JSON output binding described in
+[Configuration](../config.md#module-bindings-and-validators).
 
-## Payload
+## Wire Shape
 
-The payload has these required fields:
+Every payload has these required fields:
 
-- `source_id`: accepted source-document identity.
-- `source_digest`: canonical lower-case `sha256:` digest of that document.
-- `plan_digest`: canonical lower-case `sha256:` digest of the accepted logical
-  plan.
-- `requested_chunker`: chunk module selected by the current resolved pipeline.
-- `producer`: the original accepted-plan producer, with required
-  `input_module` and `chunk_module`; `llm_profile` is present only for an
-  LLM-backed producer.
-- `plan_annotations`: accepted plan-level annotation namespace map. It is
-  `{}` when no namespaces are present.
-- `chunks`: non-empty execution-order collection of accepted chunks.
+| Field | Meaning |
+| --- | --- |
+| `source_id` | Accepted source-document identity. |
+| `source_digest` | Lower-case `sha256:` digest of that source document. |
+| `plan_digest` | Lower-case `sha256:` digest of the logical chunk plan. |
+| `requested_chunker` | Chunk module selected by the resolved pipeline. |
+| `producer` | Original accepted-plan producer. `input_module` and `chunk_module` are required; `llm_profile` is optional. |
+| `plan_annotations` | Plan-level annotation namespace map; `{}` when none are present. |
+| `chunks` | Non-empty execution-order chunk collection. |
 
-Each chunk has `id`, zero-based `index`, `source_ref`, positive `unit_count`,
-and an explicit `annotations` namespace map. A source reference has the source
-ID and inclusive positive `start_unit_id` and `end_unit_id` endpoints.
-Annotation values are arbitrary valid JSON under non-empty namespaces. They
-are preserved as canonical JSON without interpreting any module-specific
-namespace.
+Each `chunks` entry contains non-empty `id`, zero-based `index`, `source_ref`,
+positive `unit_count`, and an explicit `annotations` map. `source_ref` contains
+the same `source_id` as the top-level value plus positive inclusive
+`start_unit_id` and `end_unit_id` values. Endpoints identify source units; their
+numeric values do not by themselves establish source-document order.
 
-## Invariants
+Annotation namespaces are non-empty trimmed strings. Their values are arbitrary
+valid JSON and are retained without interpreting a module-specific namespace.
 
-The framework constructs this artifact only after materializing the selected
-logical plan and accepting it through the configured chunk validator chain.
-Construction proves the source and plan digests, source-document range order,
-materialized chunk IDs and indexes, source references, unit membership and
-counts, and plan/range annotations agree exactly. Chunk IDs are unique and
-indexes are contiguous and agree with array order.
+## Ordering And Validation
 
-The codec rejects unknown fixed-object fields, malformed identities or
-digests, invalid annotation JSON, trailing JSON content, and any payload whose
-reconstructed logical plan does not reproduce `plan_digest`. It makes
-defensive copies at serialization and decoding boundaries.
+`chunks` are in execution order. Their indexes are contiguous, start at zero,
+and equal their array positions; chunk IDs are unique. The emitted map is built
+only after the selected plan has been accepted and materialized against the
+source document, so its ranges, unit counts, annotations, and digests describe
+that exact plan.
 
-## Acceptance And Provenance
+The codec rejects malformed JSON, trailing content, unknown fixed-object
+fields, invalid identities or digests, invalid annotations, duplicate chunk
+IDs, non-contiguous indexes, and a `plan_digest` that does not match the
+reconstructed logical plan. The checked-in
+[schema](../../internal/framework/chunkmap/assets/schemas/source_chunk_map.v1.json)
+defines the strict JSON shape.
 
-The artifact is available only when the chunk plan was accepted. It remains
-available when a later extraction, merge, or normalization result is rejected;
-it is absent when chunk validation rejects the candidate plan.
+## Valid Example
 
-`requested_chunker` describes the current pipeline selection. `producer`
-describes who originally produced the accepted plan. On a cache hit these can
-differ: the accepted ranges, annotations, digests, and stable materialized IDs
-are reused, while the producer remains the stored producer. Cache paths,
-actions, references, metadata, warnings, timestamps, and detailed provenance
-remain in the run manifest rather than this payload.
+The compact
+[source chunk-map fixture](../../internal/framework/chunkmap/testdata/source_chunk_map.v1.json)
+is decoded by the production codec and demonstrates an accepted map with
+annotations, producer identity, and ordered chunks.
 
-## Data Handling
+## Publication And Compatibility
 
-The map contains structure, not source content. It excludes transcript bytes,
-materialized units, source-unit metadata, chunk content, private model
-responses, rejected proposals, debug data, external-reference content, and
-filesystem paths.
+The map is present only when a chunk plan was accepted and its export is
+enabled. It remains publishable if a later lane is rejected, but is absent when
+chunk-plan validation rejects the plan. `requested_chunker` identifies the
+current pipeline selection, while `producer` identifies the component that
+originally produced the accepted plan; they may differ when an accepted plan is
+reused.
 
-Annotations can nevertheless be source- or model-derived. Treat an enabled
-`chunk-map.json` with the same sensitivity and retention expectations as lane
-output. Physical placement, confined atomic writing, and permissions follow
-the ordinary [output operation](../operations.md#output).
+The map contains structure rather than source content: it excludes transcript
+bytes, source-unit metadata, chunk text, private model output, reference
+content, debug data, and filesystem paths. Treat the exported map with the
+same care as other published output. Publication location and retention are
+defined in [Operations](../operations.md#output-bundles).

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

@@ -1,10 +1,10 @@
-# D&D Combat-Turn Artifact Contract
+# D&D Combat-Turn Artifact
 
-This document defines the durable artifact, serialization, extraction,
-candidate-validation, normalization, and production lane boundaries for D&D
-combat turns.
+This contract defines the durable combat-action occurrence list produced by
+`dnd/combat-turns`. It records source-grounded turns and actions; it is not a
+complete initiative tracker, combat summary, or state model.
 
-## Artifact identity
+## Identity and compatibility
 
 | Property | Value |
 | --- | --- |
@@ -14,167 +14,58 @@ combat turns.
 | Schema version | `v1` |
 | Media type | `application/json` |
 
-The top-level JSON object contains the required `combat_turns` array, which
-may be empty. Every object rejects unknown fields.
+`v1` is a strict JSON object with required `combat_turns`; the array may be
+empty. Turn and source-reference objects reject unknown fields. An incompatible
+shape change requires a new schema version.
 
-## JSON shape
+## Wire shape
 
-Each combat turn contains these required fields:
+Each combat turn has these required fields:
 
-| Field | Shape |
+| Field | Contract |
 | --- | --- |
-| `actor` | Non-empty string. |
-| `turn_kind` | One of `turn`, `reaction`, `legendary_action`, `lair_action`, or `other`. |
-| `source_refs` | Required array with at least one source reference. |
+| `actor` | Non-empty acting character or creature name. |
+| `turn_kind` | `turn`, `reaction`, `legendary_action`, `lair_action`, or `other`. |
+| `source_refs` | One or more transcript evidence ranges. |
 
-Source references use the shared source-reference shape:
+Each source reference has exactly `source_id`, `start_unit_id`, and
+`end_unit_id`. It identifies an inclusive current-transcript range; unit IDs
+are positive and the start may not follow the end.
 
 ```json
 {
-  "source_id": "session-alpha",
-  "start_unit_id": 1,
-  "end_unit_id": 2
+  "combat_turns": [
+    {
+      "actor": "Mira Thorn",
+      "turn_kind": "turn",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 31, "end_unit_id": 32}
+      ]
+    }
+  ]
 }
 ```
 
-`source_id` must be non-empty and both unit IDs must be positive integers. The
-codec does not resolve references against a source document or enforce source
-range ordering; those checks belong to the later source-reference validation
-boundary.
+## Eligibility, evidence, and normalized form
 
-## Codec behavior
+The extractor requires an approved [scene-description artifact](dnd-scene-description-artifacts.md).
+It emits combat turns only for a chunk with an exact matching scene classified
+`combat`; an exact non-combat scene produces an accepted empty list. The scene
+record controls eligibility only: its title, summary, and reference do not
+become turn evidence. No exact matching scene also produces an empty list and
+the `scene_classification_unavailable` warning.
 
-The codec exposes two representations of the same typed artifact:
+An optional normalized [NPC registry artifact](dnd-npc-registry-artifacts.md) can ground an
+actor name. Its registry references are provenance, never combat evidence.
+Normalization trims and, where possible, canonicalizes actor names; orders and
+deduplicates exact source references; orders valid-evidence turns by source
+chronology; and collapses only duplicates with the same actor identity, turn
+kind, and complete valid evidence. It does not infer turns, initiative, or
+actions from registry or scene data.
 
-- Candidate encode/decode preserves invalid actor and turn-kind values,
-  collection presence, and source references so later validators can report
-  them. Candidate decoding still requires valid JSON, one JSON value, known
-  fields, and compatible JSON types.
-- Approved encode/decode enforces the structural rules in this contract.
-
-The codec owns the durable JSON Schema, whose object layers all set
-`additionalProperties` to `false`. Codec metadata contains only
-`combat_turn_count`.
-
-The maintained compact fixture is
-`internal/modules/dnd/codec/combatturns/testdata/dnd_combat_turns.v1.json`.
-
-## Extraction boundary
-
-The standalone extractor uses these identities:
-
-| Property | Value |
-| --- | --- |
-| Extractor key | `dnd/combat-turns` |
-| Capability | `dnd.combat_turns` |
-| Prompt ID | `dnd.combat_turns` |
-| Prompt version | `v1` |
-| Private response-schema key | `dnd_combat_turns_llm` |
-| Private response-schema ID | `notarius.dnd.combat_turns.llm` |
-| Default profile | `gemini-2-flash` |
-
-It requires `chunks` and `source.transcript`, accepts no options, and requires
-one `scene_descriptions` reference. That reference must be exactly one approved
-`dnd/scene-description-list` artifact with media type `application/json` and a
-maximum size of 1 MiB (1048576 bytes). It may be an external file validated
-during preparation or a canonical generated artifact supplied at an ordered
-step handoff. An unbound slot is a configuration error.
-
-The scene artifact controls eligibility, not evidence. The extractor calls the
-LLM only when exactly one record has the current chunk's ID, source ID, start
-unit ID, and end unit ID, and that record has `kind: combat`. An exact
-`narrative`, `recap`, or `meta` record returns an accepted empty
-`combat_turns` array without an LLM call, warning, or retry attempt. A missing
-or mismatched exact record returns the same accepted empty result without an
-LLM call or retry and emits one content-safe
-`scene_classification_unavailable` warning. The scene artifact, its title and
-summary, and its source references are never copied into combat turns.
-
-For an eligible combat chunk, the prompt receives the 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. `scene_descriptions` is never a
-combat prompt input.
-
-The private response envelope has the same turn fields and JSON types as the
-durable shape except that source references contain only `start_unit_id`
-and `end_unit_id`. It enforces required field presence, types, and
-unknown-field rejection, while deterministic validators own enum membership,
-non-empty values and collections, and positive-number requirements. The
-extractor assigns the current source ID, removes exact duplicate ranges, and
-stable-sorts turns by the earliest valid source-document position. Numeric unit
-IDs are identifiers; source-document slice position determines chronology.
-Semantically malformed candidate fields remain in the typed result for the
-configured validation and retry boundary.
-
-## Deterministic candidate validation
-
-The standalone validator keys are:
-
-| Validator | Responsibility |
-| --- | --- |
-| `extract/dnd/combat-turns/shape` | Required list, actor, turn kind, and source references, plus supported turn-kind values. |
-| `extract/dnd/combat-turns/source_refs` | Source identity, source-unit existence, and range order through the source document. |
-| `extract/dnd/combat-turns/source_relatedness` | At most one advisory warning per turn when the actor is not related to cited transcript text. |
-
-Source-reference and relatedness validators defer malformed shape to the shape
-validator. Relatedness also defers when any cited source range is invalid. It
-combines overlapping cited ranges once in document order and compares actors
-with the shared Unicode-aware NPC identity policy.
-
-The production D&D registrar exposes the extractor and these validators. Its
-default extraction chain preserves this order: JSON syntax, combat shape,
-source references, private response schema, then source relatedness.
-
-## Normalization boundary
-
-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. 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
-the actor, canonicalizes exact registry actor matches, orders and deduplicates
-exact source references, stable-sorts records by earliest valid source-document
-position, and collapses only records with the same actor identity, turn kind,
-and complete valid evidence set. The first normalized record is retained.
-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. 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 actor display normalization, canonical evidence ordering,
-chronology, and duplicate identity. It rejects
-with `invalid_combat_turn_normalization` under policy
-`dnd.combat_turns.validator.normalized.v1`.
-
-The production D&D registrar exposes the normalizer and normalized-invariants
-validator. Its default normalization chain is JSON syntax, combat shape,
-normalized invariants, source references, durable schema, then source
-relatedness. The lane uses the framework's typed append-order merger and has no
-merge validator chain.
-
-## Production manifest and references
-
-The selectable lane uses extractor and normalizer key `dnd/combat-turns`,
-`appendorder` for the typed merger, and the durable codec above. Bound external
-references contribute raw-file provenance to the run manifest. Generated
-bindings contribute artifact kind, schema identity, media type, canonical
-digest, size, and bounded producer provenance. This includes the generated
-scene-description artifact for the combat extractor. Consumer metadata and
-checkpoint fingerprints contain no reference names, content, paths, source
-ranges, scene titles, or scene summaries. For an external scene artifact,
-component metadata records the gate policy plus a semantic eligibility digest
-and record count; generated scene identity remains in framework handoff
-provenance and dependencies. The eligibility digest changes with scene ID,
-exact source range, or kind, but not with title or summary. 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.
+The [NPC-occurrence artifact](dnd-npc-occurrence-artifacts.md) records
+broader NPC occurrences. The [enemy-event artifact](dnd-enemy-event-artifacts.md)
+uses combat turns as grounding only; turns do not establish an enemy event or
+its outcome. The [JSON output contract](json-output.md) defines publication,
+and [D&D module internals](../internal/dnd.md) describes routing and validation
+mechanics.

docs/integrations/dnd-enemy-event-artifacts.md

@@ -0,0 +1,114 @@
+# D&D Enemy-Event Artifact
+
+This contract defines the durable, source-grounded enemy-event occurrence list.
+It records enemies directly established as opposing the party and explicitly
+observed combat outcomes. It is an ordered observation artifact from which a
+consumer may derive a ledger; it is not a ledger, encounter roster, or terminal
+state model.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/enemy-event-list` |
+| Schema ID | `notarius.dnd.enemy_events` |
+| Schema name | `notarius_dnd_enemy_events_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+
+`v1` is a strict JSON object with required `events`; the array may be empty.
+Event and source-reference objects reject unknown fields. An incompatible shape
+change requires a new schema version.
+
+## Wire shape
+
+Every event has these required fields:
+
+| Field | Contract |
+| --- | --- |
+| `name` | Non-empty display name or directly grounded collective subject label. |
+| `kind` | `engaged`, `killed`, `fled`, `captured`, or `incapacitated`. |
+| `source_refs` | One or more current-transcript evidence ranges. |
+
+Each source reference has exactly `source_id`, `start_unit_id`, and
+`end_unit_id`. It identifies an inclusive current-transcript range; unit IDs
+are positive and the start may not follow the end.
+
+```json
+{
+  "events": [
+    {
+      "name": "Ashfang",
+      "kind": "engaged",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 41, "end_unit_id": 42}
+      ]
+    },
+    {
+      "name": "Ashfang",
+      "kind": "fled",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 57, "end_unit_id": 58}
+      ]
+    }
+  ]
+}
+```
+
+## Event semantics and evidence
+
+| Kind | Required evidence |
+| --- | --- |
+| `engaged` | The subject is directly established as actively opposing the party in combat. At most one engagement is emitted for one subject in one combat scene. |
+| `killed` | The transcript explicitly establishes that the subject died or was killed. Damage, defeat, disappearance, or combat ending is insufficient. |
+| `fled` | The subject explicitly escapes, retreats, or otherwise leaves combat to avoid continued engagement. Movement or absence from later turns is insufficient. |
+| `captured` | The subject is explicitly taken prisoner or secured under the party's control. A grapple or temporary restraint alone is insufficient. |
+| `incapacitated` | The subject is explicitly rendered unable to continue acting without being established as killed or captured. A missed turn is insufficient. |
+
+The current transcript is the only event evidence. Campaign context and
+normalized NPC, scene-description, combat-turn, and NPC-occurrence artifacts
+can ground names or control combat eligibility, but none may supply event
+evidence. An outcome may share evidence with an engagement, in which case both
+events are retained.
+
+Extraction is limited to chunks with an exact combat-scene classification. An
+exact non-combat classification produces an accepted empty list. Missing or
+mismatched classification also produces an accepted empty list and a
+`scene_classification_unavailable` warning.
+
+## Subjects, normalization, and order
+
+A subject matching the normalized NPC registry uses that registry's canonical
+display name. Unmatched hostile creatures, summoned entities, and directly
+grounded groups remain valid subjects. An unnamed homogeneous group uses the
+narrowest transcript-grounded label, such as `Orcs`, `One orc`, or `Remaining
+orcs`; the artifact never invents synthetic member identities or quantities.
+Party members, allies, neutral observers, mentioned-but-absent enemies, hazards,
+traps, and environmental effects are excluded.
+
+Normalization collapses surrounding and repeated internal whitespace in subject
+display values, canonicalizes recognized registry names, canonicalizes and
+deduplicates exact source ranges, then orders events by valid evidence
+chronology, normalized subject identity, display name, kind, and reference
+sequence. The deterministic kind tie order is `engaged`,
+`incapacitated`, `captured`, `fled`, then `killed`. Only entries with the same
+normalized name, kind, and complete canonical evidence sequence are collapsed.
+Different kinds, evidence, repeated engagement in separate scenes, and later
+outcomes remain separate. A later engagement for the same named subject is
+preserved after an earlier outcome because the artifact does not assert an
+irreversible state transition.
+
+## Non-goals
+
+The artifact has no NPC or scene ID, quantity, confidence, description,
+rationale, summary, current state, or inferred terminal outcome. It does not
+emit `active` or `unresolved`; consumers may derive an unresolved ledger view
+only when an engagement has no later explicit outcome. It never infers an
+outcome from turn absence, scene termination, initiative order, hit-point
+guesses, or other artifacts.
+
+The [JSON output contract](json-output.md) defines publication. Configuration
+keys, required generated-reference slots, and validator-chain selection are
+defined in the [configuration reference](../config.md). Implementation and
+prompt-grounding mechanics are described in the
+[D&D module internals](../internal/dnd.md).

docs/integrations/dnd-item-event-artifacts.md

@@ -1,133 +0,0 @@
-# D&D Item-Event Artifact Contract
-
-This document defines the durable D&D item-event artifact and its production
-boundaries. It records source-grounded discoveries and possession changes; it
-does not maintain an inventory or ledger.
-
-## Artifact Identity
-
-| Property | Value |
-| --- | --- |
-| Extractor key | `dnd/item-events` |
-| Extract capability | `dnd.item_events` |
-| Artifact kind | `dnd/item-event-list` |
-| Schema ID | `notarius.dnd.item_events` |
-| Schema name | `notarius_dnd_item_events_v1` |
-| Schema version | `v1` |
-| Media type | `application/json` |
-| Normalizer key | `dnd/item-events` |
-
-The payload is one strict JSON object containing a required `events` array,
-which may be empty. Objects reject unknown fields.
-
-## Event Shape And Categories
-
-Every event has `name`, `kind`, and a non-empty `source_refs` array. `quantity`
-is optional and, when present, is a positive integer. `from` and `to` are
-optional display values whose presence depends on `kind`.
-
-| Field | Rule |
-| --- | --- |
-| `name` | Non-empty, transcript-supported display value. |
-| `kind` | One of the categories below. |
-| `quantity` | Optional positive integer; omitted when the source does not establish a count. |
-| `from` | Holder that loses possession when the category permits it. |
-| `to` | Holder that gains possession when the category permits it. |
-| `source_refs` | One or more current-source references. |
-
-| Kind | Meaning and holder rule |
-| --- | --- |
-| `discovered` | The party learns of or encounters an item without established possession; neither holder is present. |
-| `acquired` | A party member or `party` gains possession; `to` is required and `from` is absent. |
-| `lost` | A party member or `party` ceases to possess an item without consuming it; `from` is required and `to` is absent. |
-| `consumed` | Use depletes, expends, or destroys an item; `from` is required and `to` is absent. |
-| `transferred` | Possession moves between distinct party members; both holders are required and neither may be `party`. |
-
-`party` is the reserved display holder for collective party possession when an
-individual holder is not established. Its comparison is case- and
-Unicode-insensitive. Transfers require distinct normalized holder values.
-Giving an item to an NPC, spending currency, selling an item, or another move
-outside party possession is `lost`, not `transferred` or `consumed`. Monetary
-spending, purchases, and payments are always `lost`. Currency is `consumed` only
-when the source explicitly describes its physical destruction or expenditure as
-a non-payment component. Ordinary non-depleting use is not an event.
-
-Currency is represented as an ordinary event name plus an explicit quantity
-when the transcript supplies one. Each denomination remains separate. The
-artifact never converts denominations, infers a missing count, calculates a
-balance, or sums nearby events.
-
-## Source Evidence And Normalization
-
-Each source reference contains `source_id`, `start_unit_id`, and `end_unit_id`.
-It must identify an ordered range in the current source document. During
-extraction, every cited range must also be wholly contained in the current
-accepted chunk. Campaign references may disambiguate names, but never provide
-event evidence.
-
-The deterministic normalizer trims only display-edge whitespace in names and
-holders, canonicalizes source-reference order and exact duplicate references,
-then orders events by earliest valid source position and stable tie-breakers
-over name, kind, holders, quantity, and complete evidence. It removes only
-events with the same normalized fields and complete valid evidence sequence.
-Invalid evidence is never collapsed. It does not rename, singularize, resolve
-aliases, infer holders or quantities, or merge nearby events.
-
-The default extraction validation chain is JSON syntax, item-event shape,
-source references, durable JSON Schema, then advisory source relatedness. The
-normalization chain adds normalized invariants after shape validation and before
-source references and schema validation. Relatedness warnings are advisory so
-contextual names and currency notation do not reject otherwise valid evidence.
-
-## Representative JSON
-
-```json
-{
-  "events": [
-    {
-      "name": "Hidden Cache",
-      "kind": "discovered",
-      "source_refs": [{"source_id": "session-7", "start_unit_id": 1, "end_unit_id": 1}]
-    },
-    {
-      "name": "Silver Pieces",
-      "kind": "acquired",
-      "quantity": 20,
-      "to": "party",
-      "source_refs": [{"source_id": "session-7", "start_unit_id": 2, "end_unit_id": 2}]
-    },
-    {
-      "name": "Torch",
-      "kind": "lost",
-      "from": "party",
-      "source_refs": [{"source_id": "session-7", "start_unit_id": 3, "end_unit_id": 3}]
-    },
-    {
-      "name": "Healing Potion",
-      "kind": "consumed",
-      "from": "Aria",
-      "source_refs": [{"source_id": "session-7", "start_unit_id": 4, "end_unit_id": 4}]
-    },
-    {
-      "name": "Moonblade",
-      "kind": "transferred",
-      "from": "Aria",
-      "to": "Borin",
-      "source_refs": [{"source_id": "session-7", "start_unit_id": 5, "end_unit_id": 5}]
-    }
-  ]
-}
-```
-
-## Production Boundary
-
-The extractor requires `chunks` and `source.transcript`, and accepts optional
-`glossary`, `party`, `players`, and deprecated `roster` campaign references for
-disambiguation only. It has no generated NPC, scene-description, or item-registry
-dependency. The append-order merger preserves chunk order, and the normalizer
-has no reference slots.
-
-The normalized lane is emitted as `lanes/<lane-id>.json` by the JSON output
-module. See [Configuration](../config.md#implemented-production-modules) for
-the selectable keys and default chains, and the
-[JSON output contract](json-output.md) for bundle paths.

docs/integrations/dnd-item-occurrence-artifacts.md

@@ -0,0 +1,72 @@
+# D&D Item-Occurrence Artifact
+
+`dnd/item-occurrences` currently produces this source-grounded item and currency
+occurrence list. It records discoveries and possession changes, not an
+inventory, balance, or ledger.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/item-occurrence-list` |
+| Schema ID | `notarius.dnd.item_occurrences` |
+| Schema name | `notarius_dnd_item_occurrences_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+
+`v1` accepts one strict JSON object with required `occurrences`; the array may
+be empty. Each occurrence has required `item_id`, `name`, `kind`, and
+`source_refs`, and occurrence and source-reference objects reject unknown
+fields. `quantity`, `from`, and `to` appear only when their kind permits them.
+An incompatible shape change requires a new schema version.
+
+## Registry grounding
+
+Both extraction and normalization require an `item_registry` reference bound to
+an earlier normalized `dnd/item-registry` artifact. The registry is immutable
+for an operation and contributes names-only grounding after the shared evidence
+message. Notarius resolves the model's selected name into the unchanged exact
+durable ID/name pair. It is never occurrence evidence.
+
+Each occurrence must use one exact registry ID/name pair. An extraction response
+with an unknown or ambiguous selected name is rejected as invalid model output;
+the configured pipeline may retry it and never accepts a partial artifact.
+Normalization and validation remain defense in depth for artifacts entering
+through other boundaries: normalization canonicalizes a recognized name by ID,
+preserves unknown values for the registry validator, and the registry validator
+rejects unknown or mismatched pairs.
+
+## Wire shape
+
+Each source reference has exactly `source_id`, `start_unit_id`, and
+`end_unit_id`. It identifies an inclusive range in the current transcript;
+unit IDs are positive and the start may not follow the end.
+
+```json
+{
+  "occurrences": [
+    {
+      "item_id": "item:sha256:…",
+      "name": "Silver Pieces",
+      "kind": "acquired",
+      "quantity": 20,
+      "to": "party",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 2, "end_unit_id": 2}
+      ]
+    }
+  ]
+}
+```
+
+The five kinds remain `discovered`, `acquired`, `lost`, `consumed`, and
+`transferred`. Holder, quantity, currency, ordering, and exact-duplicate rules
+are unchanged: discovered has no holder; acquired requires `to`; lost and
+consumed require `from`; transferred requires distinct non-`party` holders.
+The only current downstream compatibility requirement is its registry handoff;
+the normalized occurrence list is otherwise published for callers. See
+[Configuration](../config.md#d-d-reference-slots) for the binding and
+[JSON output](json-output.md) for publication.
+
+See [item registry](dnd-item-registry-artifacts.md) for the grounding artifact
+and [D&D module internals](../internal/dnd.md) for implementation details.

docs/integrations/dnd-item-registry-artifacts.md

@@ -0,0 +1,95 @@
+# D&D Item Registry Artifact
+
+This contract defines the durable, source-grounded item registry produced by
+`dnd/item-registry`. It records transcript-established item types and unique
+designations for one source document; it is not an inventory, holder record,
+quantity ledger, or item-occurrence artifact.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/item-registry` |
+| Schema ID | `notarius.dnd.item_registry` |
+| Schema name | `notarius_dnd_item_registry_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+| Identity policy | `dnd.item_registry.identity.v1` |
+
+`v1` accepts one strict JSON object with required `items`; the array may be
+empty. Item and source-reference objects reject unknown fields. An incompatible
+artifact shape or identity-policy change uses a new version or policy.
+
+## Wire shape and identity
+
+Each item has these required fields:
+
+| Field | Contract |
+| --- | --- |
+| `id` | `item:sha256:` followed by 64 lowercase hexadecimal characters. |
+| `name` | Non-empty transcript-established item type or unique designation. |
+| `source_refs` | One or more transcript evidence ranges that establish the item. |
+
+A source reference has exactly `source_id`, `start_unit_id`, and `end_unit_id`.
+The source ID identifies the transcript, unit IDs are positive inclusive unit
+identifiers, and the start may not follow the end.
+
+```json
+{
+  "items": [
+    {
+      "id": "item:sha256:31e73b6280ef98e4d8070e07fd4de9b2c3e842cc03af1a09ca631cb95b73e3b3",
+      "name": "Star Compass",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 4, "end_unit_id": 5}
+      ]
+    }
+  ]
+}
+```
+
+The ID is deterministic for an item name or type, rather than for one physical
+instance. Notarius normalizes the display name for comparison with Unicode
+NFKC, supported apostrophe normalization, collapsed whitespace, and case
+folding. It hashes compact JSON for this array:
+
+```text
+["dnd.item_registry.identity.v1", comparison_name]
+```
+
+The canonical ID is the lowercase SHA-256 digest of those bytes with the
+`item:sha256:` prefix. Equal comparison names represent one item identity;
+normalization unions their transcript evidence when it safely consolidates a
+candidate group.
+
+## Scope, reconciliation, and evidence
+
+The registry includes named unique items, concrete reusable item types, stable
+unique designations, and separately established currency denominations. It
+excludes vague loot or treasure, generic weapons, quantities, inferred
+properties, and inferred uniqueness. Capitalization alone does not establish
+eligibility.
+
+Normalization first applies deterministic display, evidence, and ID rules. It
+then may use a bounded LLM-assisted proposal to reconcile semantically duplicate
+records. The proposal may choose only a supplied candidate display name;
+invalid, uncertain, overlapping, or unsafe proposals retain the deterministic
+result with retry or fallback diagnostics. A proposal that mixes a recognized
+currency denomination with a non-currency item, or combines recognized
+denominations, is unsafe and retains every deterministic record. Currency
+denominations, materially different item types, and merely nearby objects
+remain distinct. Source references establish registry provenance, not evidence
+for later artifacts.
+
+## Consumers and publication
+
+`dnd/item-occurrences` requires one approved item registry through its
+`item_registry` reference slot for both extraction and normalization. Its
+consumer receives names-only grounding; Notarius resolves the selected name
+into the unchanged exact durable ID/name pair. The registry’s source references
+are never occurrence evidence. Unknown or ambiguous selections are rejected by
+the occurrence contract. See the
+[item-occurrence artifact](dnd-item-occurrence-artifacts.md) for that strict
+wire contract, [Configuration](../config.md#d-d-reference-slots) for binding
+rules and validator selection, and the [JSON output contract](json-output.md)
+for publication.

docs/integrations/dnd-location-occurrence-artifacts.md

@@ -0,0 +1,86 @@
+# D&D Location-Occurrence Artifact
+
+This contract defines the durable occurrence list produced by
+`dnd/location-occurrences`. It records source-grounded ways the party relates
+to locations in a required normalized location registry; it does not extend
+that registry or infer a place absent from it.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/location-occurrence-list` |
+| Schema ID | `notarius.dnd.location_occurrences` |
+| Schema name | `notarius_dnd_location_occurrences_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+
+`v1` accepts one strict JSON object with required `occurrences`; the array may
+be empty. Occurrence and source-reference objects reject unknown fields. An
+incompatible shape change requires a new schema version.
+
+## Wire shape
+
+Each occurrence has these required fields:
+
+| Field | Contract |
+| --- | --- |
+| `location_id` | Exact ID from the required normalized [location registry](dnd-location-registry-artifacts.md). |
+| `name` | Exact canonical display name for `location_id` in that registry. |
+| `kind` | One of `visited`, `planned`, `recalled`, or `mentioned`. |
+| `source_refs` | One or more current-transcript evidence ranges for this occurrence. |
+
+A source reference has exactly `source_id`, `start_unit_id`, and `end_unit_id`.
+It identifies an inclusive range in the current transcript; unit IDs are
+positive and the start may not follow the end.
+
+```json
+{
+  "occurrences": [
+    {
+      "location_id": "location:sha256:fb05475da0fc7debf994b517e1906ffe7209887a6a1ec306356d84de820b1a24",
+      "name": "Moon Gate",
+      "kind": "visited",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 12, "end_unit_id": 13}
+      ]
+    }
+  ]
+}
+```
+
+## Occurrence categories
+
+| Kind | Meaning |
+| --- | --- |
+| `visited` | The transcript establishes physical party presence, including arrival, continuing presence, or departure. |
+| `planned` | The party explicitly proposes, intends, or agrees to future travel; speculation alone is not enough. |
+| `recalled` | The transcript explicitly recounts prior party presence before the current live events. |
+| `mentioned` | The location is explicit but no stronger category applies, including lore, directions, third-party activity, non-actionable speculation, a mere hypothetical reference, or out-of-character discussion. |
+
+For overlapping evidence, precedence is `visited`, then `planned`, then
+`recalled`, then `mentioned`. For example, “What if we went to Moon Gate?” is
+eligible as `mentioned` when its narrow evidence explicitly references that
+registry location, but it is not `planned` without an actual proposal,
+intention, or agreement to travel. Inferred, unstated, uncertain, and
+unsupported places or occurrences are omitted. Normalization
+canonicalizes the registry name, orders and deduplicates source references, and
+orders occurrences by source chronology, location ID, name, kind, and reference
+sequence. It collapses only exact duplicates with the same ID, kind, and
+complete canonical evidence sequence.
+
+## Required grounding and evidence
+
+Both extraction and normalization require exactly one `location_registry` reference of
+kind `dnd/location-registry`, media type `application/json`, and at most 1 MiB. The
+registry provides identity grounding only. The model selects a supplied
+contextual name-and-registry-reference descriptor, and Notarius resolves it
+into the exact durable ID/name pair. Unknown, partial, or ambiguous selections
+are rejected rather than guessed or reassigned. The current transcript is the
+only evidence source for an occurrence; registry evidence and provenance never
+become occurrence evidence.
+
+See [Configuration](../config.md#d-d-reference-slots) for the selectable slot
+and generated-handoff compatibility, [D&D module internals](../internal/dnd.md)
+for implementation behavior, and the [JSON output contract](json-output.md)
+for publication.

docs/integrations/dnd-location-registry-artifacts.md

@@ -0,0 +1,93 @@
+# D&D Location Registry Artifact
+
+This contract defines the durable, source-grounded location registry produced
+by `dnd/location-registry`. It records transcript-established physical places for one
+source document; it is not a map, location hierarchy, campaign-wide world
+registry, or location description.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/location-registry` |
+| Schema ID | `notarius.dnd.location_registry` |
+| Schema name | `notarius_dnd_location_registry_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+| Identity policy | `dnd.location_registry.identity.v1` |
+
+`v1` accepts one strict JSON object with required `locations`; the array may be
+empty. Location and source-reference objects reject unknown fields. An
+incompatible artifact shape or identity-policy change uses a new version or
+policy.
+
+## Wire shape and identity
+
+Each location has these required fields:
+
+| Field | Contract |
+| --- | --- |
+| `id` | `location:sha256:` followed by 64 lowercase hexadecimal characters. |
+| `name` | Non-empty transcript-established display name. |
+| `source_refs` | One or more transcript evidence ranges that identify the place. |
+
+A source reference has exactly `source_id`, `start_unit_id`, and `end_unit_id`.
+The source ID identifies the transcript, unit IDs are positive inclusive unit
+identifiers, and the start may not follow the end.
+
+```json
+{
+  "locations": [
+    {
+      "id": "location:sha256:fb05475da0fc7debf994b517e1906ffe7209887a6a1ec306356d84de820b1a24",
+      "name": "Moon Gate",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 4, "end_unit_id": 5}
+      ]
+    }
+  ]
+}
+```
+
+The ID is deterministic and scoped to the source document. Notarius normalizes
+the display name for comparison with Unicode NFKC, supported apostrophe
+normalization, collapsed whitespace, and case folding. It hashes compact JSON
+for this array, using the earliest canonical source reference as the anchor:
+
+```text
+["dnd.location_registry.identity.v1", comparison_name, source_id, start_unit_id, end_unit_id]
+```
+
+The canonical ID is the lowercase SHA-256 digest of those bytes with the
+`location:sha256:` prefix. Equal display names are allowed when their evidence
+anchors differ, so a generic name does not force distinct places to collapse.
+
+## Scope, reconciliation, and evidence
+
+Locations are physical or spatial places established by the transcript with a
+stable proper name or unique in-world designation, such as named planes,
+regions, settlements, districts, buildings, rooms, landmarks, routes, and
+geographic features. Generic, temporary, relative, and descriptive phrases
+such as “the room,” “the bar,” “the hallway,” “outside,” and “upstairs” are not
+registry locations. Capitalization alone does not establish eligibility.
+Notarius does not infer an unstated place or add hierarchy, coordinates,
+descriptions, participants, or ownership.
+
+Normalization first applies deterministic display, evidence, and ID rules. It
+then may use a bounded LLM-assisted proposal to reconcile semantically duplicate
+records. The proposal is validated and applied conservatively; invalid or
+unusable proposals retain the deterministic result with retry or fallback
+diagnostics. The registry's source references establish registry provenance,
+not evidence for later artifacts.
+
+## Consumers and publication
+
+`dnd/location-occurrences` requires one approved location registry through its
+`location_registry` reference slot. Its prompt receives contextual selectors
+containing a canonical name and registry references; Notarius resolves a
+selection into the unchanged exact durable ID/name pair. Registry references
+must not be treated as occurrence evidence. See the
+[location-occurrence artifact](dnd-location-occurrence-artifacts.md)
+for that contract, [Configuration](../config.md#references-and-ordered-handoffs)
+for binding rules, and the [JSON output contract](json-output.md) for
+publication.

docs/integrations/dnd-npc-artifacts.md

@@ -1,160 +0,0 @@
-# D&D NPC Artifact
-
-This document defines the durable D&D NPC-list artifact, its JSON codec, and
-the selectable production NPC pipeline. The normalized JSON payload can be
-passed explicitly to the spell extractor as an optional caster-name registry
-or to the combat extractor and normalizer as an actor registry. It
-remains a reference, not spell or combat evidence.
-The NPC interaction extractor and normalizer also consume this registry for
-canonical identity; registry source references remain provenance and never
-become interaction evidence. Their occurrence contract is defined in the
-[D&D NPC interaction artifact](dnd-npc-interaction-artifacts.md).
-
-## Identity
-
-- Artifact kind: `dnd/npc-list`
-- Durable schema ID: `notarius.dnd.npcs`
-- Durable schema name: `notarius_dnd_npcs_v1`
-- Durable schema version: `v1`
-- Media type: `application/json`
-- Identity policy: `dnd.npcs.identity.v1`
-
-The durable JSON Schema is owned by the D&D NPC codec. NPC IDs are derived from
-the Unicode-normalized, case-folded canonical name using the identity policy.
-The durable codec enforces the artifact shape and ID syntax; registry identity
-validation remains a separate deterministic concern.
-
-The extractor's private LLM response schema is a separate structural transport
-contract. It omits framework-assigned NPC and source IDs and admits semantic
-candidates for the deterministic shape and source-reference validators; it is
-not part of this durable contract.
-
-## Output Shape
-
-The payload is one object with a required top-level `npcs` array:
-
-```json
-{"npcs": []}
-```
-
-The array may be empty. Every object and nested object rejects unknown fields.
-
-## NPC Fields
-
-Each NPC contains exactly these required fields:
-
-- `id`: `npc:sha256:` followed by 64 lowercase hexadecimal characters;
-- `name`: the canonical display name;
-- `source_refs`: at least one source reference supporting the NPC record.
-
-Each source reference contains required `source_id`, `start_unit_id`, and
-`end_unit_id`; unit IDs are positive integers. Source document identity, unit
-existence, and range ordering are validated by the source-reference validator
-when the artifact is used by a pipeline.
-
-## Codec Boundary
-
-`EncodeCandidate` and `DecodeCandidate` provide strict single-value JSON
-serialization while preserving typed values that still need semantic
-validation. `Encode` and `Decode` are the approved-artifact boundary and
-require all durable structural fields, non-empty required strings, valid source
-reference shapes, and the NPC ID pattern.
-
-Codec metadata contains only `npc_count`. Schema bytes and returned metadata
-are independent values so callers cannot mutate codec-owned state.
-
-## Production Pipeline
-
-The production identities are:
-
-- extractor: `dnd/npcs`;
-- artifact kind: `dnd/npc-list`;
-- normalizer: `dnd/npcs`; and
-- durable schema: `notarius.dnd.npcs`, version `v1`, media type
-  `application/json`.
-
-The extractor maps private model records to the current source identity and
-assigns deterministic IDs. Extraction validation checks shape, source
-references, and source relatedness. The normalizer first consolidates equal
-canonical-name matches, then may make one document-level LLM-assisted identity
-decision per configured normalize attempt for eligible distinctly named
-records. Consolidation is name-based: it retains a supplied canonical display
-name, keeps the earliest affected output position, derives its ID again, and
-unions exact evidence in canonical order. Ambiguous, invalid, or conflicting
-proposals are not applied; independently safe matches may still be retained.
-After the retry budget is exhausted, the safe result is accepted with bounded
-normalization warnings and the usual validation. The durable v1 artifact shape
-does not add aliases, proposal fields, or any other semantic-normalization
-representation.
-
-The extraction prompt asks only for individually identifiable NPC names backed
-by source evidence. Groups, generic roles, invented labels, and descriptive or
-relationship enrichment are outside the contract.
-
-The default extraction chain is `generic/valid_json`,
-`extract/dnd/npcs/shape`, `extract/dnd/npcs/source_refs`,
-`generic/valid_json_schema`, and `extract/dnd/npcs/source_relatedness`. The
-default normalize chain is `generic/valid_json`, `extract/dnd/npcs/shape`,
-`normalize/dnd/npcs/identity`, `extract/dnd/npcs/source_refs`,
-`generic/valid_json_schema`, and `extract/dnd/npcs/source_relatedness`.
-Relatedness emits bounded warnings when an NPC canonical name is not present
-near its cited transcript text; opaque campaign
-references may explain such a warning but do not become evidence.
-
-## Manifest And Artifact Handoff
-
-The NPC extractor records prompt and response-schema identities. The durable
-codec records only `npc_count`; raw names, source references, and payload bytes
-stay in the lane file rather than manifest
-metadata. The normalized lane can be consumed by a later ordered step through
-the registered canonical codec:
-
-```yaml
-steps:
-  - id: identify-npcs
-    artifacts:
-      npcs:
-        extract: dnd/npcs
-        normalize: dnd/npcs
-      scene-descriptions:
-        extract: dnd/scene-descriptions
-        normalize: dnd/scene-descriptions
-  - id: grounded-events
-    references:
-      npcs:
-        artifact:
-          step: identify-npcs
-          lane: npcs
-      scene_descriptions:
-        artifact:
-          step: identify-npcs
-          lane: scene-descriptions
-    artifacts:
-      spells:
-        extract: dnd/spells
-        normalize: dnd/spells
-      combat:
-        extract: dnd/combat-turns
-        normalize: dnd/combat-turns
-```
-
-The framework hands only accepted normalized artifacts across the barrier. It
-validates the canonical bytes against each consumer slot and clones the NPC
-operation-time reference for spell and combat consumers. The accompanying
-scene-description reference is required by the combat extractor for eligibility
-only; its consumer contract is defined in the
-[D&D combat-turn artifact contract](dnd-combat-turn-artifacts.md). Generated
-provenance records the artifact kind, schema identity, media type, canonical
-digest, size, and producer step/lane/module, but not names, 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.
-
-Consumers receive a separate names-only projection in normalized registry
-order, for example `{"npcs":[{"name":"Mira Thorn"}]}`. The projection omits
-IDs and evidence. Its digest covers the exact projected bytes and is used for
-consumer-local checkpoint identity, while the full durable artifact digest
-remains the manifest and generated-reference provenance identity. The unbound
-projection is exactly `{"npcs":[]}` and also has a projection digest.

docs/integrations/dnd-npc-interaction-artifacts.md

@@ -1,148 +0,0 @@
-# D&D NPC Interaction Artifact
-
-This document defines the durable D&D NPC-interaction-list artifact and its
-two-step production pipeline. It records discrete, source-grounded occurrences
-for NPCs already accepted into a normalized NPC registry; it does not expand
-the registry or summarize events.
-
-## Identity And JSON
-
-- Artifact kind: `dnd/npc-interaction-list`
-- Durable schema ID: `notarius.dnd.npc_interactions`
-- Durable schema name: `notarius_dnd_npc_interactions_v1`
-- Durable schema version: `v1`
-- Media type: `application/json`
-
-The payload is one strict JSON object with only an `interactions` array. The
-array may be empty. Each item has exactly `name`, `kind`, and `source_refs`:
-
-```json
-{
-  "interactions": [
-    {
-      "name": "Mira Thorn",
-      "kind": "dialogue",
-      "source_refs": [
-        {"source_id": "session-7", "start_unit_id": 12, "end_unit_id": 13}
-      ]
-    }
-  ]
-}
-```
-
-`name` is the canonical display name from the required NPC registry.
-`source_refs` contains one or more current-source ranges with required
-`source_id`, `start_unit_id`, and `end_unit_id`; unit IDs are positive integers.
-During extraction, every range must be wholly contained in the current accepted
-chunk. This prevents a candidate from citing valid units that were not presented
-to that extraction call.
-Unknown fields are rejected.
-
-## Interaction Categories
-
-`kind` is exactly one of:
-
-| Kind | Meaning |
-| --- | --- |
-| `mentioned` | The NPC is referred to, but is not established as present or communicating in the evidenced passage. |
-| `noncombat_presence` | The NPC is present and relevant to the passage but does not meaningfully participate in dialogue or combat. |
-| `dialogue` | The NPC speaks, responds, or is directly engaged in a meaningful non-combat exchange. |
-| `combat_ally` | The NPC actively participates in combat on the party's side. |
-| `combat_opponent` | The NPC actively participates in combat against the party. |
-| `other` | The transcript clearly establishes a direct NPC occurrence that fits none of the preceding kinds. |
-
-`other` is a residual category for positively evidenced activity, not a fallback
-for uncertain classification. When activities overlap, active combat
-participation outranks dialogue, presence, and mention; dialogue outranks
-non-combat presence and mention; and non-combat presence outranks mention.
-Combat alignment is not resolved by precedence: a meaningful change between
-ally and opponent creates separate occurrences.
-
-These categories do not encode summaries, relationships, state, motives, or
-unobserved events.
-
-## Occurrence Boundaries And Ordering
-
-One occurrence represents one NPC, one kind, and one locally coherent passage
-within one accepted chunk. Repeated evidence belongs to the same occurrence
-only while it supports the same uninterrupted activity. A kind change, combat
-alignment change, intervening scene or meaningful absence, or transition from
-mention to presence starts a new occurrence. Occurrences never span chunks, and
-merge or normalization never semantically combines nearby, overlapping, or
-cross-chunk records.
-
-Normalization orders records by:
-
-1. earliest valid source-document position;
-2. the NPC identity comparison key;
-3. the exact canonical NPC display name;
-4. interaction kind in lexical order; and
-5. the complete canonical source-reference sequence, ordered by source ID and
-   the source-document positions of each range's start and end.
-
-Only records with identical canonical names, kinds, and complete valid evidence
-sequences are duplicates. Different categories, ranges, or separately grounded
-occurrences remain separate.
-
-## Evidence, Registry, And Normalization
-
-The registry proves only the canonical NPC identity. Its source references are
-registry provenance and are never interaction evidence. Every durable
-interaction must cite current transcript units supporting both the name and its
-classification.
-
-The extractor receives a names-only registry projection such as
-`{"npcs":[{"name":"Mira Thorn"}]}`. The normalizer uses the full immutable
-registry for exact canonical-name lookup. It canonicalizes source references
-and applies the ordering and exact-duplicate rules above.
-
-## Production Pipeline
-
-The extractor and normalizer key is `dnd/npc-interactions`. Both require the
-structured `npcs` slot, so an accepted normalized registry must come from an
-earlier step:
-
-```yaml
-pipelines:
-  dnd-npc-interactions:
-    input: seriatim
-    steps:
-      - id: identify-npcs
-        artifacts:
-          npcs:
-            extract: dnd/npcs
-            normalize: dnd/npcs
-      - id: extract-interactions
-        references:
-          npcs:
-            artifact:
-              step: identify-npcs
-              lane: npcs
-        artifacts:
-          interactions:
-            extract: dnd/npc-interactions
-            normalize: dnd/npc-interactions
-```
-
-The framework passes only the accepted normalized producer. A missing, rejected,
-or incompatible NPC artifact prevents the consumer step from executing. It
-records generated artifact identity and bounded producer provenance without
-copying registry names, source ranges, or payload content into the manifest.
-
-## Validation And Metadata
-
-The default extract chain is `generic/valid_json`, interaction shape, registry,
-and source-reference validation, `generic/valid_json_schema`, then warning-only
-source relatedness. The normalize chain runs normalized invariants after
-registry validation and before source-reference and schema validation, followed
-by relatedness. Normalizer and relatedness warnings are bounded and end with an
-omission summary when necessary. The codec metadata contains only
-`interaction_count`. Extractor metadata identifies its prompt and private
-response schema; component-local checkpoint identities include the names-only
-registry projection where relevant. Generated registry identity stays in
-framework provenance and dependency fingerprints.
-
-See [Configuration](../config.md#implemented-production-modules) for selectable
-keys and chains, [the NPC artifact contract](dnd-npc-artifacts.md) for the
-registry boundary, and the copyable
-[complete D&D example](../../examples/dnd-complete.config.yml).

docs/integrations/dnd-npc-occurrence-artifacts.md

@@ -0,0 +1,90 @@
+# D&D NPC Occurrence Artifact
+
+This contract defines the durable occurrence list produced by
+`dnd/npc-occurrences`. It records discrete, source-grounded occurrences with
+NPCs already present in a normalized registry; it does not extend that registry
+or summarize the session.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/npc-occurrence-list` |
+| Schema ID | `notarius.dnd.npc_occurrences` |
+| Schema name | `notarius_dnd_npc_occurrences_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+
+`v1` is a strict JSON object with required `occurrences`; the array may be
+empty. Occurrence and source-reference objects reject unknown fields. An
+incompatible shape change requires a new schema version.
+
+## Wire shape
+
+Each occurrence has these required fields:
+
+| Field | Contract |
+| --- | --- |
+| `npc_id` | Exact durable ID from the required NPC registry. |
+| `name` | Non-empty canonical display name from the required NPC registry. |
+| `kind` | One of the occurrence categories below. |
+| `source_refs` | One or more transcript evidence ranges. |
+
+Each source reference has exactly `source_id`, `start_unit_id`, and
+`end_unit_id`. It identifies an inclusive range in the current transcript;
+unit IDs are positive and the start may not follow the end. Extraction evidence
+for an occurrence is confined to its accepted chunk.
+
+```json
+{
+  "occurrences": [
+    {
+      "npc_id": "npc:sha256:example",
+      "name": "Mira Thorn",
+      "kind": "dialogue",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 12, "end_unit_id": 13}
+      ]
+    }
+  ]
+}
+```
+
+## Occurrence categories
+
+| Kind | Meaning |
+| --- | --- |
+| `mentioned` | The NPC is referred to but is not established as present or communicating. |
+| `noncombat_presence` | The NPC is present and relevant without meaningful dialogue or combat participation. |
+| `dialogue` | The NPC speaks, responds, or meaningfully participates in a non-combat exchange. |
+| `combat_ally` | The NPC actively participates in combat on the party's side. |
+| `combat_opponent` | The NPC actively participates in combat against the party. |
+| `other` | A clearly evidenced direct occurrence not covered by another category. |
+
+The categories do not represent motives, relationships, state, or events that
+the cited transcript does not establish. An `other` entry is not a substitute
+for uncertain classification.
+
+## Identity, evidence, and order
+
+The required normalized [NPC registry artifact](dnd-npc-registry-artifacts.md)
+supplies names-only contextual grounding to the model. Notarius resolves the
+selected name and writes the exact `{npc_id, name}` pair. An unknown or
+ambiguous selection rejects the complete model result; normalization does not
+repair names by similarity. Registry references are provenance only and never
+replace an occurrence's own evidence.
+The registry may include an identity established by a factual third-party
+mention; that provenance alone does not create a `mentioned` occurrence. Each
+occurrence remains a separately cited fact in the current transcript.
+Normalization validates the exact pair, orders and
+deduplicates exact source references, then orders occurrences by valid source
+chronology, NPC comparison identity, display name, kind, and reference sequence.
+Only entries with the same NPC ID, canonical name, kind, and complete valid evidence
+sequence are collapsed; distinct categories or evidence remain separate.
+
+See the [combat-turn artifact](dnd-combat-turn-artifacts.md) for combat-action
+occurrences. The [enemy-event artifact](dnd-enemy-event-artifacts.md) consumes
+only `combat_opponent` occurrences as grounding; they never establish an enemy
+event or outcome. The [JSON output contract](json-output.md) defines
+publication. Pipeline mechanics are described in
+[D&D module internals](../internal/dnd.md).

docs/integrations/dnd-npc-registry-artifacts.md

@@ -0,0 +1,92 @@
+# D&D NPC Registry Artifact
+
+This contract defines the durable NPC registry produced by `dnd/npc-registry`. It is a
+minimal, source-grounded identity registry for other D&D artifacts, not a
+character sheet or a relationship summary.
+
+## Identity and compatibility
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `dnd/npc-registry` |
+| Schema ID | `notarius.dnd.npc_registry` |
+| Schema name | `notarius_dnd_npc_registry_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
+| Identity policy | `dnd.npc_registry.identity.v1` |
+
+`v1` accepts one strict JSON object with required `npcs`; the array may be
+empty. NPC and source-reference objects reject unknown fields. An incompatible
+artifact shape or identity-policy change uses a new version or policy.
+
+## Wire shape and identity
+
+Each NPC has these required fields:
+
+| Field | Contract |
+| --- | --- |
+| `id` | `npc:sha256:` followed by 64 lowercase hexadecimal characters. |
+| `name` | Non-empty canonical display name. |
+| `source_refs` | One or more transcript evidence ranges for the identity. |
+
+A source reference has exactly `source_id`, `start_unit_id`, and `end_unit_id`.
+The source ID identifies the transcript, unit IDs are positive inclusive unit
+identifiers, and the start may not follow the end.
+
+```json
+{
+  "npcs": [
+    {
+      "id": "npc:sha256:35ba5f679aee69e07ae3bd65c44278f29539d5dc9bb5225db1c0060555b23221",
+      "name": "Mira Thorn",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 4, "end_unit_id": 5}
+      ]
+    }
+  ]
+}
+```
+
+The ID is deterministic: normalize the name to Unicode NFKC, normalize the
+supported apostrophe forms, collapse whitespace, case-fold it, then serialize
+`["dnd.npc_registry.identity.v1", comparison_name]` as compact JSON. SHA-256
+those UTF-8 bytes and prefix the lowercase hexadecimal digest with
+`npc:sha256:`. Each canonical identity and ID appears at most once.
+Normalization collapses records with the same canonical identity, retains their
+earliest position, and merges
+their canonicalized evidence; it does not add aliases, roles, descriptions, or
+relationship fields.
+
+When evidence supports a semantically duplicate group, the canonical display
+name is one of that group's supplied candidates. A complete, stable proper name
+is preferred over an abbreviation. An unadorned proper name is preferred over
+the same name plus a contextual class, role, title, or relationship descriptor
+unless the transcript establishes that descriptor as part of the person's
+name. A longer candidate is not preferred solely because it includes such a
+descriptor.
+
+## Scope and consumers
+
+Only individually identifiable NPC names with transcript evidence belong in
+this artifact. A factual third-party mention can establish an identity even if
+the NPC is not present, speaking, or acting in the cited passage. Names used
+only in hypothetical, speculative, or imagined examples are excluded, as are
+groups, generic roles, invented labels, and descriptive enrichment. Its source
+references prove registry provenance; they do not become evidence for a spell,
+occurrence, combat, or enemy-event occurrence.
+
+Registry evidence establishes an identity, not an [NPC occurrence](dnd-npc-occurrence-artifacts.md).
+That later artifact independently records any current-transcript occurrence
+with its own cited evidence and category.
+
+This registry can ground actor or caster names in the [spell](dnd-spell-artifacts.md)
+and [combat-turn](dnd-combat-turn-artifacts.md) artifacts. It is required to
+resolve the canonical `name` in an [NPC occurrence](dnd-npc-occurrence-artifacts.md).
+Occurrence consumers receive names-only grounding; Notarius resolves the
+selected canonical name and writes the unchanged exact durable ID/name pair.
+Spells, combat turns, and the [enemy-event artifact](dnd-enemy-event-artifacts.md)
+also receive names-only grounding for actor or subject display. None of these
+projections supply later-artifact evidence. [Configuration](../config.md#d-d-reference-slots)
+owns the `npc_registry` binding rules.
+The [JSON output contract](json-output.md) defines publication, and
+[D&D module internals](../internal/dnd.md) owns pipeline mechanics.

docs/integrations/dnd-scene-description-artifacts.md

@@ -1,9 +1,10 @@
-# D&D Scene Description Artifact Contract
+# D&D Scene-Description Artifact
 
-This document defines the durable `dnd/scene-description-list` artifact
-emitted by the D&D scene-description lane.
+This contract defines the durable output of `dnd/scene-descriptions`. Each
+record classifies one accepted transcript chunk and gives it a minimal
+source-grounded title and summary.
 
-## Artifact identity
+## Identity and compatibility
 
 | Property | Value |
 | --- | --- |
@@ -13,38 +14,32 @@ emitted by the D&D scene-description lane.
 | Schema version | `v1` |
 | Media type | `application/json` |
 
-The normalized payload is written by the JSON output module to
-`lanes/<lane-id>.json`. See [JSON output](json-output.md) for the surrounding
-output bundle.
+`v1` is a strict JSON object with required non-empty `scenes`. Scene and
+source-reference objects reject unknown fields. An incompatible shape change
+requires a new schema version.
 
-## JSON shape
+## Wire shape
 
-The payload is a JSON object containing exactly one required field, `scenes`.
-Each scene object contains exactly these required fields:
+Each scene has exactly these required fields:
 
-| Field | Shape and ownership |
+| Field | Contract |
 | --- | --- |
 | `id` | Non-empty accepted chunk ID, assigned by Notarius. |
-| `source_ref` | Exact inclusive accepted chunk range, assigned by Notarius. |
-| `kind` | One of `combat`, `narrative`, `recap`, or `meta`. |
+| `source_ref` | The assigned inclusive source range for that chunk. |
+| `kind` | `combat`, `narrative`, `recap`, or `meta`. |
 | `title` | Non-empty, trimmed, source-grounded title. |
 | `summary` | Non-empty, trimmed, source-grounded summary. |
 
-All object layers reject unknown fields. The `scenes` array must be present and
-non-empty. `source_ref` has exactly `source_id`, `start_unit_id`, and
-`end_unit_id`; its source ID is non-empty and its unit IDs are positive
-integers.
+`source_ref` has exactly `source_id`, `start_unit_id`, and `end_unit_id`.
+Its source ID identifies the input transcript; its positive unit IDs identify
+the chunk's inclusive range, with the start no later than the end.
 
 ```json
 {
   "scenes": [
     {
       "id": "chunk-000001",
-      "source_ref": {
-        "source_id": "session-alpha",
-        "start_unit_id": 1,
-        "end_unit_id": 3
-      },
+      "source_ref": {"source_id": "session-7", "start_unit_id": 1, "end_unit_id": 3},
       "kind": "narrative",
       "title": "Arrival at the watchtower",
       "summary": "The party reaches the ruined watchtower and begins to investigate it."
@@ -53,78 +48,23 @@ integers.
 }
 ```
 
-`id` and `source_ref` are application-owned identity and evidence. The model
-provides only `kind`, `title`, and `summary`; it is not asked for chunk IDs,
-source IDs, unit IDs, ranges, participants, or confidence.
+## Meaning and normalized form
 
-## Scene kinds
+`combat` identifies a chunk where active combat is the central activity.
+`narrative` is current in-world play that is not principally combat, recap, or
+meta discussion. `recap` is primarily a recounting of an earlier session, and
+`meta` is primarily out-of-character discussion. The artifact does not add
+participants, confidence, events, or information absent from the chunk.
 
-| Kind | Meaning |
-| --- | --- |
-| `combat` | Active combat is a substantive central activity. |
-| `narrative` | Current-session in-world play that is not principally combat, recap, or meta discussion. |
-| `recap` | The table is primarily recounting a previous session. |
-| `meta` | Sustained out-of-character discussion is the scene's primary purpose. |
+Normalization trims title and summary, orders scenes by source position and
+then ID, and removes exact duplicate records. A reused ID with different
+durable fields, or the same source range with different kind, title, or
+summary, is invalid. It does not merge adjacent ranges, alter prose, or infer
+missing scenes.
 
-For a mixed accepted chunk, classification prefers `combat`, then `recap`,
-then `meta`, then `narrative`. Brief table talk, rules clarification, or a
-short recollection does not replace the main current-session activity.
-
-## Extraction and evidence
-
-The extractor runs once for each accepted chunk and maps one successful model
-response to one scene record. It copies the current chunk ID and exact chunk
-range, preserves the model kind without repair, and trims only surrounding
-whitespace from title and summary. A model response cannot represent an empty
-result; extraction failure follows the configured retry and rejection policy.
-
-Optional `players`, `party`, and `glossary` campaign references can help
-disambiguate names or setting terms. They never supply scene evidence or add
-events absent from the accepted chunk. The lane requires no NPC registry or
-other generated artifact reference.
-
-## Merge and normalization
-
-Accepted per-chunk lists are appended in chunk order. Normalization then:
-
-1. validates the current-source range, non-empty ID and prose, and closed kind;
-2. trims only title and summary whitespace;
-3. sorts records by source-document start position, then ID;
-4. removes records only when all five durable fields are identical;
-5. rejects a reused ID when any remaining durable field differs; and
-6. rejects the same exact range when `kind`, `title`, or `summary` differs.
-
-Two different IDs with the same range and identical model-owned content remain
-separate records. Normalization does not join adjacent ranges, rewrite prose,
-repair kinds, infer missing scenes, or use chunk annotations.
-
-## Validation and warnings
-
-Extraction validation requires exactly one record with an ID and range exactly
-equal to its current chunk. Later validation checks source membership without a
-current chunk. Shape, source-range, kind, ID, and normalized-invariant failures
-reject the artifact.
-
-Relatedness checks are advisory. They separately warn when a scene title or
-summary has no significant lexical token in its cited transcript range. The
-check ignores short tokens and common function words, uses transcript text only,
-and does not treat campaign references as evidence. Warning diagnostics are
-bounded and do not copy transcript or campaign-reference content.
-
-## Configuration
-
-Use `dnd/scenes` to form accepted scene chunks, then select
-`dnd/scene-descriptions` for extraction and normalization. The maintained
-[complete D&D configuration](../../examples/dnd-complete.config.yml) includes
-this lane alongside the other D&D artifacts. Selectable keys and default
-validator chains are defined in [Configuration](../config.md).
-
-## Downstream combat use
-
-The combat-turn extractor consumes this approved artifact as required
-eligibility control context through an explicit ordered reference binding. It
-uses only an exact chunk ID and source-range match with `kind: combat` to permit
-combat extraction; titles, summaries, and scene references do not become combat
-prompt material or evidence. The complete downstream behavior, including empty
-results and warnings for unavailable coverage, is defined in the
-[D&D combat-turn artifact contract](dnd-combat-turn-artifacts.md).
+The [combat-turn artifact](dnd-combat-turn-artifacts.md) and
+[enemy-event artifact](dnd-enemy-event-artifacts.md) use an exact matching
+`combat` scene only as eligibility control; scene title, summary, and source
+reference never become their evidence. Publication is defined by the
+[JSON output contract](json-output.md); implementation details live in
+[D&D module internals](../internal/dnd.md).

docs/integrations/dnd-spell-artifacts.md

@@ -1,204 +1,73 @@
 # D&D Spell Artifact
 
-This document is the durable serialized artifact contract for the production
-D&D spell extractor. Selectable extractor keys are cataloged in
-[Configuration](../config.md#implemented-production-modules).
+This contract defines the durable output of the `dnd/spells` extractor and
+normalizer. It records source-grounded spell-casting occurrences; it is not a
+spellbook, a rules lookup result, or a record of hypothetical casts.
 
-## Identity
+## Identity and compatibility
 
-- Artifact kind: `dnd/spell-list`
-- Prompt ID: `dnd.spells`
-- Response schema key: `dnd_spells`
-- Response schema ID: `notarius.dnd.spells`
-- Response schema name: `notarius_dnd_spells_v1`
-- Response schema version: `v1`
-- Media type: `application/json`
-
-The durable JSON Schema is owned by the D&D spell artifact codec. The
-extractor's private LLM response schema is a separate transport contract: its
-source-reference objects omit `source_id`, which the extractor assigns while
-mapping the response to the canonical artifact. The LLM DTO and transport
-schema are not part of this durable contract. The private schema owns required
-fields, JSON types, object and array shapes, and unknown-field rejection;
-deterministic validators own the durable artifact's semantic constraints.
-
-The output contains canonical spell casts derived from transcript evidence.
-Source IDs are assigned from the input identity; source-unit ranges identify
-the evidence location.
-
-## Output Shape
-
-The extractor payload is a JSON object with one required top-level array. Its
-structure is:
-
-```text
-{"spell_casts": [<spell-cast object>, ...]}
-```
-
-`spell_casts` must be present. It may be empty when no spell casts are found.
-When multiple chunk results are combined, spell casts remain in chunk order.
-When the payload is written as durable output, its logical path is derived from
-the configured artifact lane ID as defined by the
-[JSON output contract](json-output.md#output-payload-files).
-
-## Spell-Cast Fields
-
-Each spell cast contains exactly these required fields:
-
-- `caster`: in-world character or creature casting the spell;
-- `spell`: spell name;
-- `source_refs`: transcript source references with extractor-assigned source
-  IDs and evidence unit ranges. It must contain at least one entry.
-
-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
-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.
-
-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
-
-Each source reference contains exactly three required fields: `source_id`,
-`start_unit_id`, and `end_unit_id`. The source ID must match the input identity.
-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 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
-supporting disambiguation material, not source evidence, and are not
-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. 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.
-
-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. Generated provenance records producer and canonical
-artifact identity without payload content or a path. When the slot is absent,
-the prompt receives exactly `{"npcs":[]}` with its projection digest, and the
-run has no NPC reference provenance.
-
-## Normalization Behavior
-
-When the `dnd/spells` normalizer is selected, each recognized spell name is
-rewritten to the effective catalog's canonical display name. Lookup uses the
-catalog's case-insensitive, whitespace-normalizing, apostrophe-normalizing, and
-alias rules. Unknown names are preserved exactly for the normalize validators;
-the normalizer does not guess or apply fuzzy matching.
-
-Each cast's `source_refs` is copied, sorted by exact `source_id`,
-`start_unit_id`, and `end_unit_id`, and stripped of exact structural
-duplicates. Adjacent or overlapping ranges are not merged, and the normalizer
-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
-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]`,
-so they remain meaningful even when a later duplicate is removed. The
-normalizer uses these reason codes:
-
-| Reason code | Meaning |
+| Property | Value |
 | --- | --- |
-| `spell_name_canonicalized` | A catalog lookup replaced an input name with its canonical display name. |
-| `spell_name_unresolved` | A name was not found in the effective catalog and was retained unchanged. |
-| `source_references_normalized` | Reference order changed or exact duplicate references were removed. |
-| `duplicate_spell_cast_collapsed` | A later cast matched the retained cast's complete duplicate identity. |
+| Artifact kind | `dnd/spell-list` |
+| Schema ID | `notarius.dnd.spells` |
+| Schema name | `notarius_dnd_spells_v1` |
+| Schema version | `v1` |
+| Media type | `application/json` |
 
-Only warnings from an accepted normalize attempt are promoted to
-`warnings.json`. If an unresolved name reaches the default normalize validator
-chain, the catalog validator rejects the candidate with `unknown_spell`; the
-`spell_name_unresolved` warning remains in the attempt's debug artifact. An
-explicit validator override that accepts the candidate promotes the unresolved
-warning normally.
+`v1` is a single strict JSON object. It requires `spell_casts`; the array may
+be empty. Each spell-cast object and source-reference object rejects unknown
+fields. An incompatible shape change requires a new schema version.
 
-The default extraction and normalization chains both preserve this registered
-order: JSON syntax, spell shape, catalog membership, source references, JSON
-Schema, then source relatedness. Extraction validates the private response
-schema; normalization validates the durable artifact schema.
+## Wire shape
 
-## Manifest Metadata
+Each `spell_casts` entry has these required fields:
 
-The extractor adds prompt and response-schema provenance under the artifact lane
-manifest metadata:
+| Field | Contract |
+| --- | --- |
+| `caster` | Non-empty in-world character or creature name. |
+| `spell` | Non-empty spell name. |
+| `source_refs` | One or more transcript evidence ranges. |
+
+Every source reference has exactly `source_id`, `start_unit_id`, and
+`end_unit_id`. The source ID identifies the input transcript; the unit IDs are
+positive inclusive unit identifiers, and the start may not follow the end in
+that source. References are evidence for the cast, not campaign-reference or
+NPC-registry provenance.
 
 ```json
 {
-  "metadata": {
-    "extractor": {
-      "prompt_id": "dnd.spells",
-      "prompt_version": "v1",
-      "prompt_sha256": "sha256:...",
-      "response_schema_key": "dnd_spells",
-      "response_schema_id": "notarius.dnd.spells",
-      "response_schema_name": "notarius_dnd_spells_v1",
-      "response_schema_version": "v1",
-      "response_schema_sha256": "sha256:...",
-      "catalog_base_id": "dnd-5e-2014-srd-spells",
-      "catalog_digest": "sha256:...",
-      "catalog_overlay_ids": ["campaign.example"],
-      "npc_registry_digest": "sha256:...",
-      "npc_count": 3
-    },
-    "normalizer": {
-      "catalog_base_id": "dnd-5e-2014-srd-spells",
-      "catalog_digest": "sha256:...",
-      "catalog_overlay_ids": ["campaign.example"]
+  "spell_casts": [
+    {
+      "caster": "Mira Thorn",
+      "spell": "Fireball",
+      "source_refs": [
+        {"source_id": "session-7", "start_unit_id": 12, "end_unit_id": 13}
+      ]
     }
-  }
+  ]
 }
 ```
 
-`catalog_digest` identifies the effective semantic catalog, while
-`catalog_overlay_ids` is sorted and empty for a base-only configuration. Raw
-prompt, schema, catalog, alias, and local overlay-file content are not
-included in manifest metadata. The `normalizer` metadata uses the same catalog
-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).
+## Evidence and normalized form
 
-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, 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.
+An entry represents an actual cast or an unambiguous declared attempt. A spell
+mention, rules discussion, plan, or catalog match alone is not an occurrence.
+The configured catalog checks the name; it does not establish evidence.
 
-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 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.
+When normalization is selected, recognized spell names use the effective
+catalog's canonical display name. Source references are put in canonical source
+order and exact duplicate references are removed. A later entry is collapsed
+only when it has the same canonical spell, the same case- and
+whitespace-insensitive caster identity, and the same complete valid reference
+sequence. Remaining entries retain their merged order.
+
+The optional normalized [NPC registry artifact](dnd-npc-registry-artifacts.md) can ground a
+caster name. Its own references remain registry provenance and are never copied
+into `source_refs`.
+
+## Related contracts
+
+The [spell-catalog overlay contract](dnd-spell-catalog-overlays.md) defines
+the configured catalog additions. The [JSON output contract](json-output.md)
+defines where this logical artifact is published; [D&D module internals](../internal/dnd.md)
+describes extraction and validation mechanics.

docs/integrations/dnd-spell-catalog-overlays.md

@@ -1,19 +1,27 @@
-# D&D Spell-Catalog Overlay Contract
+# D&D Spell-Catalog Overlays
 
-This document defines the JSON format accepted by the D&D spell catalog
-resolver. An overlay supplies campaign-specific spell names and aliases for
-recognition. It does not supply spell rules, levels, classes, effects, or
-source evidence.
+This document defines the optional JSON overlay consumed by the D&D spell
+extractor. An overlay contributes campaign spell names and aliases for
+recognition. It does not define spell rules, effects, levels, classes, or
+transcript evidence. Bind the optional `spell_catalog` reference as described
+in [Configuration](../config.md#references-and-ordered-handoffs).
 
-The `dnd/spells` extractor accepts one optional UTF-8 `application/json` overlay
-bundle through its `spell_catalog` reference slot. The framework materializes
-that file relative to the configuration or command-line binding, enforces the
-1 MiB slot limit, and records its origin and raw digest separately from the
-effective catalog digest.
+## Contract Identity
 
-## Shape
+| Property | Value |
+| --- | --- |
+| Consumer | D&D spell extraction and normalization |
+| Reference slot | `spell_catalog` |
+| Media type | `application/json` |
+| Required schema version | `notarius.dnd.spell-catalog-overlay.v1` |
+| Base catalog | Embedded D&D 5e 2014 SRD catalog |
 
-An overlay bundle has this shape:
+At most one overlay document may be bound. The maintained example is
+[dnd-spell-catalog.json](../../examples/dnd-spell-catalog.json).
+
+## Wire Shape
+
+This is a minimal valid overlay:
 
 ```json
 {
@@ -22,49 +30,49 @@ An overlay bundle has this shape:
     {
       "id": "campaign.example",
       "ruleset": "dnd-5e-2014",
-      "source": {
-        "title": "Example campaign spells",
-        "version": "1",
-        "url": "",
-        "license": ""
-      },
-      "spells": [
-        {
-          "name": "Aegis of Emberfall",
-          "aliases": ["Emberfall Aegis"]
-        }
-      ]
+      "source": {"title": "Example campaign spells"},
+      "spells": [{"name": "Aegis of Emberfall"}]
     }
   ]
 }
 ```
 
-The top-level `schema_version` and `catalogs` fields are required. The schema
-version must be exactly `notarius.dnd.spell-catalog-overlay.v1`, and at least
-one catalog is required. Catalogs require a unique, non-empty, trimmed `id`,
-the exact `dnd-5e-2014` `ruleset`, a `source`, and a non-empty `spells` array.
+| Field | Required | Meaning and constraints |
+| --- | --- | --- |
+| `schema_version` | Yes | Exactly `notarius.dnd.spell-catalog-overlay.v1`. |
+| `catalogs` | Yes | Non-empty array of catalog objects with unique IDs. |
+| `catalogs[].id` | Yes | Non-empty trimmed string. |
+| `catalogs[].ruleset` | Yes | Exactly `dnd-5e-2014`. |
+| `catalogs[].source.title` | Yes | Non-empty trimmed string. |
+| `catalogs[].source.version` | No | String when present. |
+| `catalogs[].source.url` | No | String when present. |
+| `catalogs[].source.license` | No | String when present. |
+| `catalogs[].spells` | Yes | Non-empty array of spell objects. |
+| `catalogs[].spells[].name` | Yes | Non-empty trimmed string. |
+| `catalogs[].spells[].aliases` | No | Array of non-empty trimmed strings when present. |
 
-`source.title` is required and must be non-empty and trimmed. `source.version`,
-`source.url`, and `source.license` are optional strings and may be empty.
-Each spell requires a non-empty, trimmed `name`. `aliases` may be omitted or
-may be an array of trimmed, non-empty strings; JSON `null` is not an alias
-array. Overlay objects contain no other supported spell fields.
+Unknown fields are rejected at every object level. The document must contain
+one JSON value; `null` is not accepted for optional strings or aliases.
 
-Decoding is strict: unknown fields, malformed JSON, trailing JSON values, and
-non-string optional source fields are rejected.
+## Composition And Compatibility
 
-## Composition
+Notarius starts with the embedded base catalog, then applies overlay catalogs
+in ascending catalog-ID order. A new canonical spell name adds a recognition
+entry. If an overlay names an existing canonical spell, it augments that spell
+with aliases while retaining the established display spelling.
 
-The resolver always starts with the embedded D&D 5e 2014 SRD catalog. Overlay
-catalogs are sorted by `id` before composition, so the input order does not
-affect the result. A new canonical name adds a recognition entry. A canonical
-name matching an existing canonical name augments that spell and keeps the
-established canonical display spelling. Repeated aliases for the same spell
-are idempotent.
+Repeated aliases for the same spell are accepted. A canonical-name, canonical-
+to-alias, or alias-to-alias collision between different spells is rejected,
+including a collision with the embedded catalog. Matching uses the catalog’s
+case, whitespace, and apostrophe normalization, so authors should avoid names
+or aliases that normalize to another spell.
 
-Canonical-name display conflicts and canonical/alias or alias/alias collisions
-between different spells are errors, including collisions with the embedded
-catalog. Canonical names and aliases use the catalog's case, whitespace, and
-common-apostrophe normalization rules. The effective catalog returns canonical
-names in sorted order and produces a semantic SHA-256 digest that is stable
-under JSON formatting, object-key, catalog, spell, and alias reordering.
+Spell extraction receives the effective catalog as deterministic canonical-name
+and alias pairs. An alias in the transcript selects its associated canonical
+name; the extractor is instructed to return that canonical spelling. The
+projection contains no catalog source metadata or provenance, and aliases
+remain recognition context rather than transcript evidence.
+
+The overlay is a recognition aid only. The durable spell-artifact schema and
+source-evidence rules are defined by the
+[D&D spell artifact contract](dnd-spell-artifacts.md).

docs/integrations/evidence-context.md

@@ -0,0 +1,107 @@
+# Published Evidence Context
+
+This contract defines the optional `source/evidence-context` artifact emitted
+by the production JSON output. It is a selected source-unit excerpt for
+convenient reading alongside normalized lane artifacts; it is not a second
+citation or provenance model. Its configuration is owned by
+[Configuration](../config.md#module-bindings-and-validators), and its
+logical-file discovery is owned by [Published JSON Output](json-output.md).
+
+## Identity And Discovery
+
+When enabled, the JSON bundle contains `evidence-context.json` and an
+`index.json` `evidence_context` descriptor with the same six fields as other
+pipeline-wide artifact descriptors.
+
+| Property | Value |
+| --- | --- |
+| Artifact kind | `source/evidence-context` |
+| Media type | `application/json` |
+| Schema ID | `notarius.source.evidence_context` |
+| Schema name | `notarius_source_evidence_context_v1` |
+| Schema version | `v1` |
+| Logical file | `evidence-context.json` |
+
+Consumers must discover the file from the descriptor, verify all six descriptor
+fields, and decode only a supported schema version. The descriptor is optional:
+its absence means evidence publication was not enabled for that bundle.
+
+## Payload
+
+The v1 payload is a top-level JSON array of generic source units. There is no
+wrapper, source-level metadata, context grouping, lane identifier, or evidence
+reference in the payload. An enabled configuration with no contributing
+accepted evidence publishes `[]`.
+
+```json
+[
+  {
+    "id": 10,
+    "kind": "transcript_segment",
+    "text": "Aria casts Cure Wounds.",
+    "ref": {
+      "source_id": "session-alpha",
+      "start_unit_id": 10,
+      "end_unit_id": 10
+    }
+  },
+  {
+    "id": 20,
+    "kind": "transcript_segment",
+    "text": "The party regroups.",
+    "ref": {
+      "source_id": "session-alpha",
+      "start_unit_id": 20,
+      "end_unit_id": 20
+    }
+  }
+]
+```
+
+Each source unit has required `id`, `kind`, `text`, and self `ref` fields.
+`ref` contains `source_id`, `start_unit_id`, and `end_unit_id`, and both unit
+endpoints identify that unit's `id`. A unit may also contain source-owned
+`metadata`, an open-ended JSON object. Fixed unit and reference fields are
+strict: consumers must reject unknown fixed fields, malformed units, invalid
+self-references, units whose `source_id` differs from other units in the same
+excerpt, and a payload that is not the array described here.
+
+The excerpt preserves each selected unit exactly as represented by the
+validated generic source document. It does not add evidence-context-specific
+annotations or reshape source-owned metadata.
+
+## Selection And Citations
+
+The framework obtains direct source references only through typed evidence
+projections of accepted normalized artifacts in the configured lane allowlist.
+It validates each reference against the current source document, expands its
+range by `window_units` source-unit positions on each side, clamps at document
+boundaries, and takes the union of all expanded ranges. The output contains
+each selected source unit once in source-document position order, regardless
+of numeric unit IDs. Repeated references, overlapping windows, and citations
+from multiple lanes do not duplicate a unit. Rejected, failed, absent,
+inactive, and unselected lanes contribute nothing.
+
+Normalized lane artifacts remain authoritative for citations and for which lane
+cited a range. The excerpt has no lane attribution and must not be used to
+reconstruct it. Its included nearby units provide reading context only; they
+do not widen any citation in a lane artifact.
+
+The excerpt contains at most every generic source unit once. It can therefore
+equal the complete generic source document when coverage is broad or the
+window is large. No byte-, token-, or compression-size guarantee is made, and
+the framework does not truncate the excerpt to meet an arbitrary size limit.
+
+## Consumer Responsibilities And Data Handling
+
+The artifact is additive to the JSON bundle and is not a lane payload,
+normalized-output count, checkpoint, or generated reference. Consumers that
+do not need it must tolerate an absent descriptor. Consumers that do use it
+should validate the descriptor and payload before use, retain the artifact with
+its schema identity when needed for a run record, and read citations from the
+corresponding normalized lane artifacts.
+
+The excerpt contains source-unit text and source-owned metadata and is durable
+output. Treat it as sensitive source content, apply appropriate access controls
+and retention, and do not assume its selected form is materially smaller or
+less sensitive than the original input.

docs/integrations/json-output.md

@@ -1,201 +1,155 @@
-# JSON Output
+# Published JSON Output
 
-This document is the durable JSON output file-format contract produced by the
-production JSON encoder and written by the CLI. Selectable output-encoder keys
-are cataloged in
-[Configuration](../config.md#implemented-production-modules).
+This document defines the logical JSON bundle emitted by the production JSON
+output encoder. The bundle’s physical destination, atomic publication, and
+retention are operational concerns; see [Operations](../operations.md#output-bundles).
+Output configuration, including chunk-map and evidence-context publication, belongs in
+[Configuration](../config.md#module-bindings-and-validators).
 
-The output module produces the logical bundle described here. The CLI's
-physical placement and lifecycle for that bundle are defined in
-[Operations](../operations.md#output-directory).
+## Bundle Layout
 
-## Files
+All paths below are logical, relative, slash-separated bundle paths. The
+encoder always emits the first four JSON files below and adds lane or
+pipeline-wide artifact files when their corresponding artifacts are available:
 
-The encoder writes:
+A subprocess caller first obtains the physical bundle root from the
+[run-result receipt](run-result.md), then resolves `index.json` beneath that
+root for the logical discovery described here.
 
-- `index.json`
-- `manifest.json`
-- `lanes/<lane-id>.json`, one file per normalized serialized artifact
-- `rejected.json`
-- `warnings.json`
-- `chunk-map.json`, only when the JSON output binding enables
-  `include_chunk_map` and the run has an accepted chunk map
+| Path | Purpose |
+| --- | --- |
+| `index.json` | Entry point that names the other published files and lane payloads. |
+| `manifest.json` | Run provenance and result summaries. |
+| `rejected.json` | Rejected pipeline outputs. |
+| `warnings.json` | Accepted-output and run warnings. |
+| `lanes/<safe-lane-id>.json` | One normalized artifact payload for each lane. |
+| `chunk-map.json` | Optional accepted chunk map, when its export is enabled and available. |
+| `evidence-context.json` | Optional selected source-unit excerpt, when evidence publication is enabled. |
 
-Files are pretty-printed JSON with a trailing newline when the payload is JSON.
-Logical file paths are relative, slash-separated, and may not contain `..`.
+JSON files are pretty-printed with a trailing newline. Lane payloads are
+accepted only when their media type is `application/json`.
 
 ## `index.json`
 
-Shape:
+`index.json` is the bundle’s discovery document. An approved run with no
+normalized lanes has this valid minimal index:
 
 ```json
 {
   "manifest_file": "manifest.json",
-  "output_files": [
-    {
-      "lane_id": "spells",
-      "media_type": "application/json",
-      "file": "lanes/spells.json",
-      "module_key": "noop",
-      "schema_id": "notarius.dnd.spells",
-      "schema_name": "notarius_dnd_spells_v1",
-      "schema_version": "v1"
-    }
-  ],
+  "output_files": [],
   "rejected_file": "rejected.json",
   "warnings_file": "warnings.json"
 }
 ```
 
-`output_files` is sorted by lane ID. Output file names are produced by
-sanitizing the lane ID:
+| Field | Required | Meaning |
+| --- | --- | --- |
+| `manifest_file` | Yes | Always `manifest.json`. |
+| `output_files` | Yes | Lane descriptors sorted by `lane_id`. |
+| `rejected_file` | Yes | Always `rejected.json`. |
+| `warnings_file` | Yes | Always `warnings.json`. |
+| `chunk_map` | No | Descriptor for the pipeline-wide `chunk-map.json`; never a lane descriptor. |
+| `evidence_context` | No | Descriptor for the pipeline-wide `evidence-context.json`; never a lane descriptor. |
 
-- characters outside `A-Z`, `a-z`, `0-9`, `.`, `_`, and `-` become `_`;
-- repeated `..` sequences are replaced;
-- leading and trailing `.`, `_`, and `-` are trimmed;
-- empty sanitized names are rejected;
-- two lanes that sanitize to the same output file are rejected.
+Each lane descriptor has required `lane_id` and `file`. It may also include
+`media_type`, `module_key`, `schema_id`, `schema_name`, and `schema_version`
+when supplied by the normalized artifact. Each pipeline-wide artifact
+descriptor (`chunk_map` or `evidence_context`) contains `artifact_kind`,
+`file`, `media_type`, `schema_id`, `schema_name`, and `schema_version`. Their
+payloads are defined by the [Accepted Chunk Map contract](chunk-map.md) and
+[Published Evidence Context](evidence-context.md), respectively.
 
-`manifest_file`, `rejected_file`, and `warnings_file` contain the fixed paths
-shown above. Each `output_files` entry requires `lane_id` and `file`. It also
-contains the normalized payload `media_type`, normalizer `module_key`, and
-response `schema_id`, `schema_name`, and `schema_version` when those values are
-available.
+The lane path is derived from its lane ID. Characters outside letters, digits,
+periods, underscores, and hyphens become underscores; `..` sequences are
+neutralized; leading and trailing periods and underscores are removed. A lane
+that produces an empty name, or two lanes that produce the same path, makes
+output encoding fail.
 
-When present, the top-level optional `chunk_map` descriptor contains exactly
-`artifact_kind`, `file`, `media_type`, `schema_id`, `schema_name`, and
-`schema_version`. It identifies the pipeline-wide `chunk-map.json`; it is not
-a lane output and never appears in `output_files`. The descriptor and file are
-both absent when export is disabled or no chunk plan was accepted. Its payload
-contract is defined by [Accepted Chunk Map](chunk-map.md).
+## Lane Payloads
+
+Each `lanes/<safe-lane-id>.json` file is the codec-owned normalized JSON for
+that lane. Consumers should use the index descriptor’s schema identity rather
+than infer a lane schema from its name. The current D&D payload contracts are
+[spells](dnd-spell-artifacts.md), [NPC registry](dnd-npc-registry-artifacts.md),
+[NPC occurrences](dnd-npc-occurrence-artifacts.md),
+[combat turns](dnd-combat-turn-artifacts.md),
+[item registry](dnd-item-registry-artifacts.md),
+[item occurrences](dnd-item-occurrence-artifacts.md),
+[scene descriptions](dnd-scene-description-artifacts.md),
+[enemy events](dnd-enemy-event-artifacts.md),
+[location registry](dnd-location-registry-artifacts.md), and
+[location occurrences](dnd-location-occurrence-artifacts.md).
 
 ## `manifest.json`
 
-`manifest.json` contains a run manifest. This abridged example shows its core
-structure:
+`manifest.json` is published provenance, not a copy of lane payloads or a
+checkpoint store. Fields without a value may be omitted. Its top-level fields
+group into the following externally observable summaries:
 
-```json
-{
-  "run_id": "run-123",
-  "pipeline_id": "dnd-session",
-  "artifact_lanes": [
-    {
-      "id": "spells",
-      "extractor": "dnd/spells",
-      "merger": "appendorder",
-      "normalizer": "noop"
-    }
-  ],
-  "validation_status": "approved",
-  "started_at": "2026-01-01T00:00:00Z",
-  "completed_at": "2026-01-01T00:00:01Z"
-}
-```
+| Group | Fields |
+| --- | --- |
+| Run identity and result | `run_id`, `pipeline_id`, `pipeline_digest`, `schema_version`, `validation_status`, `started_at`, `completed_at` |
+| Resolved components | `input_module`, `chunker`, `extractors`, `merger`, `normalizer`, `output_encoder`, `artifact_lanes`, `validator_chains`, `module_metadata` |
+| Source and references | `source_digests`, `references` |
+| Published result summaries | `normalized_outputs`, `rejected_outputs`, `validation_summaries` |
+| Execution summaries | `chunk_plan`, `checkpoint_decisions`, `llm_profiles`, `metadata` |
 
-Fields with empty values may be omitted by JSON encoding.
+`references` records provenance such as the target, slot, origin, digest,
+media type, size, and generated-artifact identity. It does not contain
+reference content. `normalized_outputs` and `rejected_outputs` likewise
+summarize results without embedding lane payload bytes. A chunk-plan summary is
+provenance for the plan used by this run; cache records, debug artifacts, and
+other operational state are not published as bundle files.
 
-The manifest fields are:
+Each `validation_summaries` entry is a bounded outcome for one producer result.
+It has required `status`, `producer_attempt_count`, and `terminal_action`;
+the stage and affected step, lane, module, or chunk identity are present when
+applicable. `status` is `complete`, `rejected`, or `incomplete`.
+`rejecting_validators`, `reason_codes`, and `incomplete_validators` preserve
+configured validator order and omit later duplicates. Entries contain no raw
+candidate response, correction guidance, validator diagnostic message, or
+artifact payload. The same shape may appear as `validation` on an affected
+rejection entry.
 
-- `run_id`, `pipeline_id`, and `pipeline_digest`: run and resolved-pipeline
-  identity;
-- `input_module`, `chunker`, `extractors`, `merger`, `normalizer`, and
-  `output_encoder`: resolved module keys;
-- `chunk_plan`: payload-free provenance for the effective chunk plan. `mode`
-  is the effective cache mode; `action` is `reused`, `generated`,
-  `refreshed`, or `bypassed` when a plan was materialized. `requested_module`
-  is the current pipeline chunker, while `producer_input_module`,
-  `producer_module`, `producer_llm_profile`, `producer_references`,
-  `producer_metadata`, `source_digest`, `plan_digest`, `plan_schema_version`,
-  and `created_at` describe the stored or generated producer when available.
-  A cached plan can therefore identify a producer different from the requested
-  module. This object never embeds ranges, units, annotations, prompts,
-  responses, or reference content;
-- `module_metadata` and `artifact_lanes`: module and per-lane provenance,
-  including prompt and response-schema provenance when provided;
-- `validator_chains`: resolved validation points and validators;
-- `source_digests` and `references`: source and reference provenance;
-- `normalized_outputs` and `rejected_outputs`: payload-free result summaries;
-- `llm_profiles`: selected profile IDs and provider or model names when
-  available;
-- `metadata`: the effective prompt `session_id`;
-- `validation_status`: `approved` or `rejected`;
-- `started_at` and `completed_at`: UTC run timestamps.
+When present, `metadata.session_id` is the effective non-secret routing
+correlation identifier used for the run. It can be visible to providers and is
+not a substitute for a cache or checkpoint identity. Its generation and
+override behavior are defined by the [CLI reference](../cli.md#run).
 
-`source_digests` contains source document digests only. Bound references are
-recorded separately under `references`, which contains provenance only: target
-stage, lane ID when present, slot name, origin type and URI, digest, media
-type, byte size, and binding source. Reference content is not written to
-durable output.
+Each `llm_profiles` entry identifies effective, non-secret LLM execution
+provenance:
 
-Reference `stage` is `chunk`, `extract`, `merge`, or `normalize`. `lane_id` is
-omitted for chunk references and present for extract, merge, and normalize
-references.
+| Field | Required | Meaning |
+| --- | --- | --- |
+| `id` | Yes | Selected PromptKit profile identifier. |
+| `provider` | No | Notarius adapter provider identifier. |
+| `model` | No | Effective provider model identifier. |
+| `backend_id` | No | Effective PromptKit backend registration identifier. Endpoint-only profiles omit it. |
+| `reasoning_effort` | No | Effective opaque provider reasoning setting. An empty or explicitly cleared setting is omitted. |
 
-`validation_status` is `approved` when no outputs were rejected and `rejected`
-when one or more outputs were rejected.
+These values describe observed execution; they are not a backend-registration
+interface. Entries that differ by backend or effective reasoning remain
+distinct even when their profile, provider, and model are otherwise equal.
 
-Producer warnings and the current run's chunk-validation warnings remain in
-`warnings.json`. The manifest records only provenance and decision summaries;
-empty producer-only values are omitted for compatibility with existing readers.
+## Rejections And Warnings
 
-`validator_chains` records the resolved validator chain for each validation
-point. Entries include stage, lane ID when applicable, module key, and validators
-with key and execution class. Empty chains are recorded with an empty
-`validators` array, including chains resolved from explicit empty config
-overrides.
+`rejected.json` is always an object with a `rejected` array. Each entry has
+required `stage` and `message`; `step_id`, `lane_id`, `module_key`, `chunk_id`,
+`chunk_index`, `validator_name`, `reason_code`, `attempt_count`, and
+`diagnostic_artifact_path` are present only when applicable. An entry may also
+contain the bounded `validation` summary described above; the existing singular
+validator and reason fields remain the first configured rejection for
+compatibility.
 
-`normalized_outputs` summarizes each normalized lane output without embedding
-payload bytes. Entries include lane ID, normalizer module key, source ID, media
-type, and response schema provenance where available.
+`warnings.json` is always an object with a `warnings` array. Each warning has
+`reason_code` and `message`; `scope` is optional. Both arrays are empty when
+there is nothing to report.
 
-`rejected_outputs` summarizes rejected module outputs without embedding raw
-payload bytes. Entries include stage, lane, module, chunk, validator or reason,
-message, attempt count, and optional diagnostic artifact path.
+## Compatibility
 
-## Output Payload Files
-
-Each normalized serialized artifact is written to
-`lanes/<sanitized-lane-id>.json`. The JSON output encoder is domain-neutral and
-accepts only artifacts whose codec media type is `application/json`. The file
-contains the codec-owned JSON bytes pretty-printed.
-
-The schema of each lane payload is owned by that artifact contract. For the
-current D&D lanes, see [D&D Spell Artifact](dnd-spell-artifacts.md),
-[D&D NPC Artifact](dnd-npc-artifacts.md), and
-[D&D Combat-Turn Artifact](dnd-combat-turn-artifacts.md), and
-[D&D Scene Description Artifact](dnd-scene-description-artifacts.md).
-
-## `rejected.json`
-
-Shape:
-
-```json
-{
-  "rejected": []
-}
-```
-
-When output validation rejects an output, each entry contains `stage` and
-`message`. It includes `lane_id`, `module_key`, `chunk_id`, `chunk_index`,
-`validator_name`, `reason_code`, `attempt_count`, and
-`diagnostic_artifact_path` when applicable.
-
-## `warnings.json`
-
-Shape:
-
-```json
-{
-  "warnings": [
-    {
-      "scope": "extract",
-      "reason_code": "example",
-      "message": "human-readable warning"
-    }
-  ]
-}
-```
-
-`warnings` is an empty array when no warnings are reported.
-Each warning requires `reason_code` and `message`; `scope` is omitted when it is
-empty.
+The index is the authoritative map from a logical lane to its published
+payload. Consumers must tolerate omitted optional manifest and descriptor
+fields, and should rely on the linked artifact contract for each lane’s JSON
+shape. This contract describes the published logical bundle only; it does not
+promise a filesystem layout or expose internal state formats.

docs/integrations/pkg-promptkit.md

@@ -0,0 +1,148 @@
+# PromptKit Integration
+
+Notarius pins
+[`gitea.maximumdirect.net/eric/promptkit` v0.9.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0)
+as its in-process prompt engine. The upstream
+[Go package consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/consumers/pkg-promptkit.md)
+owns the public engine API, and the upstream
+[format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/formats.md)
+owns prompt, profile, and schema file contracts.
+
+## Supported Boundary
+
+Notarius relies on the root `promptkit` package to:
+
+- construct an `Engine` with filesystem-backed prompt, schema, and optional
+  operator and application-fallback profile sources;
+- prepare one frozen execution from a `RunRequest` with named inline artifacts,
+  variables, a direct session ID, prompt identity, profile selection, and
+  optional appended rendered messages, then
+  record credential-redacted details and run that exact execution;
+- return rendered debug material, validated structured output, selected
+  profile, backend, effective model metadata, and token usage;
+- register the optional conventional `local` backend through `BackendLocal`,
+  `LocalBackend`, and `WithBackend`;
+- distinguish structured-output validation failure from execution failure; and
+- identify a missing explicit profile through `ErrProfileNotFound` and backend
+  admission exhaustion through `ErrCapacityExceeded`.
+
+The pinned
+[`BackendLocal`, `LocalBackend`, and `WithBackend` API](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/backends.go)
+owns the registration and backend-capacity contract.
+
+For one completion, the adapter calls `PrepareExecution`, takes a
+caller-owned `Details` snapshot, and calls `RunPrepared` for that same opaque
+prepared execution. It defers `Discard` for every unexecuted handle. Explicit
+profile preflight uses `Engine.InspectProfile`; it does not prepare a synthetic
+prompt. PromptKit's prepared handle, inspection result, and capacity-error
+types stay inside the Notarius LLM adapter.
+
+When a PromptKit profile and runtime override leave `temperature`, `max_tokens`,
+or `top_p` unset, Notarius leaves that control unset as well. Compatible
+providers therefore apply their own defaults; an operator that requires a
+specific sampling value must select it explicitly in the profile or runtime
+override.
+
+Notarius does not use PromptKit's optional `ArtifactReader`. It materializes
+source and reference content itself and supplies owned inline artifacts at the
+adapter boundary. It also retains responsibility for pipeline retries,
+scheduling, debug persistence, redaction, profile provenance, and conversion
+from private model responses into durable domain artifacts.
+
+Notarius sends one stable effective session through PromptKit's direct session
+field, which is authoritative for provider session behavior. It also retains
+the same value as the `session_id` prompt variable for maintained prompt
+compatibility. The generated identifier is 76 ASCII characters, within
+PromptKit v0.9.0's 256-code-point session limit. Session IDs are non-secret
+correlation identifiers and may be exposed to providers and provider
+observability. The CLI contract owns generation and override behavior.
+
+Notarius records PromptKit's selected backend ID and effective reasoning
+setting as optional run-manifest provenance. Endpoint-only profiles have no
+backend ID. Debug prompt material also retains the selected backend ID and
+PromptKit's stable lower-case `effective_model_params` JSON, which may include
+`backend_id`. Notarius production configuration exposes one optional
+conventional `local` registration. It does not expose a general user-defined
+PromptKit backend registry. Endpoint-only profiles remain supported unchanged.
+
+Notarius retains its application-wide scheduled client around the PromptKit
+adapter. PromptKit may apply a narrower limit for the selected backend;
+endpoint-only profiles have no such backend limit. The adapter translates
+PromptKit capacity rejection into the provider-neutral Notarius
+`ErrLLMCapacityExceeded` contract. It may include the normalized selected
+backend ID in safe diagnostic context, without exposing PromptKit's capacity
+error type, and leaves retries to the calling pipeline stage.
+
+## Profile Sources And Compatibility
+
+Notarius gives PromptKit the configured operator profile source, registered
+application fallback profile assets, and optional backend registration through
+the same construction path for inspection and execution. PromptKit owns the
+resulting source precedence and strict profile parsing: a matching operator
+profile is a complete replacement for a fallback or built-in profile, while an
+invalid matching document fails instead of falling through. The operator
+configuration and deployment workflow are defined in
+[Configuration](../config.md#promptkit-profiles) and
+[Operations](../operations.md#promptkit-profile-deployment).
+
+PromptKit owns `base_profile` resolution under its
+[pinned format rules](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.0/docs/formats.md).
+Notarius records the selected leaf identity and resolved target without parsing
+or merging inheritance. An unset filesystem `api_key_env` is optional and may
+reach the provider without authorization, which can result in a 401 or 403.
+
+PromptKit v0.9.0 accepts only the `developer`, `system`, `user`, and
+`assistant` text-chat roles after normalizing case and surrounding whitespace.
+Maintained Notarius prompt definitions use only `system` and `user`.
+
+For application-owned semantic correction, Notarius uses PromptKit v0.9.0's
+`RunRequest.AppendedMessages` after the ordinary rendered prompt. It supplies
+exactly two messages in order: the latest validated producer response with
+role `assistant`, then deterministic validation guidance with role `user`.
+It never exposes a general caller-selected role API, accumulates earlier
+correction turns, or changes the ordinary prompt prefix. Ordinary requests
+leave appended messages unset.
+
+PromptKit preserves supplied content but does not own Notarius's correction
+bounds. Notarius rejects invalid UTF-8, blank, or oversized assistant material
+(at most 1 MiB), guidance (at most 64 KiB), and combined content (at most
+1,114,112 bytes) before preparing the request. The transport-neutral
+application contract owns defensive copying and these limits. Default request
+and terminal summaries retain only safe counts, digests, identities, and usage;
+complete appended messages remain limited to the explicitly requested detailed
+debug trace.
+
+PromptKit now obtains its maintained OpenRouter and Rakestrawhome backend and
+profile catalogs from independently versioned transitive modules. Notarius
+does not import or register either catalog; PromptKit retains catalog source,
+identity, precedence, credential, and capacity ownership.
+
+Notarius supports this boundary against PromptKit v0.9.0. Its fallback source,
+prepared-execution, inspection, and typed capacity APIs are used as public
+upstream contracts; other PromptKit APIs or file-format behavior are not
+implicitly supported. A dependency upgrade requires reviewing the adapter,
+profile-source construction, and this compatibility statement against the
+pinned upstream documentation.
+
+## Notarius Ownership
+
+[LLM Runtime Internals](../internal/llm.md) describes how Notarius mounts
+module assets, maps its transport-neutral completion contract, prepares and
+executes requests, validates output, records provenance, captures debug
+material, redacts errors, and preserves timeout ownership.
+
+PromptKit provider error details do not cross the ordinary completion boundary.
+Notarius exposes a provider-neutral generation category and optional status;
+redacted provider details are retained only in requested debug material.
+[D&D Module Internals](../internal/dnd.md) owns the embedded
+`dnd-extraction` fallback profile and the maintained D&D prompt defaults.
+[Configuration](../config.md#promptkit-profiles) defines how a Notarius
+configuration selects one PromptKit profile source and optionally registers
+the conventional local backend.
+
+PromptKit API or format changes outside this boundary are not implicitly
+supported. Updating the pinned version requires reviewing the adapter and
+profile/configuration contracts against the upstream documentation. Maintained
+production prompts use PromptKit's bounded structural-repair contract; their
+current declaration is one additional repair attempt. Notarius retains the
+transport-neutral boundary and does not expose PromptKit types to modules.

docs/integrations/run-result.md

@@ -0,0 +1,85 @@
+# Run Result Receipt
+
+`notarius run --json` writes this receipt to standard output when a run
+completes successfully. It lets a subprocess caller discover the physical root
+of the published output bundle without parsing interactive command output.
+Command syntax, streams, and exit statuses are defined in the
+[CLI reference](../cli.md); logical files within the bundle are defined in the
+[Published JSON Output contract](json-output.md).
+
+## Schema
+
+The current schema version is `notarius.run-result.v1`.
+
+| Field | Required | Meaning |
+| --- | --- | --- |
+| `schema_version` | Yes | Exactly `notarius.run-result.v1`. |
+| `run_id` | Yes | The finalized Notarius run identifier. |
+| `pipeline_id` | Yes | The effective pipeline identifier. |
+| `output_directory` | Yes | Absolute path to the published, run-specific output bundle. |
+| `index_file` | For the production JSON output | Logical path `index.json`; omitted for other output modules. |
+| `normalized_output_count` | Yes | Number of final normalized outputs. |
+| `rejected_output_count` | Yes | Number of recorded rejected outputs. |
+| `warning_count` | Yes | Number of final run warnings. |
+| `validation_status` | Yes | The final run manifest validation status. |
+| `validation_summaries` | No | Bounded per-producer validation outcomes; present when producer work ran. |
+| `debug_directory` | No | Absolute path to the run-specific debug bundle when requested debug capture completed. |
+
+For the production `json` output module, `index_file` is present only when the
+completed run returned exactly one logical output file named `index.json`.
+For another output module, its absence does not indicate a failed run.
+`validation_status` is `approved`, `rejected`, or `incomplete`; `incomplete`
+means one or more otherwise accepted results advanced under validator-failure
+`warn_continue`.
+
+```json
+{
+  "schema_version": "notarius.run-result.v1",
+  "run_id": "run-1770000000000000000-0123456789abcdef0123456789abcdef",
+  "pipeline_id": "dnd-session",
+  "output_directory": "/work/results/run-1770000000000000000-0123456789abcdef0123456789abcdef",
+  "index_file": "index.json",
+  "normalized_output_count": 6,
+  "rejected_output_count": 2,
+  "warning_count": 1,
+  "validation_status": "incomplete",
+  "validation_summaries": [
+    {
+      "stage": "extract",
+      "lane_id": "spells",
+      "status": "incomplete",
+      "incomplete_validators": ["dnd/spells/source_refs"],
+      "producer_attempt_count": 1,
+      "terminal_action": "warn_continue"
+    }
+  ]
+}
+```
+
+## Paths And Bundle Discovery
+
+`output_directory` and `debug_directory`, when present, are lexical absolute
+paths. They identify the paths used by Notarius and do not resolve symlinks.
+`output_directory` is the run-specific bundle, not the configured output root.
+
+The receipt is a summary and discovery document. Its optional validation
+summaries contain only stable status, identity, validator names, reason codes,
+attempt counts, and terminal actions. It does not contain lane descriptors,
+payloads, manifest payloads, rejection messages, warnings, raw model responses,
+correction guidance, or file contents.
+For the production JSON output, resolve `index_file` beneath
+`output_directory`, reject path escapes, and use the
+[Published JSON Output contract](json-output.md) to discover logical files and
+lane payloads.
+
+## Delivery And Compatibility
+
+Notarius writes the receipt only after the output bundle has been published and
+any requested debug terminal reporting has completed. Standard output is not
+transactional: a result-write failure returns a nonzero status and can leave
+partial bytes. Consumers must ignore standard output unless the process exits
+with status 0.
+
+Future versions may add optional fields to this schema. Consumers must tolerate
+unknown fields. An incompatible field or semantic change requires a new
+`schema_version` value.

docs/integrations/seriatim.md

@@ -1,69 +1,73 @@
-# Seriatim Transcript JSON
+# Seriatim Transcript Input
 
-This document is the external input contract consumed by the production
-Seriatim input adapter. Selectable input-adapter keys are cataloged in
-[Configuration](../config.md#implemented-production-modules).
+This document defines the JSON transcript accepted by the production Seriatim
+input adapter. It is a source input, not a durable lane artifact. Configure the
+input adapter through [Configuration](../config.md#production-module-keys).
 
-## Adapter
+## Contract Identity
 
-- Source format: `application/vnd.seriatim+json`
+| Property | Value |
+| --- | --- |
+| Consumer | Seriatim input adapter |
+| Media type | `application/vnd.seriatim+json` |
+| Source document kind | `transcript` |
+| Source-unit kind | `transcript_segment` |
 
 ## Accepted Shape
 
-The input must be one JSON object with top-level `metadata` and `segments`
-fields. This covers the maintained minimal fixture and Seriatim intermediate
-output that provides the same required segment fields.
+The input is one JSON object containing `metadata` and a non-empty `segments`
+array. This minimal document is valid:
 
-The maintained example is
-[examples/seriatim-minimal-transcript.json](../../examples/seriatim-minimal-transcript.json).
+```json
+{
+  "metadata": {"id": "session-alpha"},
+  "segments": [
+    {
+      "id": 1,
+      "start": 0,
+      "end": 4,
+      "speaker": "Aria",
+      "text": "Aria casts Cure Wounds."
+    }
+  ]
+}
+```
 
-Required top-level fields:
+The maintained two-segment input is
+[seriatim-minimal-transcript.json](../../examples/seriatim-minimal-transcript.json).
 
-- `metadata`: an object. Its entries are accepted as source metadata.
-- `segments`: a non-empty array of segment objects.
+| Field | Required | Meaning and constraints |
+| --- | --- | --- |
+| `metadata` | Yes | JSON object. Its entries become source metadata; no particular metadata key is otherwise required. |
+| `segments` | Yes | Non-empty array of segment objects, kept in input order. |
+| `segments[].id` | Yes | Positive canonical decimal integer, supplied as a JSON number or string. IDs must be unique. |
+| `segments[].start` | Yes | Finite, non-negative numeric value, supplied as a JSON number or string. |
+| `segments[].end` | Yes | Finite, non-negative numeric value that is not earlier than `start`. |
+| `segments[].speaker` | Yes | String that is non-empty after trimming. |
+| `segments[].text` | Yes | String that is non-empty after trimming. Its original text is retained. |
 
-Required segment fields:
+Additional top-level and segment fields are ignored. A missing required field,
+`null` in place of an object or array, malformed JSON, or more than one
+top-level JSON value is rejected.
 
-- `id`: a positive integer JSON number or canonical decimal string without
-  leading zeros or surrounding whitespace;
-- `start`: a finite, non-negative JSON number or numeric string;
-- `end`: a finite, non-negative JSON number or numeric string that is not less
-  than `start`;
-- `speaker`: a non-empty string;
-- `text`: a non-empty string.
+## Source Identity And References
 
-Other top-level and segment fields, such as `categories`, are ignored.
+The adapter chooses the source ID in this order:
 
-Multiple top-level JSON values are rejected.
+1. a non-empty source ID supplied by the calling request;
+2. non-empty string `metadata.id`;
+3. non-empty string `metadata.source_id`;
+4. `seriatim:` followed by the first 16 hexadecimal characters of the raw
+   input’s SHA-256 digest.
 
-## Validation
+Each accepted segment becomes one source unit whose unit ID is `segments[].id`.
+Its self-reference uses the derived source ID and the same segment ID for both
+range endpoints. Artifact contracts use those segment IDs when they cite
+transcript evidence.
 
-The adapter rejects empty input, malformed JSON, multiple top-level JSON values,
-non-object segment values, duplicate segment IDs, and any violation of the
-shape or field constraints above.
+## Compatibility
 
-Segment text is preserved as provided, but it must not be empty after trimming.
-
-## Derived Identity
-
-Notarius identifies the parsed source in this order:
-
-1. `metadata.id`, when it is a non-empty string after trimming;
-2. `metadata.source_id`, when it is a non-empty string after trimming;
-3. `seriatim:<first-16-hex-chars-of-raw-sha256>`.
-
-The exact raw input SHA-256 remains the basis of the fallback source ID. The
-source digest recorded in output provenance is instead the SHA-256 of the
-canonical generic source document, excluding the digest field itself. It covers
-the derived source identity, document kind and format, ordered units and their
-self-references, and accepted metadata. Segment IDs become the unit IDs used by
-artifact source references; each produced unit carries a self-reference whose
-source ID is the derived document ID and whose start and end IDs both equal the
-segment ID.
-
-## Compatibility Limit
-
-This contract covers only Seriatim transcript JSON with the top-level
-`metadata` object and `segments` array described here. Broader Seriatim output
-schemas are compatible only when they provide these required fields with the
-accepted types.
+This adapter accepts only the shape described here. A broader Seriatim export
+is usable only when it supplies this object, metadata, and segment shape with
+the stated types and constraints. Unknown additional fields do not add
+Notarius behavior.

docs/internal/cli.md

@@ -0,0 +1,176 @@
+# CLI Internals
+
+This document describes **internal/cli**, Notarius's production composition
+root. The [CLI reference](../cli.md) owns command syntax and exit statuses;
+[Configuration](../config.md) owns configuration values; and
+[Operations](../operations.md) owns filesystem layout, recovery, and operator
+procedures.
+
+## Inputs, Outputs, And Boundaries
+
+The CLI accepts process arguments, standard streams, and injectable options
+used by tests and embedding code. It writes command results to the supplied
+streams and returns a process exit status. For a run, it also creates the
+production catalog and runtime collaborators, hands a prepared pipeline and
+source bytes to the framework, and places the logical files returned by the
+runner.
+
+It is the only boundary allowed to compose concrete registries, LLM clients,
+cache/checkpoint collaborators, debug recorders, and physical output paths.
+Pipeline modules receive interfaces and request data rather than CLI streams or
+filesystem roots. The [Architecture](../policy/architecture.md) defines this
+composition-root boundary; [Pipeline Internals](pipeline.md) owns resolution,
+preparation, and runner mechanics after their inputs are supplied.
+
+## Dispatch And Configuration Handoff
+
+The root dispatcher handles help, version reporting, configuration validation,
+pipeline listing, and a pipeline run. Version reporting resolves build
+information through `internal/buildinfo` before production composition, so the
+diagnostic remains available without configuration or runtime collaborators.
+The public syntax, streams, exit classes, and version semantics are defined by
+the [CLI reference](../cli.md). Other root commands normalize injectable
+options before dispatch so that a missing production dependency fails as a
+command error rather than reaching execution.
+
+Commands that need configuration use one shared loader. The CLI discovers the
+file, parses it through **internal/core/config**, starts from defaults, applies
+the file and supported environment overrides, and then validates it for the
+command. The configured discovery and precedence contract is in
+[Configuration](../config.md), while the loading and resolution mechanics are
+in [Configuration Internals](configuration.md).
+
+Configuration validation without a selected pipeline checks structural
+configuration only. Validation with a selected pipeline also builds the
+effective catalog, resolves the pipeline, and verifies every explicit effective
+PromptKit profile. Selected LLM-backed input, chunk, lane, output, and validator
+profiles are inspected
+against the configured PromptKit source and backend registrations without
+loading a prompt or performing generation, so an unknown or invalid profile
+fails before pipeline preparation. Credential availability remains an
+execution-time concern. Pipeline listing validates configuration before
+returning normalized, sorted identifiers.
+
+## Production Composition
+
+The production composition helper allocates every framework registry and the
+prompt-asset registry, then registers the generic, Seriatim, and D&D module
+families in that order. The resulting registries provide both the module
+catalog used for resolution and the concrete constructors used for preparation.
+Tests may provide a catalog or registries instead; production code must not
+silently merge an injected partial catalog with production registrations.
+
+The production LLM factory builds one PromptKit-backed client from the resolved
+**promptkit.profile_dir** or **promptkit.profile_file** source, attaches the
+profile-provenance recorder, creates one scheduler from the effective global
+LLM limit, and wraps the client before it reaches modules. Registration and LLM
+construction errors are returned before a pipeline is prepared. Configuration
+field definitions remain in [Configuration](../config.md#promptkit-profiles);
+the D&D registrar's fallback profile assets and the adapter mechanics remain in
+[LLM Runtime](llm.md).
+
+The factory also accepts `LLMRuntimeOverrides`, whose reasoning pointer
+preserves inherit, replace, and clear states across the composition boundary.
+Run orchestration constructs this value from the mutually exclusive
+`--reasoning-effort` and `--clear-reasoning-effort` controls. Absence preserves
+a nil pointer, replacement is trimmed, and clear uses a non-nil empty string.
+The same override reaches the one shared production client, checkpoint
+identity, and debug invocation metadata. Persistent reasoning configuration
+remains owned by PromptKit profiles; Notarius configuration has no reasoning
+field.
+
+## Run Orchestration
+
+After parsing and validating a run invocation, the CLI performs this ordered
+handoff:
+
+1. load and validate configuration, then apply command-level operational
+   overrides;
+2. create and validate a safe run identity, then allocate a debug bundle only
+   when requested;
+3. build the effective catalog, resolve requested reference changes, resolve
+   the effective pipeline, and inspect its explicit effective PromptKit
+   profiles;
+4. materialize external or generated references and record redacted invocation
+   and resolution provenance when debug capture is enabled;
+5. construct registries, the scheduled LLM client, and prepared modules;
+6. read the source input once, resolve its effective session from the explicit
+   override or resolved input module and raw bytes, then construct requested
+   checkpoint collaborators and invoke the framework runner with that same
+   value; and
+7. write the runner's logical output files only after a successful run, then
+   complete the command report and user-facing result.
+
+Preparation happens before source parsing, so module construction and
+dependency failures cannot begin stage execution. The CLI also preserves the
+framework's result and warning information when it writes summaries and the
+final command result. Detailed state lifecycle, resume handling, and physical
+path confinement are maintained in [Run State Internals](state.md) and
+[Operations](../operations.md).
+
+The CLI owns the versioned generated-session policy and resolves the sole
+effective value before checkpoint construction. It records that value in the
+final debug invocation summary when capture is enabled and passes it unchanged
+to checkpoint identity and `pipeline.RunInput`. The public flag and stability
+contract are defined by the [CLI reference](../cli.md#run); framework and LLM
+packages only transport the supplied value.
+
+For `run --json`, the CLI constructs and encodes its private run-result receipt
+after a successful runner result is available, before it publishes logical
+output files. It writes the prepared receipt to standard output only after
+output publication and requested debug terminalization succeed. A receipt-write
+failure exits with runtime status 1 and may leave partial standard-output bytes,
+but the already-published output bundle remains complete and requested debug
+reporting remains successfully terminalized. The CLI reports a bounded
+command-owned error and does not repeat terminal reporting. The receipt remains
+a CLI reporting concern rather than a framework or output-module responsibility;
+its public contract is the
+[run-result receipt](../integrations/run-result.md).
+
+## Failure Mapping And Terminal Reporting
+
+Argument, flag, and invocation-combination failures are reported to standard
+error before runtime composition and use the syntax error class. Once an
+invocation is syntactically valid, configuration loading and validation,
+resolution, registration, profile checks, reference materialization, module
+construction, input reads, runner failures, output publication, and requested
+debug handling use the runtime failure class. The public status numbers and
+stream contract are defined in the [CLI reference](../cli.md#output-streams-and-exit-statuses).
+
+When debug capture has been allocated, one command-state value records the
+known run result. Guarded terminalization writes a success report once, or
+attempts a failure report and error record once. A persistence failure is
+reported in addition to the original failure and never replaces it. If a debug
+path exists, failure output includes that path so the retained diagnostic data
+is discoverable.
+
+## Invariants To Preserve
+
+- Only the CLI composes production implementations and physical runtime roots.
+- Configuration and resolved composition failures occur before module
+  preparation or source parsing.
+- A runner's logical files are published only after a successful run.
+- Production registries and a caller-supplied catalog or registries are
+  alternative composition sources, not an implicit mixture.
+- A requested debug bundle has one terminal report attempt; its persistence
+  errors supplement rather than obscure the primary command error.
+- User-facing flags, paths, exit codes, and configuration fields are defined
+  by their public documentation, not duplicated here.
+
+## Focused Tests
+
+- **internal/cli/command_contract_test.go** covers dispatch, help, syntax and
+  runtime error classes, discovery, validation, and listing.
+- **internal/cli/run_contract_test.go** covers the run handoff, publication,
+  debug reporting, and command-owned state collaborators.
+- **internal/cli/production_contract_test.go** covers registrar composition,
+  production catalog contents, assets, and representative configuration
+  validation.
+- **internal/cli/reference_contract_test.go** covers CLI reference overrides,
+  origin separation, and materialization boundaries.
+- **internal/cli/state_hardening_test.go** covers safe run identity, state
+  roots, and failure ordering.
+
+Run **go test ./internal/cli** after changing command composition or command
+behavior. Pair it with **go test ./internal/core/config** when the configuration
+handoff changes.

docs/internal/configuration.md

@@ -0,0 +1,153 @@
+# Configuration Internals
+
+This document describes the maintainer-facing configuration boundary in
+**internal/core/config**. The [Configuration](../config.md) reference owns the
+file format, fields, defaults, precedence contract, and selectable keys. The
+[CLI reference](../cli.md) owns command syntax; this document does not redefine
+either interface.
+
+## Boundary
+
+The configuration package turns a selected YAML file and supported environment
+values into a validated, independently owned configuration. It then resolves a
+requested pipeline against a module catalog before the framework prepares or
+runs anything.
+
+| Boundary | Inputs | Outputs | Does not own |
+| --- | --- | --- | --- |
+| Loading | Selected file path and environment lookup | Parsed file model and a populated **Config** | Choosing the file path or reporting a command result. |
+| Validation | **Config** | Structural configuration errors with pipeline, lane, or binding context | Module availability, capabilities, or construction. |
+| Resolution | Valid **Config**, selected pipeline and lanes, runtime reference changes, LLM override, and module catalog | **EffectiveConfig** with a **ResolvedPipeline** | Materializing reference bytes, preparing modules, execution, or filesystem state. |
+| Summary | **Config** or **EffectiveConfig** | Detached redacted payload suitable for debug summaries | Redacting arbitrary process state or provider traffic. |
+
+The CLI discovers a configuration file, invokes this package, and supplies the
+result to the framework. Configuration never reads an input file, constructs a
+module, or creates output, cache, or debug paths. Those responsibilities remain
+at their respective [CLI](cli.md), [pipeline](pipeline.md), and
+[run-state](state.md) boundaries.
+
+## Loading And Validation
+
+The CLI loads configuration in this order:
+
+1. parse the selected YAML file strictly into the file model;
+2. start from **Default**;
+3. apply the file model; and
+4. apply the supported environment overrides.
+
+This establishes the public precedence order without giving environment input a
+second file schema. Loading and application reject malformed YAML, unsupported
+file versions, unknown fields, invalid values, and identifiers that are empty
+or collide after whitespace normalization. The file application also makes the
+effective extraction-worker default follow the effective LLM limit. A present
+PromptKit local-backend object requires and trims its endpoint, defaults its
+omitted concurrency limit to zero, and is copied so the parsed file model
+cannot alias the populated **Config**. A pipeline `llm_profile` is
+presence-aware: omission remains empty, while a present blank value is
+rejected and a non-empty file value is trimmed before it reaches **Config**.
+
+**Config.Validate** checks configuration-only invariants before resolution. It
+rejects incompatible profile sources, invalid state-surface values, unsupported
+concurrency settings, malformed bindings and references, invalid retries, and
+invalid pipeline, step, or lane structure. PromptKit local-backend validation
+accepts only an absolute HTTP or HTTPS endpoint with a host and no user
+information, query, or fragment, and rejects a negative local concurrency
+limit. Its errors retain the closest known pipeline, lane, and binding context.
+It deliberately does not require modules to be registered: that requires a
+catalog and belongs to resolution.
+
+The exact user-selectable values and validation rules are defined in
+[Configuration](../config.md). Keep additions to the file model, an
+environment override, its validation, and that reference in the same change.
+
+## Effective Resolution
+
+**Config.Resolve** first recomputes derived concurrency defaults and validates
+the configuration. It normalizes the requested pipeline ID, copies the selected
+profile, and passes the non-empty command-level LLM profile override, requested
+lane selection, and reference changes to the framework resolver.
+
+After module and validator selection, the resolver applies the effective
+profile policy to LLM-backed bindings only: command override, binding profile,
+pipeline profile, then the prompt default. Deterministic bindings remain
+profile-free, and no second inheritance decision occurs during execution. The
+public field definitions and precedence are owned by
+[Configuration](../config.md#pipelines).
+
+The resolver retains configured `validation_policy` overrides and derives one
+detached concrete terminal policy for the chunk producer and every lane's
+extract, merge, and normalize producers. That field-by-field inheritance is
+complete before preparation, and the effective values contribute to pipeline
+and checkpoint identity; execution does not interpret configuration defaults.
+
+The framework resolver supplies defaults, selects lanes, resolves validator
+chains, checks registered module and artifact compatibility, validates module
+options, and returns the fixed ordered pipeline shape. Positive validator retry
+budgets require an LLM-backed selected validator; deterministic validators are
+rejected during resolution. Eligible LLM-backed producer specifications also
+contribute their declared correction protocol to the resolved metadata. The
+resulting **EffectiveConfig** retains the selected ID, requested selection and reference
+changes, a clone of the input configuration, and the resolved pipeline.
+Callers may therefore retain or modify their input slices and maps without
+changing the resolved result, and later consumers cannot mutate the original
+configuration through the effective value. This ownership includes the nested
+PromptKit local-backend value.
+
+Resolution failures stop before module construction and source parsing. They
+include an error path for an unconfigured pipeline, missing module, missing
+capability, incompatible artifact variant, invalid option, invalid reference,
+or invalid lane selection. CLI code maps these valid-invocation failures to the
+runtime error class described in the [CLI reference](../cli.md#output-streams-and-exit-statuses).
+
+## Resolved Identity And Redaction
+
+The framework assigns the resolved pipeline a deterministic SHA-256 digest
+after defaults, lane selection, module bindings, reference bindings, validator
+chains, selected correction protocols, effective LLM profiles, and artifact
+schema identity have been resolved. The digest excludes
+its own stored value. It identifies resolved composition rather than raw YAML
+bytes, a debug payload, or all runtime state. The CLI records it as invocation
+provenance before execution; cache and checkpoint identity have additional
+owners in [Run State Internals](state.md).
+
+Configuration summaries must use **Redacted**, **RedactedSummaryPayload**, or
+**RedactedResolvedPipelinePayload**, never a direct configuration marshal.
+Those methods copy every binding and nested option container, replace values
+whose key is credential-shaped with **[REDACTED]**, and omit materialized
+reference content while retaining safe binding and reference provenance. The
+payload must not alias the source configuration or resolved pipeline.
+PromptKit's local endpoint and concurrency limit are preserved as non-secret
+configuration metadata in the independently owned summary; the object contains
+no credential value. This redaction is deliberately narrow: it protects
+configuration summaries and does not authorize recording arbitrary environment
+values or provider requests.
+
+## Invariants To Preserve
+
+- Defaults, YAML values, and environment values are applied in one direction;
+  later sources may override only their supported operational settings.
+- A configuration is structurally valid before it is resolved, and a resolved
+  pipeline is compatible with the supplied catalog before preparation begins.
+- Whitespace-normalized identifiers are unique wherever they identify a
+  pipeline, step, lane, worker, or reference slot.
+- Resolution and summary generation return detached data. Redaction must cover
+  every configured and resolved binding, including nested validator bindings.
+- The resolved digest changes when resolved composition changes and never
+  includes itself.
+
+## Focused Tests
+
+- **internal/core/config/file_config_contract_test.go** covers strict file
+  parsing, normalization, file application, and structural rejection.
+- **internal/core/config/env_contract_test.go** covers supported operational
+  overrides and their precedence.
+- **internal/core/config/validation_contract_test.go** covers configuration
+  invariants and contextual failures.
+- **internal/core/config/effective_config_contract_test.go** covers defaults,
+  selections, overrides, resolution context, digest changes, and ownership.
+- **internal/core/config/redaction_test.go** covers recursive credential
+  redaction, reference-content exclusion, and non-aliasing payloads.
+
+Run **go test ./internal/core/config** after changing this boundary. Changes to
+the handoff or resolved-composition semantics also need the focused framework
+pipeline tests.

docs/internal/dnd.md

@@ -0,0 +1,263 @@
+# D&D Module Internals
+
+This guide records the conventions shared by the production D&D module family.
+It complements [Module Internals](modules.md), which owns generic registration
+and extension mechanics, and [Configuration](../config.md), which owns the
+selectable keys, bindings, reference syntax, and default validator chains.
+
+## Durable Artifact Contracts
+
+The ten lanes have separate durable wire contracts. This guide deliberately
+does not repeat their JSON shapes or schemas.
+
+| Lane | Durable contract |
+| --- | --- |
+| Spells | [spell artifacts](../integrations/dnd-spell-artifacts.md) |
+| NPC registry | [NPC registry artifacts](../integrations/dnd-npc-registry-artifacts.md) |
+| Combat turns | [combat-turn artifacts](../integrations/dnd-combat-turn-artifacts.md) |
+| Item occurrences | [item-occurrence artifacts](../integrations/dnd-item-occurrence-artifacts.md) |
+| Item registry | [item-registry artifacts](../integrations/dnd-item-registry-artifacts.md) |
+| NPC occurrences | [NPC-occurrence artifacts](../integrations/dnd-npc-occurrence-artifacts.md) |
+| Scene descriptions | [scene-description artifacts](../integrations/dnd-scene-description-artifacts.md) |
+| Enemy events | [enemy-event artifacts](../integrations/dnd-enemy-event-artifacts.md) |
+| Location registry | [location-registry artifacts](../integrations/dnd-location-registry-artifacts.md) |
+| Location occurrences | [location-occurrence artifacts](../integrations/dnd-location-occurrence-artifacts.md) |
+
+## Family Composition
+
+The D&D registrar registers the family’s artifact codecs, extractors, typed
+append-order mergers, normalizers, validators, prompt assets, fallback LLM
+profile asset, and default validator chains. Each extractor and normalizer has
+a stable module spec, explicit execution class, strict option decoding, and a
+typed builder. Scene chunking, every extractor, and NPC, location, and item-registry
+normalization are registered as `llm_backed`; the remaining current D&D mergers
+and normalizers are `deterministic`. The metadata is available to catalog inspection and
+resolved-pipeline debug data and determines which selected bindings inherit the
+pipeline profile. The registry normalizers use `single_response_v1`, forwarding
+corrections to their reconciliation completion and retaining the accepted raw
+proposal only as an owned model candidate. Configuration remains the canonical owner of the exact keys,
+profile precedence, and validator order.
+
+Private structured-LLM response schemas are deliberately minimal. They reject
+invalid JSON structure, missing required fields, incompatible types, and
+unknown fields, while preserving semantic candidates for deterministic
+validation. Do not promote a private response envelope into a durable schema;
+the contracts above define durable data.
+
+A D&D producer that declares `single_response_v1` forwards any supplied
+semantic correction to its structured completion and returns an owned copy of
+that completion's exact validated raw response as its model candidate. It does
+not serialize normalized artifacts to create that candidate, so deterministic
+identity, evidence, warning, and durable-schema behavior remains separate from
+the model transport material.
+
+## Prompt Construction
+
+D&D LLM-facing content lives beneath `assets/dnd/`. Each module contributes a
+local `prompt.yaml` declaration and `instructions.md`; input-specific files
+such as a catalog, registry, grounding projection, or candidate collection are
+local only when that module needs them. New extractor content uses its feature
+subtree, while families with both extraction and normalization content use their
+`extract` and `normalize` subtrees. Shared visual-provenance fragments use
+the `common-dnd-` prefix. Production lane code belongs with its D&D codec,
+extractor, normalizer, and validator packages; registry projections and
+identity helpers remain in their owning entity packages rather than in a
+consumer lane.
+
+The owning module’s manifest is the source of truth for which local and shared
+assets are selected, their mount paths, their message order, cache controls,
+and the files included in its prompt fingerprint. Shared fragments belong to
+the D&D shared implementation and are selected by name rather than copied into
+module directories. The root `assets` package is a content-only boundary; its
+physical ownership and rationale are defined by
+[ADR-0011](../adr/0011-centralize-llm-assets.md).
+
+Put each rule at its narrowest owner:
+
+- universal behavior belongs in the shared system asset;
+- D&D-family behavior belongs in a selected `common-dnd-` asset;
+- rules for an input projection belong with that input asset;
+- lane-specific policy belongs in the module’s `instructions.md`; and
+- transport-envelope shape belongs in the private response schema.
+
+A rule is eligible for the system prompt only when every D&D LLM prompt needs
+it regardless of lane, inputs, or response shape. Module instructions must not
+repeat rules selected from shared assets or schemas. Reintroduce such repetition
+only after observational evaluation with representative transcripts shows that
+it improves results at the intended target models and cost; structural prompt
+tests alone are not that evidence.
+
+Every maintained D&D LLM prompt selects `dnd-extraction` as its default
+profile. The D&D registrar registers the fallback, while an operator can
+replace it with a complete profile of the same ID from the configured PromptKit
+source. Deployment profile selection is documented in
+[Configuration](../config.md#promptkit-profiles).
+
+The D&D transcript assets have distinct consumers. Scene chunking consumes the
+complete-session `common-dnd-transcript-full.md`, while extraction prompts
+consume the current-chunk `common-dnd-transcript-chunk.md`. NPC, location, and
+item normalization instead mount the generic semantic-reconciliation
+candidate and transcript-window presentation assets. Player, party, glossary,
+and compatible campaign references provide disambiguating context only when
+declared by the active prompt; they never establish evidence. Reference
+material is canonically ordered before rendering so equivalent inputs remain
+stable.
+
+Extraction prompts render the common system and identity messages first, then
+cached campaign references and the cached chunk transcript. Evidence policy and
+any lane-specific registry, catalog, or grounding projection follow that
+prefix. The final module instructions message is ephemeral. This keeps the
+reusable extraction prefix identical while preserving the lane-specific suffix.
+
+Scene chunking intentionally uses a different order: system, cached campaign
+references, uncached module instructions, then the final ephemeral full
+transcript. Entity normalization also has its own order: D&D system, mandatory
+generic protocol, ephemeral domain semantic instructions, generic candidate
+presentation, and final ephemeral generic transcript windows. These orders and
+cache controls are prompt behavior; change them only through the owning
+manifest and prompt declaration.
+
+## Evidence, Candidates, And Normalization
+
+The current transcript is the only durable evidence source. Extractors assign
+the current source identity, preserve candidate evidence ranges for validators,
+and canonically order or remove exact duplicate ranges without asking the
+model to repair semantic errors. Campaign context and generated artifacts may
+ground names or control routing, but they never establish evidence for a D&D
+result.
+
+Default chains keep responsibilities separate: structural validators assess the
+candidate, source-reference validators resolve cited ranges against the current
+source and require extraction evidence to stay within the current chunk,
+durable-schema validation checks an approved representation, and
+relatedness validators report advisory evidence concerns. The configured order
+is documented in
+[Configuration](../config.md#production-validator-keys-and-default-chains).
+
+Every D&D rejection describes the correction in transcript-grounded domain
+terms, using contextual names, artifact fields, and source segment ranges when
+useful. The guidance must not ask the model to reproduce durable entity IDs,
+hashes, validator module keys, or reason codes. Those identifiers remain in
+ordinary validation provenance; only the actionable semantic guidance is
+eligible for the correction prompt.
+
+Enemy-event extraction additionally rejects a second `engaged` observation for
+the same comparison identity within one scene-scoped result. Normalization may
+combine results from distinct scenes, so it intentionally does not apply that
+rule. Configuration owns the exact validator key and chain position.
+
+Normalizers are deterministic for spells, combat turns, item occurrences, NPC
+occurrences, scene descriptions, enemy events, and location occurrences. They
+canonicalize display values and evidence, use source-document order for stable
+output, and issue bounded warnings for changes or collapsed duplicates. NPC,
+item, and location registry normalizers are intentional exceptions: each first
+produces a deterministic candidate set, then may use a bounded structured-LLM
+proposal to reconcile identity groups.
+
+## Semantic Registry Reconciliation
+
+The three registry normalizers instantiate the domain-neutral
+`internal/framework/semanticreconcile` engine with default bounds. Each
+eligible candidate receives a contiguous, one-based `candidate_id` for that
+request. The model sees that handle, the candidate label and source-free
+evidence ranges, plus bounded transcript windows; it returns only duplicate
+groups of supplied handles and one supplied canonical handle per group. It
+never returns names, evidence, durable IDs, or replacement records. Identical
+labels and evidence remain independently selectable because their handles are
+distinct.
+
+The generic core owns the mandatory handle protocol, candidate and transcript
+presentation, the private response schema, source-reference validation,
+candidate and combined-material limits, structured completion, proposal
+assessment, stable group ordering, and typed plan-application mechanics. The
+D&D prompt contributes its system message and registry-specific semantic
+instructions. The generic registrar registers the shared prompt and schema;
+the D&D registrar registers each consuming prompt and the fallback profile.
+
+Fewer than two eligible candidates skips the LLM without a semantic warning.
+An exceeded bound also skips the call and preserves the deterministic
+preprocessed registry, adding the registry's bounded fallback warning. Invalid
+structured output or discarded proposal groups use the normalizer's existing
+retry contract; retry exhaustion preserves the safe deterministic or
+partially applied result and emits its bounded fallback warning. Provider,
+transport, cancellation, and context-material failures remain execution
+errors.
+
+Application remains typed and registry-owned. All three policies select the
+canonical member's normalized display name, union member evidence in source
+order, preserve ungrouped records, and derive durable identity only after
+consolidation. NPC IDs derive from the final name. Item IDs also derive from
+the final name, and a typed guard prevents currency aliases from crossing
+denominations or mixing currency with non-currency records. Location IDs
+derive from the final name and final evidence, preserving same-name,
+parent/child, and distinct physical-place identities. Registry warning scopes,
+reason codes, and postconditions remain outside the generic core.
+
+## Generated References And Grounding
+
+Normalized D&D artifacts can be handed to a later step through a generated
+reference binding. The framework verifies artifact compatibility and retains
+producer provenance; consumers resolve the handed-off artifact into an
+immutable, validated projection for each operation. External files are checked
+during preparation, while generated artifacts are resolved at the handoff.
+
+NPC and item registry consumers receive names-only grounding. Location
+consumers receive a contextual selector containing the canonical name and the
+registry references needed to distinguish same-name places. The calling module
+resolves those supplied selections locally and maps them into the unchanged
+durable ID/name pair; an unknown or ambiguous selection rejects the complete
+occurrence result rather than accepting a partial mapping. The NPC registry
+additionally supplies names-only actor grounding to spells, combat turns, and
+enemy events.
+
+Registry references establish a registry identity and may disambiguate a
+selection, but never become occurrence evidence. Each occurrence keeps its own
+current-transcript source references, even when it was grounded through the
+same registry record.
+Scene descriptions are eligibility-only projections: they retain current-chunk
+classification data, not scene prose or evidence, and exist to route combat
+extraction. Enemy-event extraction also projects combat turns to `actor` and
+`turn_kind` and filters NPC occurrences to `combat_opponent` names and kinds.
+These projections are guidance only and never event evidence.
+
+## Lane-Specific Rules
+
+The following differences are intentional and should remain explicit when a
+shared helper changes.
+
+Shared D&D text comparison is identified by `dnd.text_comparison.v1`. Any
+semantic change requires an explicit policy-version review for every affected
+identity, mapping, normalization, and validator policy; helper source is not a
+checkpoint fingerprint.
+
+| Lane | Intentional behavior |
+| --- | --- |
+| Spells | May use a spell-catalog overlay and optional NPC grounding; the catalog validator supplies domain-specific semantic checks. |
+| NPC registry | Establishes transcript-grounded NPC identities, including factual third-party mentions, without assigning occurrence categories. It does not consume an NPC registry, and its normalizer is the LLM-assisted reconciliation exception described above. |
+| Combat turns | Requires a scene-description artifact. It calls the LLM only for an exact `combat` classification; exact non-combat classifications return an accepted empty result, while missing or mismatched classifications return an empty result with a bounded warning. Optional NPC grounding never becomes evidence. |
+| Item occurrences | Requires the normalized item registry for exact deterministic grounding at extraction and normalization. Campaign context may disambiguate, but the registry never becomes occurrence evidence. |
+| Item registry | Produces source-grounded item types and unique designations. Its LLM-assisted reconciliation is proposal-only, preserves distinct currency denominations and item types, and does not create per-instance identities. |
+| NPC occurrences | Requires the normalized NPC registry at extraction and normalization, using it for canonical actor grounding only. It separately emits cited current-transcript occurrence facts, including `mentioned`, rather than deriving them from registry provenance. |
+| Scene descriptions | Produces the classifications consumed by combat routing; it does not consume an NPC registry or provide evidence for combat artifacts. |
+| Enemy events | Requires NPC, scene-description, combat-turn, and NPC-occurrence artifacts. It calls the LLM only for an exact `combat` classification, records ordered observations rather than terminal state, and normalizes recognized names through the NPC registry while preserving grounded collective labels. |
+| Location registry | Produces a source-anchored, session-scoped registry from stable proper names or unique in-world designations. Its LLM-assisted reconciliation is proposal-only and never collapses same-name places without validated identity and evidence rules. |
+| Location occurrences | Requires the normalized location registry for both extraction and normalization. Its [durable occurrence categories](../integrations/dnd-location-occurrence-artifacts.md#occurrence-categories) distinguish explicit speculation from unsupported inference; the deterministic normalizer enforces exact registry grounding and never turns registry provenance into occurrence evidence. |
+
+The combat and scene-description contracts describe their exact handoff and
+empty-result behavior in more detail:
+[combat turns](../integrations/dnd-combat-turn-artifacts.md) and
+[scene descriptions](../integrations/dnd-scene-description-artifacts.md).
+The [enemy-event contract](../integrations/dnd-enemy-event-artifacts.md)
+defines its durable semantics; [Configuration](../config.md) owns its
+selectable bindings and validation chains.
+
+## Focused Verification
+
+When changing D&D behavior, test the affected codec, extractor, normalizer,
+validator, prompt-asset manifest, and registry projection. Also test generated
+handoffs at the integration boundary and run the full D&D module suite:
+
+~~~sh
+go test ./internal/modules/dnd/...
+go test ./internal/modules/integration/...
+~~~

docs/internal/llm.md

@@ -1,252 +1,324 @@
 # LLM Runtime Internals
 
-`internal/framework/llm` implements Notarius's transport boundary for structured
-completion. It contains the Scriptorium adapter, concurrency scheduler,
-prompt/schema registries, selected-profile recording, and provider-error
-redaction.
+`internal/framework/llm` is Notarius’s provider-independent structured
+completion boundary. It adapts framework requests to PromptKit, bounds
+provider calls, assembles registered prompt and schema assets, records selected
+profiles, and redacts provider errors. The architectural boundary is defined in
+[Architecture](../policy/architecture.md#llm-boundary); profile sources,
+credentials, and concurrency settings belong in
+[Configuration](../config.md#promptkit-profiles) and
+[Configuration](../config.md#concurrency-output-cache-and-debug).
 
-Provider-neutral ownership rules are defined in
-[Architecture](../policy/architecture.md#llm-boundary). Profile sources,
-credentials, and concurrency settings are defined in
-[Configuration](../config.md).
+## Structured Completion Boundary
 
-## Structured Contract
+Modules and LLM-backed validators depend only on
+`contracts.StructuredLLMClient`. A completion request supplies a prompt ID and
+version, optional profile and session IDs, named input material, variables, and
+a caller-owned decode target. The successful response returns the validated raw
+structured bytes together with non-secret provider, model, profile, and token
+metadata.
 
-Modules and LLM-backed validators depend on
-`contracts.StructuredLLMClient.CompleteStructured`. A request identifies a
-prompt and optional profile/session, supplies named input materials and
-variables, and provides a caller-owned decoding target. A successful response
-contains the validated raw structured bytes plus non-secret provider, model,
-profile, and token metadata.
+The caller owns the domain behavior: it chooses the prompt, prepares inputs,
+selects the private response schema, and interprets the decoded result. The
+adapter does not own source evidence, artifact conversion, normalization, or
+durable schemas. Those responsibilities remain with the module and its
+[integration contract](../integrations/).
 
-The caller owns prompt selection, response-schema selection, and interpretation
-of the decoded result. `LLMInputMaterial` keeps source and reference bytes with
-their origin metadata so the adapter can pass named artifacts to Scriptorium
-without exposing Scriptorium types through stage contracts.
+The calling module also resolves contextual entity selections and attaches any
+application identity; PromptKit and this adapter do not own entity identity.
 
-## Production Construction
+`PromptKitClient` validates the request target and prompt identity, maps each
+named material to a PromptKit inline artifact while preserving its origin URI,
+passes the supplied request session through to PromptKit's direct per-run
+session field, retains the same value as the `session_id` prompt variable for
+maintained prompt compatibility, and forwards profile selection. It does not
+derive or replace session values; the CLI owns that policy. It then creates one
+frozen prepared execution, captures its caller-owned credential-redacted
+details for debug material, and executes that exact snapshot through
+PromptKit's prepared-execution boundary. The direct field
+is authoritative for provider session behavior. A session ID is a stable,
+non-secret correlation identifier and may be exposed to providers and provider
+observability. The adapter returns PromptKit’s validated raw bytes rather than
+re-encoding the decoded target. An empty optional material is represented as
+one space so its named input is retained by PromptKit.
 
-`internal/cli` constructs the production runtime by:
+When a request includes semantic correction material, the adapter validates and
+defensively copies it before preparation, then appends exactly two messages
+after the ordinarily rendered prompt: the prior response as an assistant
+message and the correction guidance as a user message. Requests without a
+correction do not add messages or introduce caller roles. Ordinary request
+summaries record correction byte counts and digests only; complete messages are
+available solely in an explicitly requested debug trace.
 
-1. allocating the asset registry populated by the generic, Seriatim, and D&D
-   package-family registrars;
-2. creating a `ScriptoriumClient` from the effective profile source;
-3. attaching an `LLMProfileRecorder`;
-4. creating a scheduler from the effective concurrency limit;
-5. returning a `ScheduledClient` wrapper;
-6. decorating that shared client before preparation when debug recording is
-   enabled; and
-7. injecting that one shared client into complete pipeline preparation before
-   the source file is read or the runner is invoked.
+The adapter leaves the ordinary rendered message prefix, named inputs,
+variables, session, profile, execution overrides, prepared-execution path, and
+PromptKit repair policy unchanged for a corrected request. It never imports a
+PromptKit message type into a module or pipeline contract. PromptKit reports
+actual structural repair count and cumulative token usage per completion; the
+pipeline's safe terminal debug record projects those values without copying
+message content.
 
-The D&D scene chunker and spell, NPC, combat-turn, item-event, NPC-interaction, and
-scene-description extractors retain this
-injected client and use it for every structured completion. Operation requests
-do not carry an LLM client.
+Client construction may also receive a run-wide reasoning-effort override from
+the CLI factory boundary. The adapter copies the caller-owned pointer and
+creates a fresh PromptKit execution override for each request: a nil pointer
+inherits the selected profile, a non-empty value replaces it, and an empty
+value clears inherited reasoning. The CLI's mutually exclusive
+`--reasoning-effort` and `--clear-reasoning-effort` controls select those
+states. With neither flag, profile behavior remains unchanged. Because
+production constructs one shared client, the selected state applies uniformly
+to module calls, retries, and LLM-backed validators for the whole run.
 
-The CLI separately gathers explicit profile IDs from resolved LLM-capable stage
-and validator bindings. It prepares a small internal check prompt for each ID so
-missing or invalid profiles fail before pipeline execution. The runtime profile
-override syntax and scope are defined in the
-[CLI reference](../cli.md#run); binding rules are defined in
-[Configuration](../config.md#module-bindings).
+An empty request profile lets the prompt select its configured default. Before a
+run begins, the CLI asks the adapter to inspect every explicit profile on the
+resolved selected LLM-backed bindings and validators, including inherited
+pipeline profiles. Inspection resolves the profile and its selected backend and
+target without loading a prompt, reading credentials, admitting capacity, or
+contacting a provider, so a missing or invalid explicit profile fails before
+stage execution while a valid `api_key_env` may remain unset. Calls record the
+profile actually selected by PromptKit. The recorder trims and deduplicates
+non-secret profile identity, provider, model, selected backend ID, and
+effective reasoning values for manifest use. Entries that differ in backend or
+reasoning remain distinct and deterministically ordered. Endpoint-only profiles
+retain an empty backend ID, which the published JSON omits. Successful
+completion responses and recorded profile manifests identify the adapter
+provider as `promptkit`.
 
-## Scriptorium Adapter
+The CLI's profile-inspection engine and the production adapter use the same
+profile-source construction to apply the configured profile directory or file,
+the optional registered fallback profile assets, and the optional conventional
+`local` backend. Preflight therefore resolves the same profile sources and
+backend membership as runtime without performing generation. Fallback assets
+are mounted only when at least one source is registered. The production D&D
+registrar contributes its `dnd-extraction` fallback, and the maintained D&D
+prompts select that logical ID by default. PromptKit owns source precedence and
+profile parsing and inheritance: an operator-provided matching profile takes precedence over a
+fallback profile without Notarius merging either document.
+When the registration is absent, a profile selecting `backend: local` fails
+inspection instead of falling back to a built-in or endpoint-only target.
 
-`ScriptoriumClient` converts a Notarius request into a Scriptorium `RunRequest`.
-It validates the decoding target and prompt identity, maps named input materials
-to inline artifacts, forwards explicit profile and session context, delegates
-rendering/provider execution/structured validation, and unmarshals successful
-JSON into the caller target.
+Before execution, the adapter also contributes a non-secret checkpoint
+fingerprint for the effective PromptKit profile source. It combines the
+identity of PromptKit's compiled-in profile catalog with a deterministic digest
+of every YAML profile in the configured profile directory, or of the configured
+profile file, and a deterministic digest of the flattened fallback profile
+assets. The fingerprint contains neither profile content nor source paths. It
+covers inherited pipeline profiles, explicit binding profiles, and
+prompt-selected defaults, so changing a model or other profile setting cannot
+reuse checkpoints created under the
+prior profile source. This cache identity is independent of durable
+profile provenance: run manifests continue to list only profiles actually
+observed during LLM calls. When the local backend is registered, a second
+fingerprint hashes its trimmed endpoint behind a stable marker. Changing that
+semantic execution target invalidates checkpoint reuse. The raw endpoint is not
+stored in checkpoint identity, and the local concurrency limit is excluded
+because it changes scheduling rather than execution semantics.
 
-Empty optional input material is represented by a single space so Scriptorium
-retains the named input. The client returns Scriptorium's validated structured
-bytes rather than re-encoding the caller target, allowing modules to preserve
-the runtime result exactly.
+## Shared Provider-Call Limit
 
-Selected profile, provider, model, and token metadata are mapped into the
-Notarius response. The recorder deduplicates profiles by identity and supplies
-manifest-safe profile summaries after actual calls; manifest population does
-not guess the selected prompt default in advance.
+Production construction creates one PromptKit client and wraps it in one
+scheduled client. The scheduler has a fixed, positive permit limit, serves
+queued calls in FIFO order, and removes a queued call when its context is
+cancelled. It rechecks the caller context after admission and before dispatch.
+A granted permit is released exactly once on every completion path.
 
-Generated-output validation failures and provider failures are wrapped with
-prompt context. Error strings pass through bearer-token redaction before they
-cross the runtime boundary.
+The scheduled wrapper surrounds every `CompleteStructured` call, so concurrent
+lanes, pipeline retries, and LLM-backed validators share the same provider-call
+ceiling. This ceiling is independent of pipeline worker concurrency; changing
+worker counts cannot exceed the configured LLM limit. The configuration field
+and its effective default are owned by
+[Configuration](../config.md#concurrency-output-cache-and-debug).
 
-## Scheduling
-
-`Scheduler` uses a bounded permit count and a FIFO waiter queue. Immediate
-acquisition increments the in-flight count; queued acquisition waits for a
-permit or context cancellation. Cancellation removes a queued waiter, while a
-cancelled waiter that has already received a permit releases it.
-
-`ScheduledClient` acquires a permit around each structured completion and
-defers release on every result path. The effective limit and default are
-configuration facts in [Configuration](../config.md#defaults).
-
-This provider-call ceiling is independent of the pipeline's extract worker
-limit. Concurrent lanes, retries, and validators all use the same scheduled
-client, so increasing framework workers cannot exceed `total_llm`. Pipeline
-dispatch and cancellation mechanics are documented in
-[Pipeline Internals](pipeline.md#execution-flow).
+PromptKit applies a second, independent admission limit when the selected
+profile names a limited backend. It sits beneath the Notarius scheduled client,
+so it may narrow but cannot expand the application-wide limit. Built-in
+OpenRouter profiles select PromptKit's reserved backend and its upstream
+capacity policy. A positive configured local-backend limit bounds active local
+generations inside PromptKit; zero leaves that backend unlimited there.
+Endpoint-only profiles do not select a PromptKit backend and remain limited
+only by the Notarius scheduler.
 
 ## Prompt And Schema Assets
 
-`AssetRegistry` combines caller-owned prompt filesystems under stable prefixes
-and rejects invalid or conflicting registrations. Production module packages
-register their own prompt and schema assets; generic framework code contains no
-D&D prompt content. `internal/framework/promptfs` provides the domain-neutral
-filesystem composition helper used to combine module-owned files with shared
-domain prompt fragments.
+An `AssetRegistry` collects prompt, schema, and optional fallback-profile
+filesystems from production module families. It flattens registered roots into
+the corresponding PromptKit filesystems and rejects invalid roots, unreadable
+assets, duplicate paths, and missing prompt or schema files during preparation.
+Fallback assets receive a safe content digest for checkpoint identity; raw
+paths and bytes are never included. The framework’s `promptfs` helper combines
+module-selected prompt files with reusable domain fragments without making the
+framework depend on D&D content.
 
-The D&D scene chunker and spell, NPC, combat-turn, item-event, NPC-interaction, and
-scene-description extractors each declare an
-ordered prompt asset manifest. The manifest lists the package-owned YAML and
-Markdown files, then the exact shared fragments rendered by that prompt; the
-same ordered list drives both filesystem mounting and the prompt fingerprint.
-Unused shared assets are neither mounted nor fingerprinted. Universal
-extraction-evidence and output policy lives only in the shared extraction
-assets; package-owned prompt files retain artifact-specific rules. The scene
-prompt keeps its separate output rule because it does not render the
-extraction-evidence asset.
+LLM-facing content is embedded once by the root `assets` package. Each consumer
+uses only its scoped subtree, while the module retains ownership of its prompt
+declaration, ordered manifest, private response-schema identity, and
+registration. Shared D&D fragments are selected by D&D's shared implementation;
+the detailed convention is in [D&D Module Internals](dnd.md). This physical
+arrangement and its data-only boundary are defined by
+[Architecture](../policy/architecture.md) and
+[ADR-0011](../adr/0011-centralize-llm-assets.md), rather than by this runtime
+guide.
 
-### D&D Extraction Prompt Ordering And Cache Boundaries
+The generic registrar is the sole production registration owner for the
+semantic-reconciliation default prompt and private response schema. The
+domain-neutral reconciliation package also exposes only its mandatory protocol
+and candidate/transcript presentation files for domain prompt manifests. D&D
+registry normalizers mount those files while retaining ownership and hashing
+of their D&D system message, semantic instructions, and complete prompt
+declaration. The response schema is therefore registered once even though
+several typed normalizers select it.
 
-D&D extraction prompts order messages from the most reusable content to the
-most variable content. New extraction lanes use these tiers in order:
+Mounted prompt assets determine a module's fingerprint. The fingerprint hashes
+only the module and shared files explicitly selected by its manifest, so an
+unrelated asset does not invalidate a checkpoint. Schema loaders validate JSON,
+attach identity and digest metadata, make defensive copies, and expose
+diagnostics without raw schema bytes.
 
-1. universal shared content, including the system, extraction-evidence, and
-   in-world identity messages;
-2. stable campaign or run context shared across lanes, including campaign
-   references;
-3. stable subset- and lane-specific context and instructions, including an NPC
-   registry, catalog, task, or extraction instructions when applicable;
-4. the chunk transcript as the final user message.
+Semantic-reconciliation normalizers extend this identity with the shared
+response-schema digest, framework policy version, and complete limit-policy
+digest. Their manifest metadata records the same content-free prompt, schema,
+policy, and limit identities together with domain identity and normalization
+policies. Request-local handles, source material, proposal content, and raw
+asset bytes are not checkpoint metadata.
 
-This ordering lets requests reuse the longest identical prefix before the
-per-chunk transcript changes. Cache reuse requires the preceding message
-sequence and content to be exactly identical; semantic similarity is not
-sufficient. Cache boundaries belong at the ends of reusable stable tiers,
-subject to the provider's cache-boundary limit. The shared identity and
-campaign-reference messages form the first two extraction boundaries. Spell,
-combat, and interaction prompts add a boundary at the shared NPC registry. Each extraction
-prompt places its final boundary on its lane-specific instructions, immediately
-before the transcript. The transcript does not carry cache control because no
-reusable content follows it.
+Private response schemas validate a model transport envelope. They are not the
+durable artifact schema and should not be documented as an external wire
+contract. Durable formats and compatibility rules remain in the
+[integration contracts](../integrations/).
 
-Accordingly, the common prefix of the spell, NPC, combat, item-event, and interaction
-extraction prompts is system,
-extraction evidence, identity, and campaign references. The NPC prompt then
-renders task, instructions, and transcript. Spell renders the NPC registry,
-catalog, task, instructions, and transcript. Combat renders the NPC registry,
-task, instructions, and transcript. Item-event renders task, instructions, and
-transcript without a generated-artifact input. NPC interaction renders the names-only 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
-transcript and campaign-reference messages ephemeral.
+## Prompt Maintenance And Backend Caching
 
-The scene-description extractor deliberately omits the citation-oriented
-`common-dnd-extraction-evidence.md` asset because Notarius attaches the whole
-accepted chunk range itself. Its manifest is system, shared identity, shared
-campaign references, lane task, lane instructions, then the transcript. The
-identity, campaign-reference, and instruction messages are ephemeral cache
-boundaries; the transcript is last and has no cache control. Compatible shared
-messages remain canonical shared assets rather than copied package text.
+Prompt message order and shared asset bytes are runtime behavior. Backend cache
+reuse depends on identical preceding roles, rendered bytes, and cache-control
+metadata—not merely equivalent meaning. Keep reusable shared assets
+byte-identical and preserve each prompt’s declared ordering and cache controls
+when editing it.
 
-### D&D NPC Normalization Prompt Ordering And Cache Boundaries
+For sibling prompts that can reuse the same source material, order universal
+shared context first, request source material next, and module-specific
+suffixes last. Put a cache boundary at a reusable prefix that is useful to the
+backend. Redundant intermediate cache boundaries do not extend that reusable
+prefix and add no value.
 
-NPC normalization has a distinct prompt and response-schema identity from NPC
-extraction. Its stable message tiers are the common D&D system and identity
-assets, followed by package-owned task and normalization instructions. Cache
-boundaries follow the shared identity tier and the package instructions. The
-variable tail contains the private candidate-name-and-range input and a
-windowed transcript input whose cited units provide local context; neither has
-a cache boundary because it changes with the document.
+Prompt-family owners may choose a different sequence when their inputs and
+reuse pattern differ. The D&D family’s extraction, scene-chunking, and NPC
+normalization policies are maintained in [D&D Module Internals](dnd.md#prompt-construction).
+Do not add tests that enforce prompt prose; prompt tests should verify the
+meaningful input placement and cache controls of the prompt being changed.
 
-This prompt intentionally omits extraction-evidence and campaign-reference
-assets: it reconciles existing records rather than extracting events or adding
-evidence. Its package-owned manifest and schema identity are fingerprinted
-separately, so a normalization prompt or schema change cannot reuse a prior
-normalization checkpoint.
+## Validation, Repair, And Retries
 
-Shared wording belongs in the canonical assets under
-`internal/modules/dnd/shared`; extraction packages reference those assets in
-their manifests instead of copying similar text into package-local files.
-Package-local assets contain only lane-specific content. An extraction lane may
-depart from the tier order only when prompt-quality evidence or a provider
-constraint makes the exception necessary; document the exception and rationale
-here when it becomes implemented behavior.
+PromptKit performs prompt rendering, provider execution, and the prompt’s
+structured-output validation. The adapter reports an empty result, validation
+failure, empty structured body, or decode failure as
+`ErrInvalidStructuredOutput`, while retaining the returned raw bytes and debug
+material when they exist. Provider failures remain operational errors rather
+than output-validation failures. Apart from documented context, capacity, and
+invalid-output categories, provider error values and types do not cross the
+adapter error chain; callers receive only a credential-redacted diagnostic.
 
-Schema helpers load embedded JSON Schema with identity and digest metadata,
-return defensive copies, and expose a diagnostics map that omits schema bytes.
-The small framework registry contains only generic test schemas; production
-schemas remain package-owned.
+When PromptKit rejects backend admission before generation, the adapter maps
+`promptkit.ErrCapacityExceeded` to
+`contracts.ErrLLMCapacityExceeded`, retaining prompt context and a redacted
+upstream diagnostic without exposing the PromptKit sentinel or capacity-error
+type as a framework contract. When supplied, the normalized selected backend
+ID appears only in that safe application-owned diagnostic context. A canceled
+caller context takes precedence. The adapter does not retry capacity failures;
+the pipeline's existing binding attempt policy sees the operational error and
+decides whether to rerun the complete operation.
 
-The spell, NPC, combat, item-event, NPC-interaction, and scene-description extractors'
-package-owned prompts declare their
-structured JSON inputs and private response schemas. Each private response
-schema remains separate from its durable artifact codec schema; this work does
-not use shared schema fragments or schema generation. Those private schemas own
-the transport envelope—required fields, JSON types, nullability, and
-unknown-field rejection—while deterministic validators own semantic constraints
-such as enum membership, non-empty values and collections, and positive
-numbers. The spell extractor's prompt declares a required
-`application/json` `spell_catalog` input and an optional `application/json`
-`npcs` input. The extractor generates
-the catalog input from its prepared
-effective catalog as `{"spell_names":[...]}` using sorted canonical names only.
-The shared D&D prompt assets include a generic NPC grounding fragment directly
-after the campaign reference message for spell, combat, and interaction prompts. When an NPC
-registry is bound, the
-domain registry boundary strictly decodes and identity-validates one durable
-artifact, re-encodes canonical JSON for provenance, and separately generates a
-names-only prompt projection. The unbound projection is exactly `{"npcs":[]}`.
-Prompt input and component-local checkpoint digests cover the projected bytes;
-manifests retain the optional full registry digest/count rather than names,
-overlay bytes, registry paths, or source metadata. Combat and interaction prompt,
-response-schema, mapping, normalization, identity, and registry-projection
-fingerprints remain separate semantic inputs to checkpoint identity.
+PromptKit executes structural repair within its structured-output flow. The
+maintained production prompt manifests declare one additional repair attempt.
+When a resolved binding supplies a repair value, the adapter inspects the
+prompt, copies its complete output contract, changes only the repair limit, and
+passes that complete replacement contract to PromptKit. This preserves the
+prompt's output format, validation mode, schema, and provider structured-output
+settings.
 
-## Debug And Redaction Boundaries
+A successful repair is an ordinary successful completion, not a warning. The
+adapter reports PromptKit's actual repair count and its cumulative usage
+directly, without adding the initial and corrective counts again. Debug prompt
+material records the configured complete contract; debug response material
+records the repaired response and actual validation result. If the repair
+budget is exhausted, the adapter retains the final raw bytes and debug material
+and reports `ErrInvalidStructuredOutput`. Generation failures during an initial
+or corrective call remain provider-neutral operational errors with the same
+redaction boundary.
 
-The pipeline may wrap the client with a debug recorder that captures prepared
-prompt/response material for an explicitly requested debug run. Debug summaries
-and manifests receive identities, hashes, usage, and selected profile summaries
-rather than prompt, source, reference, schema, or response content.
+Structural repair does not replace pipeline retry behavior: a binding's
+configured retry count reruns its complete stage attempt after an operational
+or structural error, module-requested retry, or actionable semantic rejection.
+The pipeline owns attempt lifecycle, validation chains, and retry diagnostics;
+see [Pipeline Internals](pipeline.md#validation-retries-and-output) and the
+[binding reference](../config.md#module-bindings-and-validators).
 
-The Scriptorium error wrapper removes bearer credential values from surfaced
-provider errors; `RedactSecrets` and `ErrorWithSecretsRedacted` support known
-secret values elsewhere in the runtime. Config summaries use a separate
-clone-and-redact path in `internal/core/config`. These mechanisms implement the
-security invariant in
-[Architecture](../policy/architecture.md#state-output-and-safety); operator
-handling of debug data is defined in [Operations](../operations.md#debug).
+## Timeout Ownership
 
-## Failure Behavior
+The caller context remains the outer cancellation authority. PromptKit applies
+a positive effective generation timeout as an inner request deadline; an
+explicit zero disables only that generation deadline. The HTTP client timeout
+is a separate transport-wide cap. Notarius forwards the caller context and
+does not install another timeout wrapper around PromptKit.
 
-- Invalid targets, missing prompt IDs, malformed structured output, and
-  Scriptorium failures return contextual errors to the calling module.
-- Scheduler construction rejects non-positive limits; acquisition respects
-  context cancellation.
-- Asset registration rejects invalid roots, missing content, and path conflicts.
-- Schema loading distinguishes missing assets, invalid JSON, and invalid
-  metadata.
-- Profile validation errors occur during CLI preparation when an explicit
-  selected ID cannot be prepared.
+The selected PromptKit profile owns generation settings. Notarius binding
+retries remain outside the adapter and repeat the complete module operation
+and validation chain. PromptKit does not add a provider retry loop.
+Operator-facing behavior is summarized in
+[Operations](../operations.md#operational-limits), and the pinned upstream
+contract is identified in
+[PromptKit Integration](../integrations/pkg-promptkit.md).
 
-## Tests To Inspect
+## Observability And Redaction
 
-- `internal/framework/llm/scriptorium_client_test.go`: adapter mapping and local
-  HTTP integration.
-- `internal/framework/llm/scheduler_test.go` and
-  `scheduled_client_test.go`: permits, FIFO behavior, cancellation, and wrapper
-  release.
-- `internal/framework/llm/asset_registry_test.go` and
-  `schema_registry_test.go`: asset composition, validation, and defensive
-  copies.
-- `internal/framework/llm/secrets_test.go`: provider-error redaction.
-- `internal/cli/run_contract_test.go`: profile validation, production client
-  wiring, manifest recording, and debug integration.
-- Module-local `scriptorium_assets_test.go` files: prompt inputs and package
-  asset registration.
+When debug recording is enabled, the pipeline decorates the shared client. The
+wrapper records prepared prompt and response material, timing, selected profile
+and backend, effective model parameters, and call identifiers in the run’s
+debug bundle, including material available from a failed structured completion.
+Effective parameters use PromptKit's stable lower-case JSON field names and may
+include `backend_id`. For a successful completion, a debug-write failure is
+surfaced; when the completion already failed, its call error remains the
+result. Debug-bundle location, retention, and handling are operational concerns
+documented in [Operations](../operations.md#debug-bundles).
+
+The attempt-terminal summary is a separate safe trace record: it contains
+attempt kinds, validator outcome counts and reason codes, effective policy,
+terminal action, and repair/usage references. It excludes raw assistant
+responses and correction text. Those values can appear only in the explicitly
+requested detailed prompt and response artifacts, which require sensitive-data
+handling.
+
+Run manifests receive selected profile summaries, including optional effective
+backend and reasoning provenance, and component identities—not prompt, schema,
+source, reference, or response content. The published field semantics belong
+to the [JSON output contract](../integrations/json-output.md#manifestjson).
+Provider error text is wrapped with prompt context and bearer credentials are
+redacted before it crosses the runtime boundary. Known-secret redaction is
+available to other runtime collaborators; it does not make prompt or response
+contents safe for general logging.
+
+Generation failures expose an application-owned category and optional HTTP
+status. Provider code, type, and message remain debug-only, after redaction.
+
+## Failure Boundaries
+
+- Construction fails for missing asset registries, mutually exclusive profile
+  sources, invalid asset registration, or a non-positive scheduler limit.
+- Preparation failures, unavailable explicit profiles, provider failures, and
+  context cancellation propagate to the calling stage with context.
+- Backend admission exhaustion is a provider-neutral operational error and is
+  not classified as invalid structured output or validator rejection.
+- Malformed or schema-invalid provider output is classified separately as
+  invalid structured output so the module or pipeline can apply its own retry
+  and rejection policy.
+- Domain semantic checks, evidence decisions, and deterministic normalization
+  run outside the provider adapter.
+
+## Focused Verification
+
+Read the LLM adapter, scheduler, asset registry, schema loader, and redaction
+tests when changing this boundary. Prompt changes also require the owning
+module’s asset tests, and retry or debug changes require focused pipeline or
+CLI coverage. The focused runtime and D&D checks are:
+
+~~~sh
+go test ./internal/framework/llm/... ./internal/modules/dnd/...
+~~~

docs/internal/modules.md

@@ -1,728 +1,180 @@
-# Module And Validator Internals
-
-Production module and validator implementations live under their domain-first
-trees in `internal/modules`.
-The selectable keys, configuration options, reference slots, and default
-validator chain are canonical in the
-[module](../config.md#implemented-production-modules) and
-[validator](../config.md#implemented-production-validators) catalogs in
-Configuration.
-
-## Extension Pattern
-
-A stage module package provides a stable key, constructor, contract
-implementation, `ModuleSpec`, `Register`, and focused behavior and registration
-tests. A validator package follows the same pattern with `ValidatorSpec` and the
-validator registry. Package-family registrars compose those leaf registrations
-into the production catalog and own family-level policy such as default
-validator chains and prompt asset collection.
-
-Production input, chunk, output, and D&D spell-, NPC-, combat-, item-event-, interaction-, and scene-description-extract packages
-register strict option decoders and run-local builders. Preparation decodes their options into
-implementation-owned values and injects dependencies plus the materialized
-reference set for the selected target. Each builder receives an isolated clone
-of that set; input and output builders receive no references. The spell, NPC,
-combat, item-event, interaction, and scene-description extractors are typed over the canonical D&D model. D&D validators, merge,
-and normalize use typed variants; JSON representation validators use serialized
-requests; and unconditional validators expose separate chunk and typed
-variants. The D&D production registrar registers the canonical typed spell,
-NPC, combat, item-event, interaction, and scene-description implementations, including their kind-specific merge and
-normalize behavior.
-
-For D&D artifact defaults, generic JSON syntax validation runs first. Rejecting
-domain validators then own semantic diagnostics before generic JSON Schema
-validation provides the final rejecting representation backstop; warning-only
-relatedness validators run last. This default composition does not reorder an
-explicitly configured validator chain.
-
-Prepared extractors, extract validators, and codecs may be reused concurrently
-by the run-wide extract pool. Production implementations are immutable after
-construction: they retain only typed options, immutable assets, or the shared
-concurrency-safe LLM client. Implementations that introduce mutable state must
-synchronize that state without creating a separate provider scheduler.
-
-Specs expose capability and execution metadata without constructing an
-implementation. Registry entries separately expose option validation and
-run-local construction. Chunk, extract, merge, and normalize modules that accept
-auxiliary material declare identical reference slots from both
-`ReferenceSlots()` and `ModuleSpec().ReferenceSlots`; registration tests enforce
-that agreement. Runtime delivery uses the corresponding stage request's
-`References` field.
-
-LLM-backed extensions own their prompt definitions and response schemas under
-package-local embedded assets. Shared filesystem composition belongs in
-`internal/framework/promptfs`; reusable D&D prompt fragments, reference
-declarations, prompt-input assembly, and source-unit/citation helpers belong in
-`internal/modules/dnd/shared`, which owns operation-scoped indexed
-source-reference validation, citation traversal, ordering and canonicalization,
-plus bounded D&D diagnostics. The
-D&D scene chunker and spell, NPC, combat-turn, item-event, NPC-interaction, and scene-description extractors use ordered
-package-local prompt manifests for both rendering and prompt fingerprinting, so
-only the shared fragments each prompt actually renders participate in either
-operation. Extraction prompts place stable shared and lane-specific context
-before the variable transcript and use shared assets for wording common across
-lanes. The canonical ordering and cache-boundary policy is documented in
-[LLM Runtime](llm.md#dd-extraction-prompt-ordering-and-cache-boundaries). Stage
-contracts expose only Notarius structured-completion types, not Scriptorium
-public types.
-
-The shared `PrepareChunkExtraction` helper owns common extraction preflight and
-transcript material preparation for the spell, NPC, combat-turn, item-event,
-NPC-interaction, and scene-description extractors. It validates common request
-state, clones supplied source metadata, falls back to the materialized chunk
-when content is absent, checks that content remains chunk-identical, and fills
-only the common default fields. Extractors retain receiver, dependency, and
-lane-specific checks locally and wrap helper errors with their module context.
-
-Reference material may inform a module or prompt but must not become source
-evidence. The resolver and materializer behavior is described in
-[Pipeline Internals](pipeline.md#reference-materialization).
-
-## Domain Reference Data
-
-### `internal/modules/dnd/spells/catalog`
-
-The spell catalog package owns the embedded, versioned D&D 5e 2014 SRD spell
-reference data. Its strict JSON asset contains one canonical record per spell,
-including spell level and all applicable class memberships. `LoadSRD5E2014`
-validates catalog identity, provenance metadata, ordering, uniqueness, levels,
-classes, aliases, and lookup-key collisions before exposing immutable copies.
-
-Lookup is case-insensitive and normalizes whitespace and common apostrophe
-variants while preserving source punctuation in canonical display names. The
-catalog contains 319 unique spells and 779 class memberships. Source and
-license details live beside the asset in `SOURCES.md`. This domain-owned data is
-separate from `internal/modules/dnd/shared`, which is reserved for reusable
-prompt and source-reference machinery.
-
-`ResolveEffectiveCatalog` builds the immutable recognition view used by the
-spell extractor and catalog validator. It starts with the embedded SRD catalog
-and optionally applies one strict JSON overlay from the `spell_catalog` item in
-a materialized reference set. Overlay catalogs are ordered by ID, may add names
-and aliases, and may augment an existing canonical spell without replacing its
-display name. Cross-spell lookup collisions are errors. The effective view
-exposes sorted canonical names, normalized lookup, overlay identities, and a
-semantic digest; overlay content remains contextual reference material rather
-than source evidence. Its external JSON contract is defined in the
-[spell-catalog overlay contract](../integrations/dnd-spell-catalog-overlays.md).
-
-### `internal/modules/dnd/npcs/identity`, `internal/modules/dnd/npcs/registry`, and `internal/modules/dnd/codec/npcs`
-
-The NPC identity package owns Unicode comparison keys, deterministic
-`npc:sha256:` IDs, display normalization, and whole-registry collision issues.
-The registry package resolves one optional normalized artifact through the
-strict codec, validates whole-registry identity, canonicalizes its JSON, and
-provides immutable records, a names-only prompt projection, distinct durable
-and projection digests, count, and exact canonical-name lookup. External files cross this boundary during
-preparation; generated artifacts cross it at the ordered step handoff. It owns
-the `npcs` slot and its bounded, content-safe validation failures. NPC source
-references are durable provenance and are not treated as evidence for a
-consuming pipeline. The NPC codec owns the strict durable `dnd/npc-list` JSON
-boundary and exposes candidate versus approved encode/decode operations. The
-shared `internal/modules/dnd/codec/candidatejson` package supplies strict typed
-candidate JSON mechanics; each artifact codec retains its own durable schema
-and approved-value policy.
-
-### `internal/modules/dnd/scenedescriptions/registry`
-
-The scene-description registry owns the required `scene_descriptions` control
-reference used by combat extraction. It decodes exactly one approved scene-list
-artifact through the scene-description codec and retains only scene ID, exact
-source reference, and kind. Titles, summaries, original bytes, paths, and
-prompt material do not cross this domain boundary.
-
-An external reference is validated during preparation; an unbound seed is
-permitted only while a configured generated reference awaits the ordered
-handoff. At operation time, a generated artifact overrides the seed and is
-resolved into an immutable view safe for concurrent extract jobs. Matching is
-strictly exact by chunk ID, source ID, start unit ID, and end unit ID, producing
-an exact, missing, or mismatched result. Only an exact result exposes kind.
-
-The registry's semantic eligibility digest is derived from a sorted projection
-of ID, exact range, and kind. It ignores titles, summaries, and input order;
-the unbound view has a stable empty projection digest. Combat extractor
-metadata and checkpoint identity use this semantic boundary for external
-references, while generated artifact identity and dependencies remain owned by
-the framework handoff.
-
-The `internal/modules/dnd/codec/combatturns` package owns the durable
-`dnd/combat-turn-list` schema and candidate versus approved JSON boundary. It
-is registered by the production D&D family registrar for the selectable combat
-lane.
-
-The `internal/modules/dnd/codec/itemevents` package owns the durable
-`dnd/item-event-list` schema and candidate versus approved JSON boundary. It is
-registered by the production D&D family registrar. Its external contract is
-defined in the [D&D item-event artifact contract](../integrations/dnd-item-event-artifacts.md).
-
-The `internal/modules/dnd/codec/npcinteractions` package owns the durable
-`dnd/npc-interaction-list` schema and candidate versus approved JSON boundary.
-It is registered by the production D&D family registrar for the selectable
-interaction lane. Its external contract is documented in the
-[D&D NPC interaction artifact contract](../integrations/dnd-npc-interaction-artifacts.md).
-
-The `internal/modules/dnd/codec/scenedescriptions` package owns the durable
-`dnd/scene-description-list` schema and candidate versus approved JSON boundary.
-It is registered by the production D&D family registrar. Its external contract
-is documented in the
-[D&D scene-description artifact contract](../integrations/dnd-scene-description-artifacts.md).
-
-## Input Adapter
-
-### `internal/modules/seriatim/input/transcript`
-
-The adapter decodes the supported transcript JSON, selects the source identity,
-computes canonical source provenance, validates segments, and maps each segment
-into a generic source unit with a self-reference plus speaker and timestamp
-metadata. It accepts no module options. Its spec advertises the transcript
-capabilities consumed by D&D modules.
-
-Parsing is strict about required values and duplicate unit IDs but deliberately
-ignores unrelated Seriatim fields. The external format and derived-identity
-rules are defined in the
-[Seriatim contract](../integrations/seriatim.md).
-
-## Chunkers
-
-Chunkers implement `contracts.Chunker.Plan`. A plan identifies ordered source
-unit ranges and may carry optional namespaced JSON annotations; it does not
-contain materialized chunk content. The framework canonicalizes annotations,
-validates ranges against the current source, and materializes chunk IDs,
-indexes, references, content, units, and generic metadata. Materialized source
-unit metadata is independently owned. Annotation
-namespaces remain optional data: generic framework code and downstream modules
-must not require D&D scene annotations or import `dnd/scenes`.
-
-### `internal/modules/generic/chunk/units`
-
-The generic chunker validates the source document and returns ranges over units
-in configured windows. Overlap changes the next window start but never reorders
-units. Framework materialization derives the resulting chunk identity and
-generic metadata from those ranges.
-
-The accepted options and defaults are defined in
-[Configuration](../config.md#implemented-production-modules). Generic
-framework validation canonicalizes the returned unit slices before extraction.
-The chunker decodes its options during construction and retains only the typed
-window settings used by `Plan`.
-
-### `internal/modules/dnd/chunk/scenes`
-
-The scene chunker prepares a structured Scriptorium request from the full
-transcript, session, and optional D&D reference inputs. It validates the model's
-inclusive source-unit endpoints against document position and converts them
-into deterministic plan ranges. Preparation injects the shared structured LLM
-client into the chunker; `Plan` supplies only the run-specific profile, session,
-source, references, and metadata.
-
-Scene validation requires sequential, contiguous, non-overlapping coverage from
-the first source unit through the last. Its private response contains only the
-boundary endpoints; the accepted plan has no D&D-specific annotations and
-produces no boundary warnings. Malformed structured output is returned as an
-error; there is no fallback chunker.
-
-The package embeds its prompt and response schema and reports their non-secret
-identity and hashes through singleton module metadata. Shared D&D assets supply
-reference declarations and prompt inputs; their user-facing keys and accepted
-file types remain canonical in [Configuration](../config.md).
-
-## Extractor
-
-### `internal/modules/dnd/extract/spells`
-
-The spell extractor prepares a structured request from one chunk, the
-chunk-scoped source input, the session, and optional D&D reference inputs. It
-decodes the model response, assigns the generic source identity to every source
-reference, canonicalizes duplicate references, orders spell casts by their
-earliest valid source-document position, and returns `dnd.SpellList`.
-
-Its private response schema admits only the structural transport envelope:
-required fields, JSON types, array and object shapes, and unknown-field
-rejection. It maps integer source-unit candidates directly without repairing
-semantic values, so the deterministic shape, catalog, and source-reference
-validators own blank values, empty evidence, and invalid or unresolved ranges.
-
-The extractor owns its private model-response DTO, embedded prompt, LLM response
-schema, strict option decoder, injected shared LLM client, and prompt/schema
-manifest metadata. During preparation it resolves the optional `spell_catalog`
-reference into an immutable effective catalog and adds a generated
-canonical-name-only JSON input to every structured completion request. Overlay
-failures therefore stop construction before source parsing or an LLM call;
-campaign references remain separate disambiguation inputs and never become
-source evidence.
-
-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
-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
-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.
-
-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. 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":[]}` 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.
-
-The durable payload and manifest metadata shapes are defined in the
-[D&D spell artifact contract](../integrations/dnd-spell-artifacts.md).
-
-### `internal/modules/dnd/extract/npcs`
-
-The NPC extractor maps private model output to the canonical `dnd.NPCList`,
-assigns source identity and deterministic NPC IDs, and preserves source
-references for deterministic validation. It uses the shared campaign
-references only for disambiguation and does not consume the optional NPC
-registry slot. Its prompt and private response schema are package-owned. The
-private response contains only a name and model-facing evidence ranges for each
-record; anonymous groups, generic roles, invented labels, descriptions,
-aliases, and relationships are outside its contract. The
-prompt follows the shared D&D extraction ordering and cache policy documented
-in [LLM Runtime](llm.md#dd-extraction-prompt-ordering-and-cache-boundaries).
-
-The private response schema owns only structural transport validation and maps
-integer source-unit candidates unchanged. Required semantic content, non-empty
-evidence, and valid source ranges are rejected by the deterministic shape and
-source-reference validators.
-
-### `internal/modules/dnd/extract/scenedescriptions`
-
-The scene-description extractor makes one structured completion for each
-accepted chunk and maps its private `kind`, `title`, and `summary` response to
-one `dnd.SceneDescription`. It assigns the current chunk ID and exact range,
-preserves kind without repair, and trims only title and summary whitespace.
-Optional players, party, and glossary references can disambiguate prompt terms
-but do not supply evidence. The package owns its private schema, prompt assets,
-and mapping fingerprint; deterministic validators own the durable semantic
-checks. The durable contract is defined in the
-[D&D scene-description artifact contract](../integrations/dnd-scene-description-artifacts.md).
-
-### `internal/modules/dnd/extract/combatturns`
-
-The combat extractor requires the `scene_descriptions` reference and resolves
-it through the immutable scene-description registry before it resolves NPC
-grounding or constructs prompt inputs. It calls the LLM only for an exact
-current-chunk match whose kind is `combat`. Exact `narrative`, `recap`, and
-`meta` matches return an accepted empty `dnd.CombatTurnList`; missing or
-mismatched coverage returns the same result with one bounded unavailable-
-classification warning. These deterministic results do not consume retry
-attempts. Scene descriptions are control context only and are not passed to the
-combat prompt or copied into combat evidence.
-
-For eligible chunks, the extractor prepares one structured request using the
-shared extraction-evidence, identity, campaign-reference, NPC-grounding, and
-transcript prompt inputs. It maps the private response to
-`dnd.CombatTurnList`, assigns the current source identity, removes exact
-duplicate source ranges, and orders turns by valid source-document position
-while preserving malformed candidate fields for deterministic validators. Its
-package-owned private response schema enforces only the structural JSON
-envelope; semantic artifact constraints remain with the validator chain.
-
-Prepared metadata and checkpoint fingerprints include prompt, response-schema,
-mapping, and scene-gate identities. An external scene reference additionally
-reports its semantic eligibility digest and count; generated identity remains
-framework handoff provenance and dependency state. Neither surface retains
-scene prose or payload bytes. The prompt follows the shared D&D extraction
-ordering and cache policy documented in
-[LLM Runtime](llm.md#dd-extraction-prompt-ordering-and-cache-boundaries). The
-package exposes typed registration and is included in the production D&D
-registrar with the default combat extraction chain.
-
-The combat normalizer accepts only the optional structured NPC registry.
-Campaign references remain extractor-only LLM context and are not materialized
-for deterministic normalization.
-
-### `internal/modules/dnd/extract/itemevents`
-
-The item-event extractor prepares one structured request from the accepted
-chunk and optional campaign references, then maps private records to
-`dnd.ItemEventList` with the current source identity. It declares only optional
-`glossary`, `party`, `players`, and deprecated `roster` reference slots; these
-can disambiguate names but never supply evidence. It has no NPC,
-scene-description, or item-registry dependency.
-
-The private response schema owns structural transport validation. The extractor
-preserves candidate category, holder, quantity, and source-range values for the
-deterministic validators, removes exact duplicate ranges, and source-orders
-events. The source-reference validator requires citations to fit the current
-accepted chunk. Prompt, response-schema, and mapping identities participate in
-checkpoint identity. The durable schema is owned separately by
-`internal/modules/dnd/codec/itemevents`.
-
-### `internal/modules/dnd/extract/npcinteractions`
-
-The NPC interaction extractor requires the structured `npcs` registry slot. It
-uses the registry's names-only prompt projection with shared extraction
-evidence, identity, and transcript material, then maps private model records to
-`dnd.NPCInteractionList` with the current source identity. Registry source
-references are never reused as interaction evidence. The private response
-schema carries only name, bounded interaction kind, and source-unit ranges;
-deterministic validators own registry membership, source validity, and
-relatedness. Extract-stage source validation additionally requires every cited
-range to be wholly contained in the current materialized chunk. Prompt, schema,
-mapping, and the names-only registry projection
-participate in checkpoint identity, while generated producer identity remains
-framework provenance.
-
-The shared D&D source-reference order defines canonical evidence ordering. The
-domain-owned `internal/modules/dnd/npcinteractions` package defines occurrence
-ordering, valid-evidence eligibility, and collision-safe exact identity. The
-interaction normalizer and normalized invariants validator consume those
-rules, so their production and checking paths cannot drift. Normalizer and
-relatedness warning lists use the shared D&D diagnostic cap and emit a final
-omission-summary warning when truncated.
-
-### `internal/modules/dnd/normalize/npcs`
-
-The NPC normalizer deterministically trims display names, recomputes IDs,
-canonicalizes evidence, and consolidates equal comparison keys before semantic
-work. Records are eligible for the document-level identity call only when they
-have a non-empty comparison key and wholly valid current-document references.
-It sends private candidate names and source ranges plus coalesced, cited
-transcript windows to its own prompt; stable NPC IDs and the durable artifact
-shape are not prompt inputs.
-
-The private structured response proposes groups of supplied names and a
-canonical supplied name. Deterministic comparison-key resolution validates each
-group, discards unsafe or overlapping groups, and independently applies safe
-ones. Application preserves earliest record order, unions canonical evidence,
-and derives the final canonical ID. Invalid structured output and discarded
-groups request framework retry with a safe fallback; bounded diagnostics become
-durable only on final fallback exhaustion.
-
-The normalizer records prompt and response-schema identities and digests,
-identity and normalization policies, and semantic-context policy and radius as
-manifest metadata. Its local checkpoint fingerprints cover the prompt, response
-schema, identity policy, normalization policy, and semantic-context policy so a
-meaningful behavior change invalidates prior normalize reuse.
-
-## Merger And Normalizer
-
-### `internal/modules/generic/merge/appendorder`
-
-The merger passes typed values to an injected combine function in framework
-source-chunk order. The D&D registrar specializes it for all six artifact
-lists; each append merger preserves collection presence and order while giving
-the result independently owned nested source-reference slices.
-
-### `internal/modules/generic/normalize/noop`
-
-The normalizer returns the merged domain value unchanged and is reusable for
-any registered artifact type.
-
-### `internal/modules/dnd/normalize/spells`
-
-The typed spell normalizer resolves the optional `spell_catalog` reference into
-the same immutable SRD-plus-overlay effective catalog used by spell extraction
-and catalog validation. It performs no LLM calls. For each spell cast it
-canonicalizes recognized names using the catalog's case, whitespace,
-apostrophe, and alias rules; canonicalizes source references with the shared
-document-aware order; removes only exact reference duplicates; and emits
-bounded, 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,
-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,
-and overlay IDs as manifest metadata. Catalog contents, reference paths, and
-raw overlay bytes are not included in either surface. The normalize-stage
-reference is stage-local, so an overlay-capable pipeline binds the catalog
-independently for extraction and normalization.
-
-### `internal/modules/dnd/normalize/combatturns`
-
-The combat normalizer prepares an external NPC registry before execution or
-receives a generated registry at the ordered step handoff, then uses the
-immutable view during runtime. It display-normalizes actors,
-rewrites canonical-name matches for actors, orders and deduplicates source
-references, stable-sorts records by source-document position, and collapses
-only exact duplicate identities with fully valid evidence. It deep-clones
-output storage and emits bounded warnings scoped to merged input indexes. Its
-metadata and fingerprints identify the normalization and NPC identity policies.
-External bindings may contribute registry
-digest/count metadata; generated identity is retained in framework provenance
-and dependency fingerprints. The normalizer is included in the production D&D
-registrar with the default combat normalization chain.
-
-### `internal/modules/dnd/normalize/itemevents`
-
-The item-event normalizer accepts no options or references and makes no LLM
-calls. It trims display-edge whitespace in names and holders, canonicalizes
-source references, source-orders events, and collapses only exact duplicates
-with complete valid evidence. It does not create a ledger, calculate balances,
-resolve aliases, infer quantities or holders, or reconcile nearby events. Its
-policy fingerprint and bounded warnings identify deterministic normalization;
-the matching invariant validator checks the resulting order and duplicate rule.
-
-### `internal/modules/dnd/normalize/npcinteractions`
-
-The interaction normalizer requires the same immutable NPC registry. It
-canonicalizes exact registry-name matches, orders and de-duplicates source
-references, stable-sorts occurrences by source-document position, and collapses
-only exact interaction identities with valid evidence. It does not infer,
-merge, or summarize distinct occurrences. Its metadata and fingerprints expose
-the normalization and NPC identity policies; generated registry identity stays
-in framework provenance and checkpoint dependencies.
-
-### `internal/modules/dnd/normalize/scenedescriptions`
-
-The scene-description normalizer has no options or references. It validates
-each source range against the source document, trims title and summary
-whitespace, orders records by source position then ID, removes only exactly
-identical records, and rejects conflicting reused IDs or ranges. Its policy
-fingerprint identifies this deterministic behavior; the matching invariant
-validator checks the normalized result in the production chain.
-
-## Output Encoder
-
-### `internal/modules/generic/output/json`
-
-The JSON encoder sorts normalized results by lane, derives collision-checked
-safe logical names, pretty-prints JSON payloads, and assembles the logical index,
-manifest, rejected-result, warning, and lane files. Invalid JSON, unsupported
-media types, unsafe names, and sanitized-name collisions are errors.
-
-Its strict `include_chunk_map` option is disabled by default. When enabled, it
-validates the framework-supplied accepted chunk map through its codec and adds
-the pipeline-wide `chunk-map.json` plus its index descriptor; it does not treat
-the map as a lane payload. The external shape is owned by the
-[Accepted Chunk Map contract](../integrations/chunk-map.md).
-
-The encoder returns logical files only. The CLI places them on disk, and the
-[JSON output contract](../integrations/json-output.md) defines their external
-paths and schemas.
-
-## Generic Validators
-
-The generic validator implementations live under
-`internal/modules/generic/validate`.
-
-The unconditional accept and reject validators provide explicit chunk and
-typed-artifact variants used primarily for controlled composition and tests.
-
-The serialized JSON syntax validator uses `encoding/json` to reject malformed
-representation bytes. The serialized JSON Schema validator requires schema
-bytes, parses the instance and schema with `jsonschema`, and distinguishes
-payload rejection from schema loading or compilation errors. The framework
-serialized-validation request carries either canonical chunk bytes or artifact
-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 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
-ranges through the shared document-order traversal, then warns when a normalized
-consecutive spell-name token sequence is absent from the cited source text.
-Invalid shape
-or cited ranges produce no relatedness warnings; the shape and source-reference
-validators own those defects.
-
-These validators are deterministic. Shape, source-reference, and relatedness
-each expose a local semantic `policy` checkpoint fingerprint. The catalog
-validator instead exposes its effective catalog digest as its semantic
-checkpoint identity and does not add a separate policy fingerprint. Their
-selectable keys and production order are defined in
-[Configuration](../config.md#implemented-production-validators); their durable
-payload rules are defined in the
-[artifact contract](../integrations/dnd-spell-artifacts.md).
-
-## D&D NPC Validators
-
-NPC shape validation checks the required ID and name strings, list presence, and source-reference
-shape. The source-reference validator defers malformed shapes, checks
-current-document identity, unit existence, and range ordering, and reports all
-defects through bounded aggregates. Source relatedness uses the shared
-document-order traversal and normalized consecutive-token matching, emitting at
-most one bounded warning per record when the canonical name does not occur near
-its cited text. Invalid shape or cited ranges produce no relatedness warnings.
-Normalize identity validation checks deterministic IDs, canonical names, and
-duplicate canonical-name or ID ownership.
-All are deterministic and expose the policy fingerprints used by the
-production chains.
-
-## D&D Combat Validators
-
-Combat shape validation owns the required list, actor, supported turn kind, and
-non-empty source-reference collection. Combat source-reference validation defers invalid
-shape, checks source identity, unit existence, and range order, and reports all
-defects through bounded aggregates. Combat source-relatedness defers invalid
-shape or ranges, uses the shared traversal to combine overlapping cited units
-in document order, and emits at most one bounded advisory warning per turn for
-an unrelated actor. Actors use normalized consecutive-token matching. The
-normalized-invariants validator owns actor display normalization, canonical
-source-reference order, chronology, and exact duplicate identity; it defers
-shape and source-reference failures. All four validators are deterministic and
-expose local policy fingerprints. In the registered defaults, JSON syntax runs
-first; combat shape, normalized invariants when applicable, and source-reference
-validation precede JSON Schema validation; warning-only relatedness runs last.
-
-## D&D Item-Event Validators
-
-Item-event shape validation owns the required list, non-empty name, supported
-category, category-and-holder combination, positive optional quantity, and
-non-empty source-reference collection. Source-reference validation defers
-malformed shapes, checks current-source identity and ordered ranges, and during
-extraction requires every citation to fit the accepted chunk. Relatedness is
-advisory and warning-only: it checks the event name against cited transcript
-text while deferring malformed candidates and invalid ranges to their blocking
-owners. The normalized-invariants validator owns display normalization,
-canonical source-reference order, chronology, and exact duplicate identity.
-All four validators are deterministic and expose policy fingerprints. The
-registered chains run syntax and blocking checks before durable JSON Schema;
-relatedness remains last.
-
-## D&D NPC Interaction Validators
-
-Interaction shape validation owns the required list, registry name, supported
-kind, and non-empty source-reference collection. Registry validation checks
-exact membership in the required immutable NPC registry. Source-reference and
-relatedness validation use the current transcript only; malformed candidates
-are deferred by later validators and produce no relatedness warning. The
-normalized-invariants validator owns canonical registry names, source-reference
-order, chronology, and exact duplicate identity. The production chains run
-shape, registry, and source-reference checks before JSON Schema validation;
-relatedness remains warning-only and last.
-
-## D&D Scene Description Validators
-
-Scene-description shape validation owns the non-empty list, trimmed ID and
-prose, closed kind, and basic source-reference shape. Extract-stage source
-validation additionally requires the one record to attach exactly to the
-current accepted chunk; later source validation checks source membership.
-Relatedness checks the title and summary independently against only their cited
-transcript range and emits bounded advisory warnings. The normalized-invariants
-validator owns ordering, exact duplicate elimination, and conflicting ID or
-range detection. The production chains run shape and source-reference checks
-before JSON Schema validation; the warning-only relatedness check is last.
-
-## Production Registration
-
-Production composition occurs through family registrars. The CLI allocates one
-complete framework registry set and one LLM asset registry. It invokes
-`internal/modules/generic/register`,
-`internal/modules/seriatim/register`, and `internal/modules/dnd/register` in
-that order, then exposes the matching catalog for resolution. The generic and
-Seriatim registrars own their production leaf registrations. The D&D registrar
-owns D&D leaf registrations, typed spell, NPC, combat, item-event, interaction, and scene-description default-validator
-chains, typed append-order specializations, and D&D prompt/schema asset
-collection. Its registration helpers group module, validator, prompt-asset, and
-chain composition while retaining artifact-specific merge and clone behavior in
-the registrar.
-
-Concrete implementation packages do not import generic implementation
-packages directly. A concrete family's `register` package is its composition
-point for specializing reusable generic implementations, while the generic
-registrar composes only generic children.
-
-Core and framework production packages do not import production extensions.
-CLI production code is the sole application composition root for extensions
-and imports only exact family registrar packages. Other production packages,
-including commands and newly introduced package trees, do not import module
-packages directly. Compatibility tests in the CLI, core, and framework trees
-may import roots and implementation leaves directly. Other non-module tests do
-not receive that exemption. White-box tests within module families retain the
-production family boundaries. `internal/modules/integration` is test
-infrastructure: its black-box tests may compose multiple families, but it is
-not a production module family or production dependency target.
-
-## Adding An Extension
-
-When adding a production module or validator:
-
-1. implement the stage or validator contract and package-local key;
-2. expose and test its spec, constructor, and registration function;
-3. keep format or domain parsing inside the concrete package;
-4. add package-owned prompt/schema assets when the extension is LLM-backed;
-   new LLM-backed D&D extraction modules must follow the stable-to-variable
-   prompt ordering, shared-asset ownership, and cache-boundary policy in
-   [LLM Runtime](llm.md#dd-extraction-prompt-ordering-and-cache-boundaries), or
-   document the implemented exception and its evidence there;
-5. register it through its package-family registrar and add a default chain
-   there only when production policy requires one;
-6. add resolution and composition coverage for capabilities, options,
-   references, and validation behavior;
-7. update the selectable-key catalog in [Configuration](../config.md), the
-   relevant external contract, this inventory, and maintained examples when
-   user-visible behavior changes.
-
-Do not add the extension to `docs/development.md`; that file routes by task and
-does not inventory implementations.
-
-### D&D Extractor Contract
-
-New D&D extractors preserve these package-owned responsibilities:
-
-- Reject unknown options unless an option namespace is intentionally
-  extensible, and use shared common preflight while retaining receiver,
-  dependency, and lane-specific checks locally.
-- Return independently owned results and exposed metadata that callers may
-  safely mutate.
-- Keep the private response DTO, structural response schema and its identity,
-  provider-response mapping, durable artifact conversion, and lane diagnostics
-  in the owning package.
-- Include every stable semantic input that can change durable output in
-  checkpoint identity. Consider prompt, schema, mapping, canonicalization,
-  prepared reference projections, identity, normalization, and trimming where
-  applicable.
-- Add focused behavioral coverage where the lane's risks warrant it, including
-  construction and registration, option rejection, preflight, provider
-  failures, structured decoding, mapping and ownership, prompt
-  role/input/cache order, and checkpoint invalidation.
-
-Prompt ordering, shared-asset ownership, cache boundaries, and private-schema
-rules are defined in [LLM Runtime](llm.md#dd-extraction-prompt-ordering-and-cache-boundaries).
-[Pipeline Internals](pipeline.md#reference-materialization) owns reference
-materialization, and its [checkpoint hooks](pipeline.md#checkpoint-and-debug-hooks)
-define checkpoint behavior. Follow [Architecture](../policy/architecture.md#source-and-domain-boundaries)
-for ownership boundaries and the [Testing Policy](../policy/testing.md) when
-selecting durable coverage. This contract intentionally does not prescribe
-prompt prose or length, hashes, test counts, filenames, fixture layouts, or
-generic implementation builders.
-
-## Tests To Inspect
-
-- Package-local `*_test.go` files under the module or validator being changed.
-- `internal/framework/pipeline/typed_resolution_test.go`: typed registry, spec,
-  and heterogeneous artifact composition.
-- `internal/framework/pipeline/profile_test.go`: framework binding defaults and
-  profile resolution.
-- `internal/cli/production_contract_test.go`: production catalog, config
-  resolution, and composition smoke coverage.
-- `internal/cli/example_contract_test.go`: maintained example ownership.
-- `internal/framework/promptfs/*_test.go` and
-  `internal/modules/dnd/shared/*_test.go`: shared prompt and reference assembly.
-- `internal/modules/integration/*_test.go`: black-box composition across
-  production extension domains.
+# Module Internals
+
+This guide owns the mechanics for implementing and registering production
+modules. [Configuration](../config.md) owns selectable keys, binding syntax,
+reference configuration, and default validator chains. Durable input and output
+shapes belong in [integration contracts](../integrations/).
+
+The D&D family has additional shared conventions and domain-specific
+exceptions. See [D&D Module Internals](dnd.md) rather than adding them here.
+
+## Module Boundary
+
+A module is a typed implementation registered for one pipeline stage. Its
+`ModuleSpec` is the public-to-the-framework declaration of its stable key,
+stage, execution class, required and provided capabilities, artifact kind, and
+accepted reference slots. The execution class states whether a module is
+`deterministic` or `llm_backed`; registries retain it for catalog inspection and
+resolved-pipeline debug data without constructing the module. The framework
+uses the declaration to resolve a configured binding before it builds the
+implementation. After selection, the resolver applies profile inheritance only
+to bindings whose declared execution class is `llm_backed` and rejects a
+binding-specific profile on a deterministic module. The user-facing precedence
+contract belongs in [Configuration](../config.md#pipelines).
+
+An eligible LLM-backed chunk, extract, merge, or normalize producer may also
+declare correction protocol `single_response_v1`. That declaration is a
+promise that the implementation accepts one attempt-local semantic correction
+and returns an owned copy of the exact one model response that directly
+controlled the candidate. It must forward correction only to its structured
+completion request; it must not manufacture prior-response material by
+serializing a normalized artifact or expose opaque application IDs. Input,
+output, validator, and deterministic specs cannot declare the protocol.
+
+Implementations that accept options must provide both an option validator and
+a builder. The validator is used while resolving configuration; the builder
+decodes the same options and constructs the implementation from the prepared
+`BuildRequest`. Reject unknown options in both paths. A builder receives only
+the dependencies and materialized references that the framework prepared for
+that operation, so it must not re-read configuration or files.
+
+Registry helpers register the typed builder for a stage-specific registry.
+They are preferable to hand-written untyped registration because they retain
+the artifact type at the framework boundary. Registrars validate the registries
+they need, register each leaf implementation, and add any family-owned assets
+or default validator chains. They return contextual errors so production
+composition fails at startup rather than at the first run.
+
+A validator that returns a completed rejection must supply two separate
+bounded values: a stable `ReasonCode` for provenance and actionable
+`CorrectionGuidance` for the producer. Guidance identifies the semantic defect
+and the constraints on one complete corrected replacement. It must not contain
+validator keys, diagnostic paths, opaque application IDs, or other internal
+identifiers. An operator-facing `Message` may explain the same event, but the
+framework never copies it into a model request. Missing or invalid guidance is
+a validator contract failure.
+
+An artifact family can register an optional typed evidence projector alongside
+its codec. The projector returns defensive copies of the artifact's direct
+generic source references and must use the codec's exact Go type. It does not
+interpret surrounding context or publish files; the pipeline validates the
+capability during preparation and the output boundary owns publication. See
+the [Published Evidence Context contract](../integrations/evidence-context.md)
+for the durable source-unit excerpt. Lane artifacts retain citation and lane
+provenance; the framework does not add either to that published excerpt.
+
+An artifact family is broader than a module: it owns the cohesive domain
+feature across its artifact type, codec, stage modules, validators, prompt
+policy, schemas, identity helpers, and reference projections. An extractor and
+normalizer in one artifact family remain independently registered modules in
+their respective pipeline stages. This ownership vocabulary does not create a
+new registry or change the fixed pipeline.
+
+## Production Composition
+
+Production composition is intentionally split by family:
+
+- The generic registrar provides the unit chunker, generic JSON validators,
+  JSON output encoder, and shared semantic-reconciliation prompt and response
+  schema assets.
+- The Seriatim registrar provides the transcript input adapter. Its external
+  input behavior is defined by the [Seriatim contract](../integrations/seriatim.md).
+- The D&D registrar provides its codecs, extractors, mergers, normalizers,
+  validators, prompt assets, fallback profile asset, and default chains. Its behavioral conventions
+  are documented in [D&D Module Internals](dnd.md).
+
+The CLI owns the composition that invokes these registrars. A module package
+may register its own family but must not assemble the CLI or make framework
+packages depend on production extensions.
+
+## Semantic Reconciliation
+
+`internal/framework/semanticreconcile` is a domain-neutral strategy used by a
+typed normalize module; it is not itself a selectable stage module. A
+source-backed artifact-family normalizer projects its deterministic records
+into contextual candidates and owned typed record envelopes, supplies its
+chosen prompt identity and resolved LLM profile, and constructs an engine with
+explicit limits. The core filters invalid evidence, assigns contiguous
+request-local integer handles, renders bounded candidate and transcript
+materials, invokes the structured-completion boundary, and assesses the
+returned duplicate groups into a stable non-overlapping plan.
+
+The normalizer then applies that plan through a typed `ApplicationPolicy`. The
+core preserves ungrouped records, contribution order, and provenance while the
+artifact family owns group guards, field and evidence consolidation, durable
+ID derivation, retry and fallback presentation, warnings, and postconditions.
+Request-local handles do not enter the typed value or durable artifact. Fewer
+than two eligible candidates skips model invocation; exceeding a candidate or
+combined-material bound preserves the deterministic result under the family's
+fallback policy. Provider, transport, cancellation, and context-construction
+failures remain execution errors.
+
+When the engine actually makes a proposal call, its typed result carries the
+owned exact proposal response under the same correction contract as other
+eligible producers. Deterministic skip, limit, and fallback outcomes carry no
+model candidate, so a later rejection applies terminal policy without spending
+an ineffective semantic retry.
+
+The core supplies a conservative generic prompt and the single private
+response schema. A domain prompt may substitute its semantic instructions but
+mounts the core-owned protocol and candidate/transcript presentation assets.
+Prompt, schema, policy, and limit identities participate in manifest metadata
+and checkpoint fingerprints. The generic registrar owns production
+registration of those shared assets; a consuming domain registrar owns only
+its domain prompt.
+
+## Adding Or Changing A Module
+
+1. Choose the pipeline stage and the typed artifact boundary. Put external
+   input or durable artifact formats in the relevant integration contract,
+   not in this guide or in a private LLM response type.
+2. Define a stable `ModuleSpec` with an explicit execution class, the exact
+   capabilities, and reference slots needed for the operation. Model a
+   producer/consumer handoff as an artifact-compatible slot; configuration
+   then chooses an external file or a generated binding.
+3. Implement strict option decoding, construction, and the typed stage
+   interface. Preserve caller ownership: do not retain mutable request data
+   and return defensive copies where an implementation exposes stored data.
+   If declaring correction capability, forward the request correction and
+   retain only the exact validated response that controlled the result.
+4. Register the module through its typed registry helper and add it to the
+   owning family registrar. Add a default validator chain only when that
+   family owns the behavior; otherwise require an explicit compatible chain.
+   Every rejection path in a validator must provide actionable correction
+   guidance while retaining its stable internal reason code.
+5. Update the selectable-key and chain reference in
+   [Configuration](../config.md#production-module-keys), the applicable
+   integration contract, and focused tests. Keep the configuration document
+   as the sole list of production keys and validator order.
+
+## Validation And References
+
+Validators operate on the value produced at their configured stage. A default
+chain is ordered behavior, not a set: JSON parsing, structural checks,
+domain-specific checks, durable-schema checks, and advisory checks may have
+different responsibilities and failure handling. The active default chains and
+override rules are maintained in
+[Configuration](../config.md#production-validator-keys-and-default-chains).
+
+Reference slots are part of the module specification. They describe the
+accepted artifact kind, media type, size, and whether a binding is required;
+the framework validates those constraints before construction. An external
+reference is materialized during preparation. A generated reference is a
+compatible normalized artifact handed from an earlier pipeline step at
+operation time. The configuration reference rules, including precedence and
+ordered-handoff requirements, are maintained in
+[Configuration](../config.md#references-and-ordered-handoffs).
+
+## Focused Verification
+
+Exercise the leaf implementation and its registration path when changing a
+module. Registry and registrar tests cover duplicate keys, required registries,
+and typed construction; pipeline resolution tests cover capabilities, options,
+and reference compatibility. Domain packages should additionally test their
+codecs, validators, normalizers, and any integration handoffs they own.
+
+Run the affected package tests while iterating. The complete module suite is:
+
+~~~sh
+go test ./internal/modules/...
+~~~