Plan D&D scene description extraction

docs/roadmap/future.md

@@ -18,27 +18,10 @@ not as committed release dates.
 
 ### Extract D&D Scene Descriptions
 
-- Add a `dnd/scene-descriptions` extractor that runs once for each accepted
-  scene chunk and explicitly owns the small amount of scene synthesis useful to
-  downstream applications.
-- Keep the private model response to exactly `kind`, `title`, and `summary`.
-  Use the enum `combat`, `narrative`, `recap`, and `meta`: `narrative` means
-  current-session in-world gameplay that is not combat, recap, or sustained
-  out-of-character discussion.
-- Treat brief table talk or rules clarification as incidental to the enclosing
-  gameplay scene. A sustained transition between kinds should normally create
-  a chunk boundary; define a primary-kind rule for residual mixed chunks before
-  implementation.
-- Deterministically attach the accepted chunk ID and its exact source range
-  while mapping the private response into the durable artifact. Do not ask the
-  model to reproduce IDs or segment boundaries, and do not defer required
-  identity or evidence until normalization.
-- Keep normalization limited to stable ordering, exact deduplication, and
-  canonical invariant enforcement. Titles and summaries are explicit,
-  source-bounded synthesis owned by this artifact rather than by the chunker.
-- Do not add `participants`. Derive participant-oriented views by joining scene
-  ranges with NPC evidence or, preferably, NPC-interaction occurrences. An NPC
-  registry reference proves identity, not exhaustive presence in every scene.
+Add one minimal, source-bounded description for each accepted D&D scene chunk.
+The proposed durable contract, scene-kind policy, evidence boundary, and
+relationship to later chunker minimization are defined in
+[D&D Scene Descriptions](dnd-scene-descriptions.md).
 
 ### Minimize And Use D&D Scene Chunking