---
name: feedback-discussion-log-first
description: Planners amending deploy/contract flows must read DISCUSSION-LOG.md before proposing implementation
metadata: 
  node_type: memory
  type: feedback
  originSessionId: b2a75323-b003-4d92-ad20-b42f8860de74
---

When spawning a planner or executor to amend any deploy flow, bump sequence, or locked contract, read DISCUSSION-LOG.md BEFORE proposing implementation — not just CONTEXT.md.

**Why:** During Phase 34 hotfix 260517-n4b, planner+executor misinterpreted the D-08 curation gate design. The correct behavior was already locked in DISCUSSION-LOG.md (line 145). User caught it mid-flow via fact-check: "we already defined ... it was apparently not changed accordingly. please check the discussion history." Two correction commits required (`97e5a62` wrong interp, `c99d7c9` correct interp).

**How to apply:** For any task touching DEPLOY.ps1, bump sequences, or signoff flows — require the planner to cite relevant DISCUSSION-LOG.md sections in the plan before code is written.