Source: frameworks/kit-tpc-post-momentum-monday/04-tpc-post-momentum-monday-quality.md

04 — QUALITY: TPC Post-Momentum-Monday Kit

When to run: After every output is drafted, before presenting to Kathryn. Format: Two gates. Gate 1 is binary (pre-build readiness). Gate 2 is per-output checklist.

Gate 1 — Pre-Build Readiness (Binary)

Cannot proceed past this gate if any check is no.

[ ] TPC reference data file (cyp/tpc/tpc-reference-data.md) has been read FIRST — proper-noun spellings, firm names, tools, prior commitments are all loaded
[ ] Transcript is readable end-to-end
[ ] All 7 member files have been read in this session
[ ] TPC CLAUDE.md has been read in this session
[ ] Session prep doc located and read — OR confirmed not to exist for this session (either is a pass; guides were discontinued 2026-06-22)
[ ] Planning doc current state has been read
[ ] Attendee list cross-checked against TPC roster + reference data (anyone not in transcript is flagged as absent)
[ ] Absentees' reasons identified (or marked unexplained)
[ ] Kathryn confirmed the run plan ("Confirm Understanding" step from 00-start-here)

Gate 2 — Per-Output Quality Checklists

Output 1 — Monday recap email

[ ] Subject line is TPC: Momentum Monday Recap- M-DD-YYYY — no [Test] prefix (dropped 6-8-2026 when the system went live)
[ ] Opener is Hi there, followed by an optional one-line warm opener
[ ] Recording link + session-notes link in the second paragraph, link text here's the link
[ ] Highlights is ONE framing bullet — what the session was at altitude. Never a tactical/teaching list.
[ ] "What Surfaced" is ONE line per PRESENT member; absentees combined into ONE forward-looking line (walk-through coming + offer of help — never "watch the recording")
[ ] Superlatives eased; no hype quotes (proof-point enthusiasm lives in Output 2)
[ ] Doesn't telegraph going deeper next session; doesn't put Kathryn's words in members' mouths; doesn't center the facilitator
[ ] Housekeeping is tight; Calendly link present; no P.S. block
[ ] Sign-off is Talk soon, — NOT See you Monday,
[ ] No internal facilitator language ("convergence," "pivot," "watch-fors," "pain points")
[ ] No corporate-speak from the forbidden list (file 02)
[ ] Length target: ~250 words (allow drift up with a full house — more present members means more "What Surfaced" lines)
[ ] Ship-state stamped Status: DRAFT — not sent per cyp/tpc/tpc-email-ship-state.md
[ ] HTML: inline styles only, no scripts, no external stylesheets; — / & / ’ entities correct; link color #478AA0

[ ] HTML uses paragraphs, NOT

bullets, for multi-item sections

[ ] Both .md and .html files exist in cyp/tpc/drafts/

Output 9 — Google Doc overview entry

[ ] Format: #### header, What We Discussed, numbered topics with sub-bullets
[ ] Starts at first substantive topic (no weekend/social check-in section)
[ ] Sub-bullet format throughout — no narrative paragraphs
[ ] No editorial commentary ("The pattern:", "The fix:", "Fair.", "Valid point.")
[ ] No thematic framing ("an accidental theme showed up," "nobody planned it but...")
[ ] Members' questions reported as questions — never framed as "pushed back," "resisted," "disagreed"
[ ] No characterization of member understanding ("where it clicked," "she tracked that but...")
[ ] Quoting proportional to weight — casual questions get paraphrases, not block-quote treatment
[ ] All member names spelled per reference data file
[ ] 5-8 numbered topics, each with 3-6 sub-bullets (not fewer, not more than 6 per topic)
[ ] Content matches transcript — no invented contributions, no extrapolation
[ ] Facts in doc overview match facts in email recap (Output 1) — no contradictions between the two

Output 2 — Personal facilitator recap

[ ] Header has Date, Meeting, Attendees (named), Absent (with reason)
[ ] Summary is 2-4 sentences capturing the session arc
[ ] "What We Discussed (in order)" section follows the actual transcript order
[ ] Each member with substantive contributions has their own subsection
[ ] Quotes are actual transcript quotes, attributed correctly (member-name spelling per terminology file)
[ ] My Takeaways section connects to Kathryn's broader business / IP / clients
[ ] Connections to Follow Up table is complete (one row per attendee + absentees)
[ ] Action Items list is concrete and dated where relevant
[ ] Ideas Sparked section names what's reusable
[ ] Quotes Worth Remembering section has speaker + context for each

Output 3 — Facilitator review

[ ] "Did the session do its job?" framing is candid, not self-protective — measured against the prep doc's stated job, or against what the session was evidently for if no prep doc exists
[ ] "Where you held the plan / where you broke from the plan" structure used
[ ] Each plan-departure has a trade-off analysis (cost / benefit / honest question)
[ ] Airtime section names dominance patterns specifically
[ ] What landed / what didn't land sections are concrete
[ ] Calibration-for-next-session has 4-6 specific actions
[ ] At least one self-question Kathryn should sit with
[ ] No sanitizing for an external audience — voice is candid

Output 4 — Member file updates

[ ] Each attendee has a new ## YYYY-MM-DD Session Contributions section appended
[ ] Section includes: AI/topic-specific contributions, pain points named, quotes for the file (if applicable), commitment made, new watch-for added
[ ] If the existing profile shifted, the existing sections are revised (not just appended)
[ ] Each absentee has a brief absence note appended with action item
[ ] No member's contributions are invented or extrapolated beyond what's in the transcript
[ ] Topic Candidates for Three Events updated where new signal warrants

Output 5 — JSON

[ ] Schema matches the 2026-04-13 baseline (meetingDate, meetingType, participants, conversation, takeaways, actions, quotes, connections, ideas)
[ ] absent array added with name + reason for any non-attending members
[ ] All names spelled per the terminology file's spelling authority
[ ] All quotes are exact transcript quotes (not paraphrased)
[ ] actions items have dates where the session set a date; empty string otherwise
[ ] connections includes both attendees and absentees with appropriate follow-ups
[ ] Valid JSON (would parse without error)

Output 6 — Planning doc append

[ ] New section appended at bottom (not interleaved into existing content)
[ ] Section title names what changed (e.g., "Arc Has Shifted" / "Arc Holds — minor adjustments")
[ ] If arc shifted: revised arc table provided with row-level changes
[ ] "What's new in the arc" and "What's still uncertain" sub-sections present
[ ] Cross-reference to facilitator review and lessons-learned (if any) included

Output 7 — Lessons-learned entry (conditional)

[ ] Decision: Was a real lesson surfaced? (If no — skip this output. Don't force one.)
[ ] If yes: file format matches cyp/tpc/lessons-learned/README.md
[ ] One-line lesson title is specific and decision-actionable
[ ] What happened section describes concretely (no generalities)
[ ] What I'd do differently section is specific (the redo)
[ ] Implication for Practice Builders mastermind section names what carries forward
[ ] Cross-reference to facilitator review at bottom

Output 8 — Friday email skeleton

Governed by cyp/tpc/planning/tpc-friday-email-rules.md. Check conformance to it:

[ ] Drafts ONLY the personal message section — no form, calendar, retreat block, signature, or footer redrafted (those are already in the MailerLite template)
[ ] Structure per rules file: warm opener → next-week sessions (what they do + what Kathryn does + what to have ready) → optional one question → 1-on-1 reminder → sign-off
[ ] Plain, paste-ready prose — no markdown bold/headers, no job-of-the-week, no single "ask," no deeper-question options, no verify/Do-NOT lists
[ ] Subject + campaign name format: TPC: Weekly Review and Preview - [M-D-YYYY] (no [Test] prefix on the real send)
[ ] Forbidden terms absent (per rules file + feedback-no-coach-language.md, feedback-tpc-no-insider-words.md, feedback-no-honest-word.md)
[ ] Header present marking it as the personal-message section to paste into the MailerLite template

Output 8 (filled) — When the skeleton is filled into a sent Friday email

[ ] Every line traces to either (a) the prior shipped Friday email in archive/, (b) the most recent transcript in cyp/tpc/transcripts/, or (c) Kathryn's known voice patterns from member feedback memories
[ ] No skeleton example text preserved as voice (failure mode: lifting the skeleton's [example: ...] text and treating it as Kathryn's voice)
[ ] No coach/facilitator phrases (per feedback-no-coach-language.md): "sit with," "rattle around for me," "lean in," "show up," "no prep," "scaffold," "starting place," "worth naming," "hold space"
[ ] No insider vocabulary (per feedback-tpc-no-insider-words.md): "kit" as noun, "playbook," "framework" as noun
[ ] No fabricated patterns — if listening hasn't happened, do not claim patterns from recordings
[ ] Bridge sentences explicitly connect each section to the others (Section 2 question must connect to the recordings/onboarding context, not float free)

Output 11 — Next Monday's prep doc

[ ] ONE PAGE. If it's longer than mm-2026-07-20-operating-week.md, it's too long — cut.
[ ] Five sections only: header / why this session / run it / watch for / decisions to land
[ ] "Why this session" names the job AND what is NOT being done
[ ] "Run it" has rough minutes per segment, in short bullets
[ ] "Watch for" carries only the members who actually need a note this week — not the full roster by default
[ ] Pulls from the prior facilitator review's "Calibration for next session"
[ ] NOT a facilitation guide — no per-segment anchor questions, no capture-sheet tables, no per-member pull-in prompts. That format was discontinued 2026-06-22.

Output 10 — Kathryn's Action Items

[ ] Markdown action-items doc exists at cyp/tpc/group/tpc-action-items-YYYY-MM-DD.md
[ ] Doc has three sections: Build/listen, Decision, Doc-update
[ ] No Member-touch items (personal reach-outs, 1:1 emails) appear anywhere in the output — these are explicitly out of scope per the cadence rule
[ ] No Gmail drafts created outside the Monday/Friday cadence — only Outputs 1 and 8 produce member-facing emails
[ ] Each Build/listen item has a proposed calendar event with title, description, duration, target date
[ ] Calendar events were created via the calendar MCP (or proposed for Kathryn to create if MCP unavailable)
[ ] Each Decision item has a by-when date and a "what's needed to decide" line
[ ] Doc-update items list what's already done by the kit AND what (if anything) requires Kathryn's manual touch (e.g., reference data updates)
[ ] Items extracted from Output 2 (personal recap), Output 3 (facilitator review), Output 6 (planning doc) — sources cross-checked
[ ] Items not fitting any category are flagged for Kathryn's review, not silently dropped

Output 12 — Notion board writes

[ ] KHB Operations open-items card created — ONE per run, Workstream TPC, Ball With Kathryn, Status In progress
[ ] Every open item on the card links to its source (repo path, another card, or URL)
[ ] Card body has ## Open items + ## Artifacts + ## Feedback
[ ] TPC Member Pipeline: every present member's row has updated Last touch + appended (not overwritten) Signal / why; absentees get a light note
[ ] Lane / Current read NOT auto-changed — any shift is proposed for Kathryn, not written silently
[ ] Both board links returned in the completion output

Cross-Output Consistency Checks

[ ] Member names spelled identically across all outputs (cross-reference terminology file)
[ ] The Monday recap email's pattern reflection matches what the personal recap captured (no drift)
[ ] The facilitator review's deviations match what the lessons-learned entry (if any) addresses
[ ] The planning doc update's arc-shift narrative matches the facilitator review's deviation analysis
[ ] The Friday email skeleton's deeper question carries an actual missing thread from this session (not generic)

Common Failure Modes

Failure	What Happens	How to Fix
Cadence rule violated — kit drafts a member-facing email outside Monday/Friday	Member experience inconsistent; trust erodes	Hard-constraint check on every Output 10 run: zero member-facing emails permitted outside Outputs 1 and 8
Reference data not read first — names misspelled, tool references wrong	Recap quality drops; trust erodes	Gate 1 enforces reference-data-first; if Gate 1 fails, run cannot proceed
Member quoted in Monday recap email	Member feels singled out	Move the quote to personal recap; pattern-level only in member-facing
Forbidden term ("convergence," "pivot," "watch-fors") leaks into Monday email	Sounds clinical	Run a forbidden-term scan against the email before HTML conversion
Member-file profile not revised when it should be	Stale member context affects future facilitation	Compare current contributions to existing engagement profile — if they conflict, revise existing sections, not just append
Lessons-learned entry forced when no real lesson surfaced	Folder bloats with non-lessons	Decision-gate at top of output 7: was a real lesson surfaced? Skip if no.
Planning doc append duplicates info from member files	Maintenance burden, two sources of truth	Member-specific stays in member files; planning doc is arc-level only
Friday email skeleton's deeper question is generic	Wastes the touchpoint	Tie the deeper question to a specific thread the week missed (e.g., avoided-conversation when Round 2 was skipped)
Skeleton placeholder text lifted as voice when filling Output 8	Email reads coach-y / not-Kathryn; multi-round rewrite churn	Voice anchor rule (file 05): voice traces to prior shipped piece + transcript ONLY. Skeleton bracketed example text is structural marker, never voice reference. If draft uses any phrase from the bracketed examples, throw it out and rewrite from anchors.
Output 8 sections disconnected from each other	Question floats free of recordings/onboarding context; reads as random reflective question	Bridge sentence explicitly connects Section 2 (question) to Section 1 (recordings) — e.g., "You sent me the operational side. Every onboarding I've built has had a conversation underneath it that hadn't happened yet. So — [question]."
Weekend/personal check-in included in Output 9	Google Doc overview is member-facing — personal updates make it read like a journal, not a session record	Output 9 rule #8: start at first substantive topic. Social/personal opening is NOT session content. Weekend details belong in Output 2 (personal recap) only.
Facilitator observations or internal language in Output 9	Doc overview reads like facilitator notes — room-dynamic observations ("Room initially quiet"), assignment narration ("Assigned Linda to book a one-on-one"), methodology language ("process pattern," "extract"), meta-observations about how the room responded	Rules #10 and #11. Remove all facilitator-perspective content: room dynamics, assignment narration, internal vocabulary, topic titles that frame a member's problem with internal language. These belong in Output 2 (personal recap), not the group-facing record.
Output 9 written as meeting minutes instead of authored record	Every bullet starts with "Member: [thing]" — reads like a transcript index, not a curated record of what was discussed. Kathryn attributed as "Kathryn:" like any other participant. No synthesis, no variation in structure across topics.	Kathryn is the author, never attributed as "Kathryn:" — her contributions are the narrative voice. Mix attributed member quotes with unattributed synthesis. Combine related contributions into single bullets. Vary structure across topics (some quote-heavy, some synthesis, some mixed). Compare to the 5-4 doc overview as the format reference.
HTML email has scripts or external stylesheets	Doesn't paste cleanly into Gmail	Inline styles only; no scripts
Absentee not noted in Monday email	Someone wonders if they were forgotten	Always include a housekeeping line for absentees, even just "if you'd like to send a recording, same deadline"
Action items output includes member-touch items	Cadence rule violated	Hard scope: only Build/listen, Decision, Doc-update categories permitted in Output 10
Calendar event proposed without realistic duration	Kathryn ignores it	Each event has a duration tied to the actual work (e.g., find-the-answer research = 45 min; kit-build = 4-6 hour weekend block)

Pass Criteria

Every output passes its per-output checklist + all cross-output consistency checks pass + Common Failure Modes scan returns clean.

If conditional outputs (lessons-learned) skipped: log the skip with reason in the Mode 2 improvement note for kit-builder.