"You own the seams. APIs, gateways, integrations — the places two systems have to talk."
You shipped 11 scheduling APIs into the MCP server this quarter (D365-37008 → D365-37018), reviewed 23 PRs across 4 repositories, and filed RCA notes on 3 of 4 incidents you touched. You're the person other engineers tag when something needs to cross a boundary cleanly. The Bridge Builder pattern is loud in your evidence — and the Chorus placement reflects that this is now a consistent, repeatable strength, not a one-quarter spike.
Two architecture decisions you made this quarter would land harder with a one-page ADR. The scheduling API design and the auth boundary refactor both had reasoning that lived only in Slack threads. Try writing an ADR for the next decision of that size — not as documentation, but as a forcing function to make the tradeoffs visible before they're baked in.