narrator-decisions

name	narrator-decisions
description	Produces RUN-DECISIONS.md by filtering decision-candidate turns into real multi-alternative decisions.
output	json
inputs	["incremental_jsonl","trace_jsonl","diff_samples"]

narrator-decisions

You are writing the decisions artifact for a deadreckon run.

Return exactly one JSON object:

{
  "design_decisions": "Markdown for choices made where the spec was ambiguous, or None.",
  "deviations": "Markdown for intentional departures from the spec and why, or None.",
  "tradeoffs": "Markdown for alternatives considered and why the chosen path won, or None.",
  "open_questions": "Markdown for anything the owner should confirm or revise, or None.",
  "decisions": [
    {
      "title": "short title",
      "turn": 1,
      "considered": ["alternative"],
      "chosen": "choice",
      "why": "reason with evidence",
      "files_affected": ["path"],
      "citations": ["[turn 1](../traces.jsonl#turn-1)"]
    }
  ]
}

Return the four implementation interpretation fields even when no real multi-alternative decision appears. In that case use "decisions": []; the binary will place the no-decisions sentence under Multi-alternative decision details.

Inputs

• Incremental turn records:

{{ incremental_jsonl }}

• Trace JSONL:

{{ trace_jsonl }}

• Diff samples:

{{ diff_samples }}

• Live implementation notes:

{{ implementation_notes }}

Requirements

• Treat implementation-notes.html as source evidence for design_decisions, deviations, tradeoffs, and open_questions.
• Inspect only turns with decision_candidate: true; filter false positives.
• A real decision must include alternatives considered, the chosen path, why it was chosen, files affected, and citations.
• files_affected must name only documentable user-authored source, config, manifest, test, asset, or project-doc files.
• Omit generated/vendor/cache/build-output/local-secret paths such as .next/, .astro/, .output/, node_modules/, .venv/, .gradle/, CMakeFiles/, .dart_tool/, .terraform/, dist/, build/, target/, .turbo/, .cache/, source maps, .env*, traces, snapshots, and run artifacts.
• Do not invent decisions from ordinary implementation summaries.
• Do not turn every implementation note into a multi-alternative decisions entry. The notes feed the four interpretation fields; the decisions array remains evidence-filtered.
• If the evidence is ambiguous, omit the entry rather than overstate it.