Automattic Minus Matt  🔗 **Source:** [Automattic Minus Matt](https://tedium.co/2026/09/10/matt-mullenweg-automattic-leave-absence/) > [!note]+ Document Notes > tags: [wordpress, automattic, matt-mullenweg, corporate-governance, open-source-leadership] > author: Ernie Smith > source: Tedium > reference: https://tedium.co/2026/09/10/matt-mullenweg-automattic-leave-absence/ > date created: 2026-09-10 > > > [!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: Automattic Minus Matt > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 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--automattic-minus-matt) ### 🔗 References (in-page) - [🗒️ Notes — timeline of the 2024–2026 dispute](#️-notes) - [✅ Action Items — WordPress governance and FAIR relevance](#-action-items) - [🔄 Refactor Appendix — atoms and permanent candidates](#-refactor-appendix--automattic-minus-matt) ## 📝 Summary - **What happened (reported fact).** Automattic's board suspended Matt Mullenweg from the CEO role and placed him on an involuntary leave of absence; the news broke via 404 Media, which Smith links and cites directly. CFO Mark Davies has temporarily taken over as CEO; Mullenweg keeps a board seat but not the CEO title. Per a Slack message Smith quotes from the 404 Media report, Mullenweg says he received the board's resolution 50 minutes before the meeting, asked repeatedly for time to have it reviewed by independent legal counsel, and was denied. - **What's Smith's interpretation, not fact.** Everything about *why* the board acted — that Mullenweg "forgot that he was simply a steward of a community," that he "couldn't stand the idea that someone else was making lots of money" off WordPress — is Smith's inferred motive, not a quoted or sourced statement from Mullenweg, the board, or Automattic. Smith says as much himself: there may be personal issues behind the scenes, he writes, that "we're not privy to," and "we don't know." The framing that this is deserved accountability — that it "would be completely reasonable for a board" to act on the damage — is Smith's editorial judgment, not a reported board rationale; Automattic hasn't published one in this piece. - **Why it matters.** This is Automattic's second public crisis tied to Mullenweg's conduct in two years. Smith ties the board action to a documented pattern he and other outlets reported earlier: severance offers to employees who didn't back the 2024 WP Engine fight (TechCrunch), a public feud with plugin developer Joost de Valk (Search Engine Journal), a stated freeze on WordPress core feature work (Tedium's own January 2025 piece), a block on WP Engine's access to the plugin directory that a court later forced Automattic to reverse (Tedium's December 2024 piece), and watermarking of an internal Automattic chat platform to trace leaks (404 Media). Each of those is a previously reported, separately sourced event — Smith is citing his own and others' prior reporting, not asserting new facts about this week's suspension. - **Key stakeholders.** Automattic's board (Mark Davies as acting CEO), Mullenweg himself (CEO-turned-board-member), WP Engine (the 2024 antagonist, not directly a party to this week's event), Automattic employees who lived through 2024's severance offer, and the wider WordPress open-source community whose governance has been entangled with one company's internal leadership fight. - **Risks and tradeoffs.** Smith names one directly: Automattic is privately held, so the piece can't rule out an undisclosed financial trigger behind the board's move — he flags this gap rather than papering over it. The larger risk he doesn't name explicitly but the facts imply: WordPress's open-source governance has no formal separation from Automattic's internal HR and legal disputes, so a boardroom conflict at one company becomes news the whole WordPress ecosystem has to interpret. - **Bottom line.** The reported facts here are narrow and sourced (suspension, temporary CEO swap, one quoted Slack message). The moral of the piece — asking whether it's "too late to get some of that goodwill back" — is Smith's opinion column wrapped around those facts, built on his and Tedium's own prior WP Engine coverage rather than new reporting of this specific event. ## 📖 Main Content Smith opens with a rhetorical either/or: is the bigger tragedy a creator losing control of their life's work, or a creator's grab for control alienating the community around it? He argues Mullenweg has now lived out both versions in two years. The first, per Smith's own September 2024 Tedium piece (linked in the article), was Mullenweg's WordCamp speech attacking WP Engine for allegedly under-contributing to WordPress despite its commercial success — a dispute that produced lawsuits from both sides and became, in Smith's description, one of the biggest tech stories before AI news displaced it. The second event, and this piece's news hook, is Automattic's board suspending Mullenweg from the CEO role this week and installing CFO Mark Davies as interim CEO — reported first by 404 Media, which Smith links and quotes. The one piece of direct, sourced testimony in the article is a Slack message Smith attributes to Mullenweg via the 404 Media report: he says the board gave him the removal resolution 50 minutes before the vote and refused his repeated requests for time to get independent legal review. Mullenweg keeps a board seat; Smith adds a dry aside that the only thing working in Mullenweg's favor there is Robert's Rules of Order — a joke, not a legal analysis, about how little procedural leverage a minority board member has. Beyond that quote, the article states plainly what it doesn't know: whether personal issues or an undisclosed financial problem — invisible because Automattic is private — factored into the board's decision. Smith is explicit about this gap rather than filling it with speculation dressed as reporting. What follows is Smith's argument, built from previously reported events rather than new facts: employees were offered severance if they didn't support Mullenweg's 2024 actions (TechCrunch); he publicly sparred with WordPress plugin author Joost de Valk (Search Engine Journal); he stopped WordPress core feature development, per Tedium's own January 2025 reporting; he blocked WP Engine's plugin-directory access, which a court forced Automattic to restore (Tedium, December 2024); and Automattic watermarked its internal P2 chat platform to trace leaks (404 Media). Smith uses this chain to argue the board's action, whatever its undisclosed trigger, isn't disproportionate given the pattern. That conclusion, and the motive Smith assigns to Mullenweg — protecting his own upside from WordPress's commercial success — is inference and opinion, not something Automattic, the board, or Mullenweg is quoted saying. **Terms worth defining:** "Leave of absence" here is involuntary and board-imposed, not a request Mullenweg made — distinct from a voluntary sabbatical. "P2" is Automattic's internal blogging-style chat/discussion platform, referenced only by the 404 Media link Smith cites for the watermarking story and not explained further in this piece. **Contested/uncertain:** the board's stated reason for the removal is not quoted or summarized anywhere in the piece — Smith infers it from the 2024–2025 pattern. Whether "personal issues" or financial pressure at the private company played a role is explicitly unknown, per Smith's own hedge. ## 🗒️ Notes - Framing device: what's the bigger tragedy — a creator separated from their work, or a creator's control-grab alienating the community around it? Smith argues Mullenweg has now supplied a real-world example of both. - Timeline point 1 (fact, linked to Tedium's own 2024-09-25 piece): Mullenweg's WordCamp speech against WP Engine, alleging insufficient contribution back to WordPress despite commercial success; both sides later sued. - Timeline point 2 (fact, linked to 404 Media): Automattic's board suspended Mullenweg as CEO this week and put him on leave; CFO Mark Davies is interim CEO; Mullenweg retains a board seat only. - Sourced quote (fact, via 404 Media, attributed to a Mullenweg Slack message): describes being given the removal resolution 50 minutes before the vote and denied time for independent legal review. - Smith's aside (opinion, not fact): a joke that the only thing working in Mullenweg's favor on the board now is Robert's Rules of Order. - Explicit epistemic hedge (Smith, not fact): unknown whether personal issues or a hidden financial problem — invisible because Automattic is private — factored into the board's move. - Pattern cited as background, each independently sourced: employee severance offers tied to loyalty on the WP Engine fight (TechCrunch); public feud with Joost de Valk (Search Engine Journal); WordPress feature-development freeze (Tedium, 2025-01-10); WP Engine plugin-directory block, later court-reversed (Tedium, 2024-12-14); P2 chat watermarking to trace leaks (404 Media). - Smith's interpretive thesis (opinion): Mullenweg forgot he was a steward of the community rather than its owner, and reacted to WP Engine's commercial success off WordPress with control-seeking behavior instead of acceptance. - Smith's verdict (opinion): the board's action reads as reasonable accountability given the pattern, though he immediately follows with an open question about whether the goodwill lost since 2024 can be recovered. - Structural note: after the Mullenweg analysis, the newsletter shifts into an unrelated "Interim Links" roundup (a Nathan Fielder/Elizabeth Holmes documentary, a *Super Mario Bros.* speedrun glitch, an Asahi Linux M3 release) and a sponsor mention for Computer Chronicles Revisited — standard Tedium newsletter structure, not part of the Mullenweg analysis proper. ## 📚 References - [404 Media — WordPress/Automattic CEO Matt Mullenweg put on leave of absence](https://www.404media.co/wordpress-automattic-ceo-matt-mullenweg-put-on-leave-of-absence/) — primary source for the suspension news and the quoted Slack message. - [Tedium, 2024-09-25 — the WordPress/WP Engine dispute's origin](https://tedium.co/2024/09/25/wordpress-wp-engine-open-web-negative-effects/) — Smith's own prior coverage of the WordCamp speech and fallout. - [TechCrunch — Automattic's 2024 severance offer to dissenting employees](https://techcrunch.com/2024/10/17/automattic-offered-employees-another-chance-to-quit-this-time-with-nine-months-severance/) - [Search Engine Journal — Mullenweg and Joost de Valk](https://www.searchenginejournal.com/wordpress-leader-mullenweg-silences-joost-de-valk/539387/) - [Tedium, 2025-01-10 — WordPress feature-development freeze](https://tedium.co/2025/01/10/wordpress-automattic-open-source-business-challenges/) - [Tedium, 2024-12-14 — the plugin-directory block and its court-forced reversal](https://tedium.co/2024/12/14/wordpress-wp-engine-reaction/) - [404 Media — P2 watermarking to trace leakers](https://www.404media.co/automattic-wordpress-p2-watermark-leakers/) ## 🗣️ Paraphrase Smith frames Matt Mullenweg's week as proof that the same instinct — reflexive control over something he built — can produce two different kinds of wreck. Two years ago it was Mullenweg turning a contract dispute with WP Engine into a fight that split the WordPress community, cost people their jobs, and dented his reputation. This week it's Automattic's own board applying similar logic back onto him: a sudden resolution, a denied request for legal review, and a demotion to a board seat he can't easily use. Smith is careful to mark the limits of what he actually knows — the board's stated reasoning isn't quoted anywhere in his piece, and he says outright that undisclosed personal or financial factors might be in play at a company that, being private, doesn't have to say. What he does have is a documented pattern from his own and other outlets' reporting: loyalty-tested severance offers, a public fight with a plugin developer, a stalled WordPress roadmap, a reversed plugin-directory block, and internal watermarking to catch leakers. Smith uses that pattern to argue the board's move isn't an overreaction, even without knowing its specific trigger — but that argument, and the motive he assigns to Mullenweg (protecting his own financial upside from WP Engine's success), is his inference, not something anyone at Automattic is quoted saying. ## 📰 Newsletter Automattic's board suspended Matt Mullenweg from the CEO role this week — first reported by 404 Media — and installed CFO Mark Davies as interim chief while Mullenweg keeps a board seat only. Ernie Smith's Tedium column ties it to the pattern from the 2024 WP Engine fight: severance offers tied to loyalty, a feud with plugin developer Joost de Valk, a stalled core-feature roadmap, a plugin-directory block a court forced Automattic to reverse, and internal chat watermarking to trace leaks. Worth flagging for anyone tracking WordPress governance: the board's actual stated rationale isn't public in this piece — Smith's read that this is deserved accountability is his opinion, built on reported history rather than a released board statement. If you follow FAIR or independent WordPress governance efforts, this is a live example of exactly the single-point-of-failure risk that work exists to reduce. ## ✅ Action Items #### DevRel - Not applicable in the classic advocacy/education sense — but any WordPress-facing DevRel messaging this week should avoid speaking for Automattic's board or Mullenweg's intentions, since neither's stated rationale is public in this source. #### OSPO - **Policy & Governance:** a live case study for any org drafting a founder-succession or leadership-crisis clause in an open-source governance charter — Automattic's board acted without (per this piece) a published rationale, which is itself a governance-transparency gap worth naming in WPOCC or FAIR policy work. - **Security Management:** the P2 watermarking-to-catch-leakers precedent (404 Media, cited in this piece) is worth a policy review for any org handling internal dissent — watermarking traces leaks but also chills legitimate internal disagreement; worth weighing against whistleblower-protection norms. #### Community - **Maintainers/Contributors:** the WordPress feature-freeze cited here (Tedium, 2025-01-10) is a concrete, sourced example of one company's internal conflict stalling the open-source roadmap — useful evidence for arguing WordPress core development needs decision rights that don't route entirely through Automattic's CEO. - **Ecosystem:** the reversed plugin-directory block (Tedium, 2024-12-14) is a precedent worth citing in any argument for contractual or technical guarantees that plugin-directory access can't be unilaterally revoked by one company again. #### WordPress - **Meta:** the .org plugin directory's dependence on Automattic-controlled infrastructure is the direct mechanism behind the 2024 block this piece references — a structural question, not just a personnel one, and it doesn't resolve just because Mullenweg is on leave. - **Core Program Team:** worth a retrospective on how a CEO-level personnel dispute produced a documented feature freeze, and what decision-making structure would prevent one person's leave of absence (or presence) from having that much leverage over the release cycle. #### The WPOCC - This event is squarely relevant to The WPOCC's remit: it's a real-time illustration of what happens when WordPress project governance and one company's internal HR/legal dispute aren't separated. Worth logging as a dated example in any governance-case-study material. #### FAIR - **Technical independence:** the plugin-directory block this piece references (2024, court-reversed) is exactly the single-point-of-control risk FAIR's local-metadata/provenance work is meant to reduce — this week's news is fresh, concrete evidence for that case, not just a hypothetical. ## 🧪 Hypotheses - H1: Automattic's board suspended Mullenweg over the cumulative reputational/financial cost of the 2024–2025 WP Engine conflict, not a single new trigger. - H2: The board's procedural denial (50-minute notice, no time for outside legal counsel) reflects urgency the board perceived but hasn't disclosed publicly, rather than mere hostility toward Mullenweg. - H3: Automattic's private ownership status is masking a financial motive for the board's action that would be visible if the company were public. - H4: The 2024 WordPress feature freeze and plugin-directory block materially damaged Automattic's standing with hosting partners and contributors in a way the board weighed in its decision. - H5: WordPress core development velocity will measurably change (up or down) during Mullenweg's leave, testable against public Trac/GitHub activity logs. ### 📊 Methodology - For H1/H3: this would require access Smith doesn't have and doesn't claim — internal board minutes or Automattic financials, neither public for a privately held company. Absent that, the honest methodology is tracking follow-up reporting (404 Media, The Verge, WP Tavern) for a published board rationale. - For H2: compare the 50-minute-notice claim against Automattic's own bylaws or board procedures, if ever disclosed, to assess whether the notice period was standard or unusual. - For H4: pull WordPress.org plugin/theme submission and update-frequency data before and after the 2025-01-10 freeze Tedium reported, and hosting-partner public statements (e.g., WP Engine, Bluehost, other major hosts) across the same window. - For H5: track wordpress-develop commit velocity and Trac ticket resolution rate for the weeks before and after this leave-of-absence announcement. ### ❓ Questions - Has Automattic's board or Mullenweg published any rationale for the suspension since this piece was written, and does it match or contradict Smith's inferred "pattern of damage" explanation? - What, specifically, is the "resolution" Mullenweg says he was given 50 minutes to review — full text hasn't surfaced in this piece or, as far as this note's source shows, elsewhere cited here. - Does Mullenweg's remaining board seat carry any practical power, or is Smith's Robert's Rules of Order joke accurate that it's procedurally close to none? - Is there a published or leaked account of the board's actual vote count and dissenting/supporting members? ### 🔮 Future Research - No comparison in this piece to how other founder-led open-source companies have handled a founder's board-level removal — a precedent survey would sharpen whether Automattic's board acted unusually fast or slow. - No assessment here of WP Engine's own position or statement on this specific event — the piece treats WP Engine as 2024 backstory, not a party to this week's news. - No tracking, in this source, of Automattic employee reaction to the leave of absence, unlike the detailed 2024 severance-offer story it cites. ### 💡 Implications - **Practice.** Any WordPress agency or hosting partner relying on Automattic's roadmap commitments should treat near-term core development timelines as unsettled until governance stabilizes — the piece's own cited 2025 feature freeze shows this isn't hypothetical. - **Policy/governance.** A concrete, sourced argument for separating WordPress project governance decisions (plugin directory access, core feature prioritization) from Automattic's internal executive disputes. - **Security.** The P2 watermarking precedent (404 Media) raises a real internal-trust question for any org considering similar leak-tracing tooling — balance against chilling effects on legitimate dissent. - **Education.** None named directly in the source; the piece is opinion commentary, not instructional content. - **Funding models.** Automattic's private-company status is cited by Smith as the specific reason financial motive can't be assessed — a concrete argument for why open-source projects this dependent on one private company's health carry an information-asymmetry risk for the community. ### 🧠 Learning Styles Assessment - **Reading level estimate:** Flesch-Kincaid Grade Level ≈ 10, from a heuristic word/sentence/syllable count over the full captured HTML (roughly 57 sentences, 1,109 words, including sponsor and interim-links content; Reader's own metadata lists the article body at 1,079 words). Register is column/op-ed: short paragraphs, first-person asides, parenthetical jokes. #### 👀 Visual learners - **Present:** one photo of Mullenweg at WordCamp Europe with a sourced Flickr caption; a sponsor image/figure for Computer Chronicles Revisited; an embedded YouTube video (an unrelated Mario speedrun) in the Interim Links section. - **Improve:** a simple annotated timeline graphic (WordCamp speech → lawsuits → feature freeze → plugin block → leave of absence) would help readers who don't already know the 2024–2026 backstory Smith assumes. #### 🔊 Aural learners - **Present:** none — no audio or podcast version referenced for this piece. - **Improve:** a short audio read-through of the newsletter isn't present here. #### 🗣️ Verbal learners - **Present:** plain-language framing of the dispute (a "my-way-or-the-highway fork in the road") and a direct definitional aside about what a board-imposed leave of absence implies versus a voluntary departure. - **Improve:** a one-line glossary distinguishing "leave of absence" (board-imposed, this piece) from "resignation" or "sabbatical" would help readers unfamiliar with corporate-governance terms. #### 🧩 Kinesthetic learners - **Present:** none — this is commentary, not a how-to; no exercises or reproducible steps. - **Improve:** not a natural fit for this content type. #### 🧠 Logical learners - **Present:** a clear chronological chain of cited events (2024 speech → lawsuits → severance offers → de Valk feud → feature freeze → plugin block → watermarking → this week's suspension) that functions as an implicit timeline argument. - **Improve:** an explicit dated timeline table would make the causal argument (pattern → board action) easier to audit than the prose form does. #### 🧑‍🤝‍🧑 Social learners - **Present:** none — no comments, discussion prompts, or community engagement shown in the captured content; the piece ends with a share link and a sponsor plug. - **Improve:** an explicit prompt inviting WordPress community members to weigh in would extend this into a discussion piece rather than a closed opinion column. #### 🧘‍♀️ Solitary learners - **Present:** the piece works as a standalone read; no external context is strictly required to follow the argument, since Smith links his own prior coverage for background. - **Improve:** none needed — self-contained via its own links. #### 🌿 Naturalistic learners - **Present:** none — no ecological or systems-in-nature framing. - **Improve:** not a natural fit for this content. ### 📊 Accessibility Assessment #### Screen reader semantics - **Present:** the article's headings are minimal (one `<h2>` used only for the page-description metadata, one `<h5>` for the sponsor line) — there's no real heading structure segmenting the body into sections for a screen-reader user to navigate by. - **Improve:** add `<h2>`/`<h3>` section breaks (e.g., "The suspension," "The pattern," "What we don't know") so screen-reader users can jump between sections instead of reading linearly (WCAG 2.2 SC 1.3.1, 2.4.6). #### Keyboard navigation - **Not observed** — no interactive UI beyond standard links and the embedded video; nothing in the captured markup suggests a keyboard trap, but this wasn't visually verified live on the page (SC 2.1.1, 2.4.3 would apply to any custom widgets not visible in this capture). #### Contrast and readability - **Not observed** — text/background contrast isn't visible in the captured HTML; flag for direct visual review before treating as compliant (WCAG 2.2 SC 1.4.3). #### Text resizing and reflow - **Not observed** — no reflow-relevant markup captured; standard article layout is implied but not visually confirmed (SC 1.4.4, 1.4.10). #### Media and captions - **Present:** two images carry `alt` text, but one (`alt="mullenweg_wordcamp.jpg"`) is just the filename, not a description of the photo — this fails WCAG 2.2 SC 1.1.1's requirement for text alternatives that serve an equivalent purpose. - **Present (concern):** the embedded YouTube video is set to autoplay, which is an accessibility and cognitive-load concern — autoplaying media needs a way to pause, stop, or mute within the first few seconds it plays (SC 1.4.2 Audio Control; SC 2.2.2 Pause, Stop, Hide). - **Improve:** replace the filename alt text with a real description ("Matt Mullenweg speaking at WordCamp Europe"); remove or gate the video's autoplay behind a user click. #### Forms and interactions - **Not applicable** — no forms present in the captured content; the share and sponsor links are plain anchors. #### Standards reference - Gaps map to WCAG 2.2 AA: 1.1.1 (non-descriptive alt text), 1.3.1/2.4.6 (missing heading structure), 1.4.2/2.2.2 (autoplaying embedded video). Contrast, reflow, and keyboard items require live visual review this capture can't confirm. ### 🌍 DEIB Assessment #### Cultural breadth - **Present:** none beyond the single US/WordPress-industry subject matter; no international framing beyond WordCamp Europe being mentioned as a location. - **Improve:** not a natural fit — the piece is narrowly about one US company's board action; forcing cultural-breadth content would be padding. #### Inclusive language - **Present:** plain, direct, non-idiomatic language for the most part; a few casual Americanisms (a "my-way-or-the-highway" fork in the road) that could read as informal to non-native English readers but aren't exclusionary. - **Improve:** none material needed. #### Neurodiversity support - **Present:** short paragraphs and a clear (if unlabeled) chronological structure aid scanning. - **Improve:** the lack of headings (also flagged in Accessibility) hurts predictability for readers who rely on structural chunking; adding section headers would help here too. #### Representation - **Present:** the piece centers exclusively on Mullenweg (male) and references Mark Davies (male) as interim CEO and Joost de Valk (pronouns not stated in source — using they/them per this note's own convention) as a past antagonist; no other individuals are named or quoted. - **Improve:** not really fixable within this piece's scope — it's a story about a specific boardroom event involving specific named individuals — but worth noting the source names no women or non-binary figures in a story about WordPress governance, a project with a broader contributor base than this narrow cast suggests. #### Psychological safety - **Present:** Smith names emotional/reputational stakes plainly — Mullenweg's "good-guy reputation" being tarnished — without dismissiveness; the tone toward Mullenweg is critical but not derisive. - **Improve:** none needed; no sensitive content requiring a warning. ### ✅ Logical Validity #### Strong reasoning - **Evidentiary chain reasoning (fact-grounded):** Smith's argument that the board's action isn't disproportionate rests on five independently sourced prior events (severance offers, the de Valk feud, the feature freeze, the plugin-directory block, the P2 watermarking) — each individually linked to a named outlet's reporting. This is a legitimate inductive case: repeated, separately documented instances of the same control-seeking pattern support treating the board's action as consistent with that pattern, even without a published board rationale. - **Explicit epistemic hedging (a mark of good reasoning, not a flaw):** Smith states directly what he doesn't know — that there may be personal issues behind the scenes he isn't privy to, and that he doesn't know — rather than filling the gap with unsupported claims. Worth naming as strong practice, since the rest of the piece could easily have overreached here and didn't. #### Fallacies - **False dilemma (opening frame).** Location: the lead question posing the bigger tragedy as either a creator losing control of their work, or a creator's control-grab alienating the community. Why it's weak: this presents exactly two mutually exclusive framings as the available options, when a reader could reasonably hold that neither framing captures it — the tragedy could be structural (that WordPress governance has no separation from one company's internal disputes) rather than personal to Mullenweg either way. Fix: pose it as one of several possible framings rather than an either/or. - **Unsupported motive attribution (mind-reading).** Location: the sentence attributing Mullenweg's conduct to not being able to stand the idea of someone else profiting from the project he chose to open source. Why it's weak: this assigns a specific psychological motive to Mullenweg with no cited interview, statement, or document establishing it — it's presented in the same declarative register as the piece's sourced facts, which risks a reader conflating inference with reporting. Fix: mark it explicitly as Smith's read rather than stating it as the reason. - **Loaded comparison (rhetorical, minor).** Location: the description of Mullenweg as a leader many believed held a Zuckerberg-like iron grip on his company. Why it's weak: invoking Mark Zuckerberg imports a separate set of associations (dual-class voting control, effective unremovability) that doesn't describe Mullenweg's actual situation — Mullenweg was in fact removable, which is the article's own point, making the comparison somewhat self-undermining. Fix: drop the comparison or make the contrast explicit (unlike Zuckerberg, Mullenweg turned out to be removable). #### Tone of voice - First-person, conversational op-ed register with dry asides and parenthetical jokes about Mullenweg's remaining board leverage; critical of Mullenweg throughout but not personal or derisive; closes on an open, slightly wistful question rather than a hard verdict. ### 🛡️ DARVO Analysis DARVO (Deny, Attack, Reverse Victim and Offender) describes a rhetorical move by a person accused of wrongdoing. It doesn't cleanly apply to this piece as captured, for two reasons. First, the only extended verbatim words from Mullenweg himself are a single Slack message describing a procedural grievance — denied time for legal review. Smith doesn't quote Mullenweg denying any specific accusation or attacking a named accuser, so the Deny and Attack elements simply aren't present in what this source captures. Second, the "accused party" framing is ambiguous here: is Mullenweg the accused (of mismanagement, per the board's unstated rationale), or is the board the one whose action needs justifying (per Smith's own admission that its rationale isn't public)? The piece doesn't resolve that, and forcing a DARVO read onto a single procedural complaint would overstate what the quote shows. What the quote does show, worth naming directly: Mullenweg's Slack message positions him as procedurally wronged (short notice, denied legal review) at the exact moment he's being scrutinized for prior conduct — a genuine instance of victim-framing language, but partial (only the reverse-victim element, and only faintly) rather than the full three-part DARVO pattern. Smith doesn't amplify or challenge this framing; he simply reports the quote and moves on to his own independent argument about the 2024–2025 pattern. The stronger rhetorical move in this piece belongs to Smith, not Mullenweg: Smith's own unsupported motive attribution (flagged above under Fallacies) does more argumentative work in the piece than anything quoted from Mullenweg. ## 🎯 Conclusion The confirmed facts in this piece are narrow: Automattic's board suspended Mullenweg as CEO, installed Mark Davies as interim CEO, and Mullenweg says — via a Slack message reported by 404 Media — he was denied time for outside legal review before the vote. Everything else, including why the board acted, whether it's deserved, and whether Mullenweg forgot his role as steward rather than owner, is Ernie Smith's interpretation, built on a real and independently sourced pattern of 2024–2025 events but not on any disclosed board rationale. Readers should treat the piece as informed opinion commentary grounded in prior reporting, not as a report of Automattic's stated reasons. Practical next step: track 404 Media, WP Tavern, or Automattic's own channels for a published board rationale, and treat any claim about Mullenweg's motive — Smith's included — as inference until one surfaces. ## 🔄 Refactor Appendix — Automattic Minus Matt > Density: 3 Literature atoms (H4), 1 Permanent candidate (H4). > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > Atomicity: one declarative sentence per atom. ### 📚 Literature Atoms (H4) #### [H1] Mullenweg says board denied him time for legal review > [!quote] > I received the resolution 50 minutes before the meeting start, and requested repeatedly for time to have it reviewed by independent legal counsel, even a few hours, which was denied, **Context & use**: - Attributed to a Mullenweg Slack message, reported by 404 Media and quoted by Smith as the piece's one direct sourced testimony. - The only verbatim account in the article of what actually happened procedurally at the board meeting — everything else about motive is inference. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H2] Smith frames the board's action as deserved accountability > [!quote] > Why are we letting this guy run our business into the ground, **Context & use**: - Smith's own imagined framing of what a reasonable board would ask itself, immediately followed by a decision to take action — not a quote from any actual board member. - Load-bearing for Smith's verdict that the suspension isn't disproportionate given the 2024–2025 pattern he cites. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H3] Smith argues Mullenweg forgot he was a community steward > [!quote] > And seemingly overnight, he forgot that he was simply a steward of a community. **Context & use**: - Smith's core interpretive thesis about Mullenweg's conduct since 2024 — presented as narrative fact but is unsourced motive/character judgment, not a quoted admission. - Directly precedes the unsupported motive-attribution sentence flagged in Logical Validity. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Founder control over open source needs a governance backstop **Claim** (Courtney's voice): A single founder's unilateral control over an open-source project's infrastructure — plugin directories, core roadmap — is a governance risk that only becomes visible when that founder's conduct, not the code, becomes the crisis. **Evidence pointer**: [[#H2]] **Scope & conditions**: Holds specifically where a company (not a foundation or elected body) controls the project's critical infrastructure — the 2024 plugin-directory block and 2025 feature freeze cited in this piece are the concrete mechanism, not a hypothetical. **Links** (≥1 with annotation): - [[FAIR governance]] — because applies-in: FAIR's local-metadata/provenance work exists specifically to reduce this single-point-of-control risk. - [[WPOCC governance case studies]] — because evidence-for: this event is a dated, sourced example to cite in governance-separation arguments. **Optional**: `status: seedling` <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Track whether Automattic or the board publishes a stated rationale for the suspension, and whether it matches or contradicts Smith's inferred "pattern of damage" explanation. — https://tedium.co/2026/09/10/matt-mullenweg-automattic-leave-absence/ #xref - [F2] Check whether WP Tavern, The Verge, or 404 Media follow-up coverage adds sourced detail (board vote count, dissenting members, full resolution text) beyond what this piece captures. — #xref ### → Things 3 (max 2 actions) - [ ] Check 404 Media and WP Tavern for follow-up reporting on Automattic's board rationale before citing this event as settled in any governance writeup — context #verification #things - [ ] Log this event as a dated case study in FAIR/WPOCC governance materials on single-company control over WordPress infrastructure — context #wpocc #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Automattic Minus Matt.md|Automattic Minus Matt by Ernie Smith]] ## Highlights - Why are we letting this guy run our business into the ground, ([View Highlight](https://read.readwise.io/read/01m25w21qnhdrvhswanc12c577)) - Note: Smith's framing of the board's implied reasoning — his inference, not a quoted source. - Tags: opinion, automattic