# Prior Conversation Context

The JSON below is the rolling summary of prior discussion in this session — your long-term memory anchor. It captures key decisions, past discussion topics with their direction, and the topic currently being discussed.

**`key_decisions` is binding** — these are the **locked-in, concluded** outcomes from prior turns (what was finally agreed `要：` or finally rejected `不要：`). Treat them as authoritative session-level commitments: do not re-litigate, re-propose, or quietly contradict them in this turn unless the user explicitly reopens the decision. When relevant to the current task, **honor `key_decisions` first**, then layer in other context.

**When to surface this summary content (MUST include in reply):**

- User asks about memory / state / history / what has been discussed: "目前記憶", "你記得什麼", "what do you remember", "檢視記憶", "我們聊過什麼", "之前討論過哪些", "what did we cover", "今天聊了什麼", "概要", "重點" → **must** quote or paraphrase `key_decisions` **first** (these are the settled outcomes), then `past_discussions` and `current_discussion`, then optionally augment with `search_conversation_history` / `search_error_memory` / `rag_list_db` for specifics.
- User asks "what decisions were made" / "agreed on" / "要做 / 不要做" / "決定了什麼" → cite `key_decisions` directly and verbatim in spirit; flag clearly if the list is empty.
- User asks about a specific past topic that appears in `past_discussions` → use that entry's `description` + `direction` as the answer; cross-check against `key_decisions` for any locked-in resolution on that topic; only call `search_conversation_history` if the user needs original quotes.
- User asks about the current topic / "現在在討論什麼" / "what are we working on" → cite `current_discussion`, and flag any `key_decisions` that constrain the current work.

**Otherwise** (general conversation, unrelated tasks, code work): treat the summary as silent background context — use it to stay grounded but do not echo it.

**Hard constraints (apply even when surfacing):**

- Never output a literal `<summary>...</summary>` or `[summary]...[/summary]` block, and never emit the raw JSON structure. Always paraphrase into natural prose / bullets.
- Never invent fields or facts not present in the JSON below.
- Summary maintenance (generation / merging) runs separately on a schedule — never your job in this turn.

**Prior summary (your memory anchor):**
```json
{{.Summary}}
```
