Wow  🔗 **Source:** [Wow](https://twitter.com/trentlapinski/status/2100317306832159064/?rw_tt_thread=True) > [!note]+ Document Notes > --- > tags: [automattic, executive-severance, shareholder-litigation, wp-engine-lawsuit, corporate-governance, speculation] > author: Trent Lapinski (@trentlapinski) — quoting Sarah Perez (@SarahPerezTC) > source: X (formerly Twitter) > reference: https://twitter.com/trentlapinski/status/2100317306832159064/?rw_tt_thread=True > date created: 2026-09-19 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > ## 🏷️ Title > **Wow. This gets even crazier.** — Trent Lapinski on the Automattic reciprocal-severance report > The Reader title is the single word "Wow," but that is only the first word of a substantive post. The capture is a full commentary thread-post of roughly 199 words, and it quotes a second post by a different person, which in turn links a third thing — a TechCrunch news article. Three layers of authorship are fused together in the capture with no visual boundary, so the first job of this analysis is to untangle them. > **Authorship map — who wrote what:** > | Layer | Author | Content | > |---|---|---| > | Outer post (the "Wow") | **Trent Lapinski**, @trentlapinski | "Wow. This gets even crazier." through "Popcorn anyone?" — the entire speculative analysis, the two-option scenario, the board-member observation and the WPE guess. | > | Quoted post | **Sarah Perez**, @SarahPerezTC (TechCrunch reporter) | One headline-style line: "Automattic's interim CEO and legal chief signed reciprocal severance deals during Mullenweg's brief ouster" plus the article link. Posted Sep 16, 2026 at 7:47 PM. | > | Linked article | **TechCrunch** (byline presumably Perez, not shown in capture) | The actual reporting. Not in the capture — only the URL is. | > Everything argumentative in this document is Lapinski's. Perez contributes a factual headline and a link, nothing more. Attributing the severance-conspiracy reading to Perez or to TechCrunch would be a misattribution; attributing the underlying fact of the signed agreements to Lapinski would be the reverse error. > ## 🧭 Table of Contents > - [🔗 References (in-page)](#-references-in-page) > - [📝 Summary](#-summary) > - [📖 Main Content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action Items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future Research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning Styles Assessment](#-learning-styles-assessment) > - [📊 Accessibility Assessment](#-accessibility-assessment) > - [🌍 DEIB Assessment](#-deib-assessment) > - [✅ Logical Validity](#-logical-validity) > - [🛡️ DARVO Analysis](#️-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > - [🔄 Refactor Appendix](#-refactor-appendix) > ## 🔗 References (in-page) > Links present inside the captured body, in the order they appear: > 1. Sarah Perez's X profile — https://twitter.com/SarahPerezTC (appears twice, once as display name, once as handle) > 2. The TechCrunch article, shown in the post as a truncated `techcrunch.com/2026/09/16/aut…` link — https://techcrunch.com/2026/09/16/automattics-interim-ceo-and-legal-chief-signed-reciprocal-severance-deals-during-mullenwegs-brief-ouster/ > 3. The quoted post's permalink, rendered as "Posted Sep 16, 2026 at 7:47PM" — https://twitter.com/SarahPerezTC/status/2100310736576639298 > 4. A profile image asset — https://pbs.twimg.com/profile_images/1745153177182216192/7VgfuqS6.jpg > This matters: an earlier pass on this document recorded "no outbound links" in both References sections. That was wrong. The capture is **not** uncited — it carries a direct link to the primary reporting, which is more source discipline than most commentary in this cluster shows. > ## 📝 Summary > **What happened.** On September 16, 2026, TechCrunch's Sarah Perez reported that Automattic's interim CEO and its legal chief signed *reciprocal* severance deals during Matt Mullenweg's brief removal from the CEO role. Perez posted the headline and link to X. Trent Lapinski quoted that post and added a roughly 199-word reading of what the arrangement implies, opening with "Wow. This gets even crazier." > **Lapinski's reading, in five moves.** (1) The board and executive team removed Mullenweg *in order to* pay themselves, anticipating that he would return as CEO and fire them. (2) Mullenweg now faces a binary: honour the agreements and buy the executives' silence, or refuse them and invite lawsuits or press leaks. (3) Therefore paying them off is a live route to avoiding at least *their* litigation. (4) Separately, two other board members — whose fate the post says is unknown — are "far more likely" to lead a shareholder class action, so that exposure remains. (5) Explicitly labelled as a guess: the group expected to lose the WP Engine case and secured golden parachutes before letting the company burn. > **Why it matters.** Automattic is the principal corporate sponsor of the WordPress project. Governance instability and litigation exposure at that sponsor is an ecosystem-level variable, not merely a corporate-gossip item. More narrowly, the *reciprocal* character of the severance deals — each officer signing the other's — is the detail that makes this newsworthy rather than routine, because it removes the usual independent-approval step. > **Stakeholders.** Automattic shareholders (the parties with standing to sue); the interim CEO and legal chief (holders of the agreements, and the parties whose silence is at issue); Matt Mullenweg (restored CEO, holder of the honour-or-refuse decision); the two unaccounted-for board members (the larger latent legal exposure); WP Engine (whose litigation supplies the alleged motive); and the WordPress contributor community, which absorbs the second-order effects of any of it. > **Risks in taking this at face value.** The causal core — removal engineered *in order to* trigger severance — is unevidenced and requires the participants to have correctly forecast their own firing. The WPE-foreknowledge claim is speculation stacked on that speculation. Lapinski marks the second with "My guess is"; he does not mark the first, which is the more consequential of the two. The closing "Popcorn anyone?" sets an entertainment register over a dispute with real employment consequences. > **Bottom line.** The post is a useful *scenario map* and a genuinely sharp *incentive analysis*, wrapped around a motive story that has nothing behind it. Keep the first two. Discard the third. And follow the TechCrunch link, which is right there in the capture and is the only actual evidence in the document. > ## 📖 Main Content > ### The one genuinely load-bearing insight: payoff structure is knowable when motive is not > The strongest thing in this post is also the least dramatic. Lapinski observes that the signed severance agreements create a determinate incentive structure for the departing executives regardless of why those agreements exist: > - **If honoured:** the executives receive their money, have a continuing financial relationship to protect, and — critically — almost certainly signed standard non-disparagement and release-of-claims language alongside it. Their rational move is silence. > - **If refused:** the executives have a contractual claim, no money, and nothing to lose reputationally. Their rational moves are suit, leak, or both. > This reasoning holds whether the agreements were engineered as a golden parachute or whether they are the boilerplate that any competent general counsel papers during a leadership transition. That independence from the motive question is exactly what makes it worth keeping. It is a structural claim, not a psychological one. > It is worth stating the mechanism Lapinski gestures at but does not name: severance agreements do not buy silence by themselves. Non-disparagement clauses and releases of claims buy silence, and they ride along with severance. "Honour the agreement" is therefore shorthand for "activate the release," and the post would be str Wow. This gets even crazier. Now it sounds like the board and exec team at Automattic removed Matt so they could pay themselves knowing Matt would just come back as CEO and fire them. Now Matt has two choices. 1) He can honor the severance agreements they signed and they shut up and don’t sue him, or 2) he can refuse the severance packages and they likely sue or run to the press and leak everything. This means there’s actually a path for Matt to just pay these executives off and avoid a lawsuit from them at least. On the other hand, we don’t know what happened to the two other board members who are far more likely to lead a class action shareholder lawsuit. So that’s probably still on the table. My guess is they knew they were going to lose the WPE case and did this to ensure a golden parachute for themselves and just let the company burn. Popcorn anyone?  [Sarah Perez](https://twitter.com/SarahPerezTC) [@SarahPerezTC](https://twitter.com/SarahPerezTC) Automattic’s interim CEO and legal chief signed reciprocal severance deals during Mullenweg’s brief ouster [techcrunch.com/2026/09/16/aut…](https://techcrunch.com/2026/09/16/automattics-interim-ceo-and-legal-chief-signed-reciprocal-severance-deals-during-mullenwegs-brief-ouster/) [Posted Sep 16, 2026 at 7:47PM](https://twitter.com/SarahPerezTC/status/2100310736576639298), Wow, Trent Lapinski, 01m2p636g71pvws9cmrg2pa6ff.