| Momentum Monday | TPC's recurring Monday call (~60 min) | Not just "the Monday call" in member-facing copy |
| The room | Whoever is on the call that day | Not "the group" (could mean the cohort) |
| The cohort | The full 7-member TPC roster | Not "the room" (which is who showed up) |
| Facilitation guide | Pre-session document outlining session flow, watch-fors, and capture sheet | Not "agenda" — agendas don't have member watch-fors |
| Capture sheet | Live in-call note structure: members × what they said × specificity | Not free-form notes |
| Member file | cyp/tpc/members/[name].md — Kathryn's per-member living context doc | Not a CRM entry — these are facilitation notes, not sales notes |
| Planning doc | cyp/tpc/planning/tpc-communication-arc-through-mastermind.md | Not "the schedule" or "the calendar" |
| The arc | The multi-touchpoint communication sequence from Friday email through mastermind/retreat | Not "the campaign" — TPC isn't being marketed to |
| The build | A real-time co-design commitment made in-room (e.g., the advisory onboarding kit beta) | Not "the project" — this is an in-room commitment, not a managed project |
| The pivot | A facilitator move that departs from the facilitation guide (e.g., skipping a planned round) | Not a "change of plans" — pivot is intentional, plan-departure is observed and named |
| Live lab | TPC's status as a legacy mastermind being mined for Practice Builders mastermind IP | Not "test group" — TPC isn't being experimented on, but learnings flow forward |
| Otter recording | A member's raw, unfiltered voice memo recorded in Otter — used as input for kit-builds | Not "questionnaire response" or "form submission" |
| The two lenses | The "janky/broken" vs. "working/optimize" frame Kathryn uses for AI work | Not "buckets" — these are diagnostic lenses, not categories |
| Convergence | When the room independently lands on the same problem in different words | Not "consensus" — convergence is observed, consensus is voted/agreed |
| Avoided conversation | The relational/postponed-conversation thread Round 2 of a facilitation guide is designed to surface | Not "the hard conversation" — that's a corporate phrase TPC doesn't use |
| Beta build | A real-time commitment to ship a kit/skill/asset for the group to use, with members as co-designers | Not "MVP" or "prototype" — beta build is the mode, not the artifact |
| Recap email | The same-day Monday email summarizing what surfaced + reinforcing any in-room asks | Not "follow-up" — recap is part of the cycle, not a courtesy add-on |
| Cadence rule | Members get exactly 2 emails per week — Monday recap + Friday review/preview. The kit produces no other member-facing emails. | Not a guideline; a hard constraint. Violations fail QC. |
| Reference data file | cyp/tpc/tpc-reference-data.md — canonical authority on proper-noun spellings, firm names, tools, prior commitments | Not a roster (the roster is in CLAUDE.md). The reference data file is the spelling/canonical-detail authority for output content. |
| Action items (Kathryn's) | Build/listen items, Decision items, Doc-update items. Output 10 of the kit. | NOT member-touch items (those are Kathryn's manual judgment, not kit-produced). |
| The Friday ask | Whatever in-room commitment the group has by Friday (Otter recording, debrief form, etc.) | Not "the homework" |
| Facilitator review | The Kathryn-only post-session comparison of what happened to what was planned | Not "retrospective" — retros are team-shared; this is solo |