Source: frameworks/kit-tpc-post-momentum-monday/03-tpc-post-momentum-monday-golden-example.md

03 — GOLDEN EXAMPLE: TPC Post-Momentum-Monday Kit

The golden example is the 2026-04-27 run — the first run of this kit, produced on the day the kit was authored. The actual artifacts live in the TPC client folder, not duplicated here.

Critical: TPC Emails Are Newsletters, Not Direct Gmail

The Monday recap email and the Friday email are MailerLite newsletters, not directly composed Gmail messages. This shapes everything about Output 1 and Output 8.

Delivery model:

The kit produces a markdown source that Kathryn pastes into MailerLite
The kit produces an HTML version that's the Gmail-paste fallback (used when she wants a quick send without going through MailerLite, or for the test draft she creates to herself)
The actual sent format renders through MailerLite's templating

Subject line pattern: [Test] TPC: Momentum Monday Recap- M-DD-YYYY (note the [Test] prefix is intentional during the system's development phase — confirm with Kathryn before removing it)

Friday email subject: [Test] TPC: Weekly Review and Preview - M-DD-YYYY

Voice/format references:

3-16 sent recap (the canonical structural example) — recovered from Bev's quoted reply in Gmail thread 19cf91baf50611d1. This is the only complete prior recap accessible via Gmail (the MailerLite previews are egress-blocked). Use this as the structural reference.
4-24 Friday V2 archive — cyp/tpc/archive/tpc-friday-email-2026-04-24-v2.md. Same tonal voice; different job.
4-27 Monday recap (this kit's first golden) — cyp/tpc/drafts/tpc-monday-recap-2026-04-27.md + .html. Built to match the 3-16 structure exactly.

The actual 3-16 structure (locked):

Hi there,

Here's your recap from this week's Momentum Monday.

If you want to hear the conversation, here's the link. If you'd like to check out the chat, here's the link.

**What we covered:** [one-sentence summary of the session arc]

**Highlights:**
- [3-4 bullets — key decisions, builds, commitments]

**What Surfaced**
- Member: [one line]
- Member: [one line]
[6 lines, one per member — names + 1-line of substance, can include personal life touches]

**Housekeeping:** [calendly link, scheduling note, anything functional]

Talk soon,
Kathryn

Length target: ~300 words. The Google Doc overview holds the depth; the email is the digest.

Links are stable week-to-week and hard-coded in the kit:

Recording: https://programs.creatingyourplan.com/
Chat (Google Doc): https://docs.google.com/document/d/15UZryXs5K_76rWfHs1kRnL6jrb1LnNmgxvOShLPLK8E/edit

These appear in every Monday recap email and never change. The MailerLite click-tracking redirects (mvglgq.clicks.mlsend.com/...) that show up in sent emails are auto-generated by MailerLite from these underlying URLs — Kathryn pastes the stable URLs into MailerLite, MailerLite handles the tracking layer. The kit produces output with the stable URLs, not the redirects.

Signoff: "Talk soon," — NOT "See you Monday," (that's a different cadence Kathryn doesn't use here).

Why this run is the golden example

The 4-27 run exercises every output the kit produces, including:

Standard recap when attendance is mixed (4 of 7 attended)
Member-file update when a member's prior profile is dramatically wrong (Linda — went from "low context" to "high engagement")
Member-file update for absentees (Tracy, Shelley, Meryl)
Facilitator review of a session that deviated from its facilitation guide (skipped Round 2, skipped Light Sort, pivoted to a real-time build commitment)
Lessons-learned entry where the deviation was the lesson
Planning doc update where the arc shape itself changed
Friday email skeleton built around a deeper question carrying forward the avoided-conversation work that Monday didn't run

Future runs may not exercise every dimension — but the 4-27 run does. Use it as the structural reference.

Pointers to the actual artifacts

cyp/tpc/sessions/
    The Tax Pro Collaborative - Momentum Monday - 4-27-2026.txt    (input transcript)
    tpc-momentum-monday-2026-04-27.md                              (personal recap — Output 2)
    tpc-momentum-monday-2026-04-27-facilitator-review.md           (facilitator review — Output 3)
    tpc-momentum-monday-2026-04-27.json                            (JSON — Output 5)

cyp/tpc/drafts/
    tpc-monday-recap-2026-04-27.md                                 (Monday recap, source — Output 1)
    tpc-monday-recap-2026-04-27.html                               (Monday recap, Gmail-paste — Output 1)
    tpc-monday-facilitation-guide-2026-04-27.md                   (input facilitation guide)
    tpc-friday-email-2026-05-01-skeleton.md                       (Friday skeleton — Output 8)

cyp/tpc/members/
    linda-stapf.md, rob-foncannon.md, bev-stitely.md, diane-gardner.md       (Output 4 — attendees, full update sections appended)
    tracy-beveridge.md, shelley-johnson.md, meryl-greenwald.md               (Output 4 — absentees, light note appended)

cyp/tpc/planning/
    tpc-communication-arc-through-mastermind.md                    (Output 6 — appended "Post-4-27 Update" section)

cyp/tpc/lessons-learned/
    lesson-listening-to-building-pivot-2026-04-27.md              (Output 7)

What to study in each artifact

Output	What's worth studying in the 4-27 version
1. Monday recap email	Length (tight). Subject line format. Pattern-level reflection without single-member call-outs. The "ask" section being clearly visible and time-boxed. Housekeeping section addressing absentees without naming them awkwardly. Voice match to prior Friday email (4-24).
2. Personal facilitator recap	"What We Discussed (in order)" structure. Member-by-member contribution detail. The takeaways section linking to Kathryn's broader business and Practice Builders work. Quotes section with speaker + context.
3. Facilitator review	The "did the session do its job?" framing. The "where you held the plan / where you broke from the plan" structure. The honest self-questions (e.g., "Did you skip Round 2 because of momentum, or because you didn't want to slow it?"). The calibration-for-next-session section.
4. Member file (attendee — Linda)	Full revision of Engagement Patterns section (was "low context," became "high engagement"). New `## YYYY-MM-DD Session Contributions` section with AI use cases, pain points, commitment, watch-for added. Topic candidates updated.
4. Member file (attendee — Diane)	Lighter update because her profile already fit. The new section captures contributions, pain points, the quiet-but-processing observation, and a watch-for added.
4. Member file (absentee — Tracy)	Brief absence note with action item (personal reach-out) and a forward-looking watch-for if she sends a recording later.
5. JSON	Schema match with the 4-13 baseline plus an `absent` array. `actions` array with dates. `quotes` with full speaker + context. `connections` separating attendees from absentees with their respective follow-ups.
6. Planning doc append	New "YYYY-MM-DD Update — Arc Has Shifted" section showing original arc table marked-through and replaced with revised arc table. The "what's new in the arc" + "what's still uncertain" structure.
7. Lessons-learned entry	One-line lesson title. The "what happened / what I'd do differently / implication for Practice Builders" structure from the lessons-learned README. Cross-reference at the bottom.
8. Friday email skeleton	Job-of-the-week framing. Three "deeper question" options matching different post-Monday patterns. Section-by-section skeleton (placeholder text). The "what to verify before sending" section. The "do NOT" list.

What this run shows that future runs may not

Member-file profile dramatic revision (Linda). Most runs will be incremental updates. When this happens again, follow the Linda pattern: revise the existing sections AND append a new contributions section.
Facilitator review of a deviation. Most sessions will follow the facilitation guide. When they don't, follow the 4-27 review pattern: the "where you held / where you broke" structure, the trade-off naming, the recovery channels.
Planning doc arc shift. Most weeks the arc holds. When it shifts (because of an in-room build commitment, an attendance pattern change, or a topic emerging that wasn't on the map), the planning doc gets a new section explicitly framing the shift.
Lessons-learned trigger. Most sessions don't generate a new lesson. The 4-27 run did because of the listening-to-building pivot. The kit should produce a lesson only when one is genuinely earned — not by default.

Pre-existing partial golden examples

Before the 4-27 run, two outputs already had golden examples in the TPC folder:

Personal recap baseline: cyp/tpc/sessions/tpc-momentum-monday-2026-04-13.md
JSON baseline: cyp/tpc/sessions/tpc-momentum-monday-2026-04-13.json

These were produced via the generic /recap-meeting skill and remain valid format references. The 4-27 versions extend them; they don't replace them.

When to update this file

Update this golden example reference when:

A run produces an output significantly different from the 4-27 version, AND
Kathryn keeps the new version (i.e., the new version becomes the better reference)

In that case, run the kit-builder in Mode 2 to update the golden example pointer + the relevant output skill instructions + (potentially) the QC checklist.