In today's quarterly engineering leaders

Answer

I'll pull the relevant cards before writing the speakable lines.

You froze in the room. That's normal — the correction doesn't have to happen in the room. The email is the correction; the 1-on-1 anchors it for the review cycle. Here are the three lines.

---

**Today — the email/thread (paste into the recap thread for today's review; CC your manager):**

> Subject: Attribution — multi-region failover architecture (today's review)
>
> Hi all,
>
> For the record on the multi-region failover architecture and benchmarking presented in today's engineering leadership review: the design, implementation, and benchmarking were done by me solo over the past three weeks. [Peer] presented, but the work is mine.
>
> I'd like this reflected in the meeting notes and any materials shared from today, before our mid-year review cycle begins next week.
>
> Thanks,
> [Your name]

The peer is on this thread. That's the point — he can't claim he didn't see it. Your manager being CC'd means the record is anchored before the review.

| His likely reply | Your next line |
| --- | --- |
| "Of course, my apologies — I'll update the notes." | "Thanks. Please reply-all confirming the notes will be updated before mid-year reviews start." |
| Silence, or a vague "let's discuss" | "I'll follow up on this in my 1-on-1 tomorrow. For now I need a yes/no on whether the meeting notes will be corrected." |
| "I thought it was understood we collaborated" | See comeback below. |

---

**Tomorrow — manager 1-on-1, opening line:**

> "I want to flag something from today's engineering leadership review. [Peer] presented the multi-region failover architecture and benchmarking as his team's. That work is mine — I designed, implemented, and tested it solo over the past three weeks. I'd like my mid-year review to reflect that, and I'd like your help getting the record corrected before the cycle starts."

| Manager's likely reply | Your next line |
| --- | --- |
| "I didn't realize. Let me check." | "Thanks. Could you confirm with [Peer]'s manager and update the meeting notes by [date this week, e.g. Wednesday]?" |
| "I'll talk to him." | "Good. Please loop me in on what he says, and let me know by [date] what changes to the notes." |
| "Couldn't it have been a joint thing?" | "I designed, implemented, and tested it solo. I can share the commit history, design doc, and any messages if that helps. The review should reflect that." |
| "Let's not make this a thing." | "I'm not trying to escalate. I just need the record to be accurate for mid-year reviews, and I'd like your help making that happen." |

---

**Comeback for "I thought it was understood we collaborated":**

The shape: name what you actually did, name what didn't happen, pivot to attribution. Don't debate intent.

Firmer version:
> "I appreciate you saying that, but I want to be clear: I designed, implemented, and benchmarked this alone. There were no commits, design reviews, or pair sessions from your team. I need authorship to be reflected accurately — especially with mid-year reviews starting next week."

Softer version, if you want to keep the working relationship intact:
> "Help me understand what 'collaboration' means here — I didn't receive any code, review, or design input from your team. I'd like the attribution to be accurate going forward, starting with the mid-year review."

If he pushes further with "we should be generous with credit / engineers share ideas all the time":
> "Ideas aren't authorship. The design, code, and benchmarking are mine, and the review should say so. Let's not relitigate the past — going forward I just need clear attribution."

---

**One line on the freeze:** freezing in the room doesn't cost you anything if the email goes out today. The room is over; the thread and the review cycle are what matter now.