01//DefinitionTerm

// ##decision-def =Decision Log — a personal record of a conclusion or commitment made while reading, attached to a specific line. .Captures the outcome of deliberation: "I will use X", "I reject Y", "This changes my approach". .Acts as a commitment device — once written, harder to ignore. →Transforms passive reading into active decision‑making.

---

02//MechanismHow it works

// ##decision-mech ~Select text → right‑click → "Decision" → enter your conclusion. ~The line gets a subtle background highlight (epi-decided). ~Decision is stored with timestamp and lineId in the trace panel. .Later, clicking the trace jumps to the line and briefly highlights it. +Unlike tags, decisions are longer‑form and represent a commitment.

---

03//Memory ConnectionWhy it sticks

// ##decision-memory →Enactment effect — performing an action (writing a decision) strengthens memory. →Commitment — stating a conclusion creates cognitive dissonance if not followed. →Episodic anchor — the decision becomes a unique event tied to that line. @episodic-memory.html — mental time travel

---

04//Implementation in CLNTechnical

// ##decision-impl +Store decisions in localStorage as part of episodic overlay: { type: "decision", decision: "...", lineId, text, timestamp }. +On page load, apply `.epi-decided` class to lines with decisions. +Right‑panel shows recent decisions; clicking jumps to the line. +Decision modal shows the original text for context.

---

05//Open QuestionsFuture

// ##decision-open ?Should decisions be exportable as a separate review list? ?How to handle decisions that become obsolete (archive vs delete)? ?Can decisions be linked to action items or tasks outside the wiki? ?What visual distinction from tags is optimal? (currently pink background)