---
creationDate: 2025-01-01
type: log
aliases: [panel feedback, feedback log, panel log, panel notes]
last_updated: 2025-01-01
playbook_owner: <your name>
---

*Living log of every real piece of feedback the panel surfaces — across work, relationships, decisions, creative projects, anything where the panel weighs in. Patterns at the top get acted on; one-offs get logged but not yet promoted.*

**The panel is broader than work feedback.** It's the rotating cast of synthetic advisors you set up in `phase-10b-panel-roster.md`, real humans who give you feedback (advisors, coaches, friends, partners), and any other voice that gets pulled in to react to a draft, decision, or framing. This log captures all of it in one place so patterns become visible across contexts.

**Discipline:**
- **Real humans only** in the "By Meeting / Conversation" section. Synthetic / AI panel reactions go in their own section at the bottom, clearly labeled.
- **Cross-context.** Not just one domain — work feedback, relationship feedback, creative critique, decision reviews, body signals. If the panel reacted, log it.
- **Quote verbatim** when something stings. Don't paraphrase the painful stuff away — that's the part worth keeping.
- **Promote to Patterns at the 2nd mention across DIFFERENT contexts.** First time = data point. Second time = signal. Same person flagging the same thing twice in one week is one mention.
- **Log the praise, not just the criticism.** What lights people up matters as much as what makes them push back.
- **Categorize by topic** so patterns surface by context.
- **After every Granola transcript, coaching session, or substantive panel reaction**: 2-minute extraction pass into this file. Don't let panel insights evaporate between sessions.

**Behavioral rule for Claude:** the panel should join in proactively when there's a real judgment moment — drafts, decisions, framings, tradeoffs — *without being asked.* The user should not have to type "what does the panel think." If a moment clearly warrants the panel, pull them in.

---

## Patterns (act on these)

*Things 2+ panelists or coaches have flagged across different contexts. The action layer.*

| Pattern | Mentions | Action |
|---|---|---|

*(Promote to acute action items here when we hear the same thing twice across different contexts. One coaching session = one mention even if multiple panelists agreed during that session.)*

---

## By Meeting / Conversation (chronological)

*Real-human feedback only. Synthetic panel reactions go in Section 3 at the bottom.*

### YYYY-MM-DD — <Person or context>

- **Source:** <wikilink to meeting note / decision log / coaching session>
- **Verdict:** (interested / pass / want to follow up / advisory only / etc)
- **What they liked:**
- **What they pushed back on:**
- **Direct quotes worth keeping:**
- **Action:** (apply now / test in next conversation / log only / promote to Patterns)
- **My note:**

---

## Section 3 — AI panel inputs (synthetic)

⚠️ **These are Claude-generated panel reactions, NOT real human feedback.** Useful as a thinking tool, but never conflate with what real humans said. Sourced from `/journal` panel sections, `/coaching` sessions, and any inline panel pulls during regular Claude conversations.

### YYYY-MM-DD — <Topic> coaching session

⚠️ **Synthetic panel reactions across one Claude session.**

**Context:** <one paragraph framing>
**Panelists:** <list of voices>
**Pass 1:** <what surfaced first>
**Pass 2 (if multi-pass):** <how takes updated with corrections>
**Convergence:** <high-confidence signals across all passes>
**Clash:** <where panelists disagreed>
**Subject-match weighting:** <which panelist's voice carries most weight>
**Collective blind spot (chairman):** <what all panelists missed>
**User's commitments:** <numbered list>
**Re-eval:** YYYY-MM-DD (one month out). <Re-eval signals.>
**Entry:** <wikilinks to coaching session record + verbatim>
