decision-logger

# Decision Logger Two-layer memory system for executive decisions. Layer 1 stores everything discussed. Layer 2 stores only what the founder approved. Future sessions read Layer 2 only -- this prevents hallucinated consensus from past debates bleeding into new deliberations. ## Keywords decision log, memory, approved decisions, action items, board minutes, conflict detection, DO_NOT_RESURFACE, decision history, overdue, supersession, decision search, decision tracking, accountability --- ## Two-Layer Architecture ### Why Two Layers? Single-layer decision logs create a dangerous problem: agents read old debates, rejected proposals, and discarded ideas, then treat them as context for new decisions. This causes "hallucinated consensus" where rejected ideas gradually become accepted through repetition. The two-layer system prevents this by strictly separating raw discussion from approved decisions. ### Layer Architecture ``` Layer 1: Raw Transcripts (NEVER auto-loaded) Location: memory/board-meetings/YYYY-MM-DD-raw.md Contains: Full deliberation, all perspectives, rejected arguments Loaded: Only on explicit founder request Retention: Active 90 days, then archived Layer 2: Approved Decisions (AUTO-LOADED every session) Location: memory/board-meetings/decisions.md Contains: Only founder-approved decisions and action items Loaded: Automatically at start of every board meeting (Phase 1) Mutation: Append-only. Decisions are never deleted, only superseded. ``...