Matt Mullenweg Apparently Back in Charge at Automattic  🔗 **Source:** [Matt Mullenweg Apparently Back in Charge at Automattic](https://www.searchenginejournal.com/matt-mullenweg-apparently-back-in-charge-at-automattic/589251/) > [!note]+ Document Notes > tags: [automattic, matt-mullenweg, corporate-governance, corporate-communications, sourcing-discipline] > author: Roger Montti > source: Search Engine Journal > reference: https://www.searchenginejournal.com/matt-mullenweg-apparently-back-in-charge-at-automattic/589251/ > date created: 2026-10-02 11:01 > > > [!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: Matt Mullenweg apparently back in charge at Automattic > <!-- 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--matt-mullenweg-apparently-back-in-charge-at-automattic) This note replaces an earlier short note on the same article. Paragraph labels like ¶5 are the pipeline's extraction labels, not part of the original. Facts about other outlets' reporting come from that earlier note, which checked them against TechCrunch and others. This pass had no network access and read only the captured text, so those facts are labeled "per the earlier note" and aren't re-verified here. ## 📝 Summary - **What happened.** Search Engine Journal (SEJ) published a short news report by Roger Montti, saved to Reader on 2026-09-13. It says an Automattic spokesperson confirmed that Matt Mullenweg is back in charge of Automattic (¶1). It recaps the board's Wednesday, September 9 move to put Mullenweg on paid leave and make CFO Mark Davies the CEO (¶3), Mullenweg's Slack posts on Friday, September 11 (¶5, ¶6), a post of support from Mary Hubbard (¶7, ¶8), and a second official statement issued Saturday, September 12 (¶11, ¶18). - **The claim.** The article's argument is about tone. It calls the first statement formal, third-person and "officially vetted" (¶14), calls the second informal, persuasive and a single run-on sentence (¶16, ¶17), and asks whether Mullenweg dictated or wrote the second (¶19). - **Why it matters.** The article is a case study in how a news report mixes three layers: facts credited to named sources, facts stated in the outlet's own voice with no source, and the outlet's interpretation. This note separates them in Main content. - **Key stakeholders.** Mullenweg; Automattic and its board; Mark Davies (named as the CEO the board installed, ¶3); Mary Hubbard (named, ¶7); Automattic employees ("Automatticians," ¶9) including @jamesgrierson (¶21); TechCrunch (named, ¶6). - **Risks and tradeoffs.** The captured text omits the blockquotes that hold both official statements (¶3, ¶11, ¶18 each end in a colon with nothing after it), so the statements the article analyzes can't be read in the capture. The article's own hedges ("apparently," "reads as if," "maybe") sit beside flat assertions, and the headline hedges while the first paragraph doesn't. - **Bottom line.** Opinion-tinted news analysis. It states one checkable fact in its first sentence (a spokesperson confirmed the return, ¶1) without naming who spoke to whom or linking the primary report. Its authorship question (¶19) rests on style alone and gets no answer from the article. Source type: news report with commentary, about 590 words in the capture. The earlier note counted 770 words on the live page, which includes the missing blockquotes. The captured text shows no commercial relationship to the subject. SEJ's own prior coverage is linked once (¶3 link). ## 📖 Main content **Scope of this reading.** All 23 paragraphs were read. The sections below separate what the article attributes to a named source, what it says in its own voice, and what it infers. Link claims were checked against the link list (three entries, listed in References). ### Timeline as the article gives it | Date in article | Event | Who says so in the text | Link in the link list | |---|---|---|---| | Wed, Sept 9 | Board puts Mullenweg on paid leave "for unspecified reasons" and puts Davies in as CEO (¶3) | SEJ, own voice | Yes, to an SEJ article whose anchor reads "Automattic put Matt Mullenweg on paid leave" | | Wed, Sept 9 | Mullenweg "apparently" got fifty minutes' notice and was refused a delay for an attorney's review (¶3) | SEJ, hedged, no source named | No | | Wed, Sept 9 | Automattic issued a three-sentence statement (¶3, ¶14) | Automattic; text not in capture | No | | Not dated | Mullenweg "took control" of the Slack workspace, removed admins, announced he was back (¶5) | SEJ, own voice, no source named | No | | Fri, Sept 11 | Mullenweg posts to Slack claiming control; "unsupported by an official statement" (¶6) | "it was reported," then TechCrunch's headline (¶6) | Yes, anchor "reported" to a TechCrunch URL dated 2026/09/11 | | Not dated | Mary Hubbard posts support (¶7, ¶8) | Hubbard, by tweet | Yes, anchor "tweeted" to an x.com status URL | | Not dated | Automatticians tweet support; Mullenweg reposts each one (¶9) | SEJ, own voice, no tweets linked | No | | Sat, Sept 12, "just after 5 PM EST" | Second official statement (¶11, ¶18) | Automattic; text not in capture | No | The weekdays check out: September 9, 11 and 12, 2026 fall on Wednesday, Friday and Saturday. ### Attribution ledger: named sources versus the outlet's own voice **Credited to a named source:** - TechCrunch's headline, quoted in ¶6: "Matt Mullenweg tells (trolls?) Automattic staff, saying he's back in control after CEO ouster." The article quotes only the headline. The report's contents aren't summarized, so the article relies on the headline's uncertainty ("trolls?") to carry the point that control was unclear. - Mary Hubbard's tweet (¶8), quoted in full, with a link. The article gives her title as Executive Director of WordPress (¶7). Per the earlier note, TechCrunch gives it as Executive Director of WordPress.org. - @jamesgrierson's tweet (¶22), quoted in full. No link in the captured markup. **Stated in the outlet's own voice with no source named in the text:** - The spokesperson confirmation that opens the piece (¶1). The text doesn't say who received it, by what channel, or where it was published. - The board action, the Davies appointment and the three-sentence statement (¶3), apart from the link to SEJ's earlier article. - The 50-minute notice and the denied delay (¶3). The text hedges with "apparently" but names no source. Per the earlier note, WP Tips reported this as Mullenweg's own account. - That Automattic "had failed to remove" Mullenweg from the Slack workspace, that he "took control," and that he "removed admins" (¶5). Per the earlier note, TechCrunch reported the admin removals citing multiple sources. "Failed to remove" is an inference by SEJ. - That "numerous Automatticians" tweeted support and Mullenweg reposted "each post" (¶9). The sample is one tweet (¶22). - That the reposts were "drowning out the tweets that supported his ouster" (¶9). No ouster-supporting tweets are linked or counted. **The outlet's interpretation, presented as analysis:** - The second statement "differs greatly" from the first "in tone, word choice, and structure" (¶12). - The first statement is "formal, in the third-person and in the language of an officially vetted announcement" (¶14). - The second "sounds like a personal assertion" and "invites the reader" to verify online (¶16). - "Most strangely" the second is a single run-on sentence that is persuasive with "an argumentative edge" (¶17). - The question of authorship (¶19) and the opening claim that the statement "reads as if it were dictated or authored by Mullenweg himself" (¶1). ### Hedge inventory | Hedge | Where | What it covers | |---|---|---| | "Apparently" (headline) | Title | The claim that Mullenweg is back in charge | | "it appeared that Mullenweg had gained access to the Automattic Slack account but not Automattic itself" | ¶1 | The days between Sept 9 and Sept 12 | | "reads as if it were dictated or authored by" | ¶1 | Authorship of the Saturday statement | | "apparently given fifty minutes' prior notification" | ¶3 | Notice before the board meeting | | "perception that maybe Matt was in control of Automattic's Slack workspace but not Automattic itself" | ¶9 | The state of control after Hubbard's tweet | | "effectively drowning out" | ¶9 | Effect of reposting; no measure given | | Question mark | ¶19 | Authorship, left unanswered | The hedges cluster around the two points the article can't source: the 50-minute notice and the authorship of the Saturday statement. The headline hedges ("apparently back in charge") while ¶1 says a spokesperson "has confirmed" the same fact. Those two framings of one claim are in tension, and the article doesn't reconcile them. ### What the capture leaves out - **Both official statements.** ¶3 ends "issued the following three-sentence statement:" and ¶11 ends "was issued just after 5 PM EST on Saturday, September 12:" with nothing after the colon. ¶18 ends "Here's the second communication sent on Saturday:" the same way. Per the earlier note, the live page holds these as blockquotes that Reader's saved copy dropped. The statements are the evidence for ¶12 to ¶17, and a reader of the capture can't check the comparison. - **The featured image.** ¶23 is a caption only: "Featured Image/Screenshot Keynote – Fireside Chat with Ma.tt Mullenweg." The earlier note found the live page's caption says "WordCamp USA," while the event's name is WordCamp US. That naming point comes from the earlier note and isn't visible in this capture. - **Embedded tweets.** ¶8 and ¶22 are the tweet text only, with no handle on Hubbard's, no date and no engagement data. ### Earlier note's claim check, carried forward The earlier note checked the live page against TechCrunch, WP Tips and others. Its verdicts, unverified here: | SEJ claim | Earlier note's finding | Verdict | |---|---|---| | A spokesperson confirmed the return | TechCrunch (Sarah Perez, 2026-09-12 23:25 UTC) says a spokesperson emailed the statement "just after 5 PM ET on Saturday evening" | Matches; SEJ doesn't say who received it or link the report | | Paid leave on Sept 9, Davies as CEO | TechCrunch matches; says "unknown reasons" | Matches | | 50 minutes' notice, denied delay | WP Tips: this is Mullenweg's own Slack account | Attribution dropped; "apparently" is the main hedge | | "Failed to remove" from Slack; admins removed | TechCrunch confirms the admin removals, citing multiple sources | Removal matches; "failed to remove" is inference | | Hubbard post | Text matches the vault copy; title shortened | Matches | | Reposts "drowning out" ouster-supporting tweets | TechCrunch reports reposts; no ouster-supporting posts linked | Reposting matches; "drowning out" unmeasured | | "5 PM EST" | TechCrunch says ET; September is daylight time | Time matches; the "EST" label is off | | Statement text | Identical to TechCrunch's quote | Matches (not visible in the capture) | | Caption "WordCamp USA" | The event is WordCamp US | Minor naming error | | @jamesgrierson post | Not linked | Unverified | The "EST" point is checkable from the calendar alone: Eastern daylight time runs through early November, so a Saturday in September is EDT. ## 🗒️ Notes #### 📄 ¶1 Lede - An Automattic spokesperson "has confirmed" Mullenweg is back in charge (¶1). No name, channel or link follows. - The sentence after it frames the previous days: it "appeared" Mullenweg had Slack access but not the company. - The paragraph closes on the article's real point: the statement "reads as if it were dictated or authored by Mullenweg himself." #### 📄 ¶2-¶3 Catching up: the Sept 9 board action - Wednesday, September 9: the board puts Mullenweg on paid leave "for unspecified reasons" and names CFO Mark Davies as CEO (¶3). - Mullenweg "was apparently given fifty minutes' prior notification" and his request for a delay to have an attorney review the move was denied (¶3). Hedged, unsourced in the text. - The paragraph says Automattic issued a three-sentence statement and ends on a colon. The statement isn't in the capture. #### 📄 ¶4-¶6 Slack and the Sept 11 reports - Heading ¶4 sets up the Slack episode. ¶5 says Automattic "had failed to remove" Mullenweg from the Slack workspace, and he "took control of it, removed admins, and announced he was back in control." - ¶6: on Friday, September 11 it "was reported" that he was posting to Slack claiming control, "unsupported by an official statement from Automattic itself." The linked anchor is "reported," pointing at TechCrunch. - The article quotes only TechCrunch's headline, which carries "(trolls?)" and frames control as uncertain. #### 📄 ¶7-¶9 Hubbard's tweet and the employee posts - ¶7 and ¶8: Mary Hubbard, titled Executive Director of WordPress, tweets relief at seeing Mullenweg "return as CEO," calls Automattic the largest financial contributor to the WordPress project, and says Mullenweg has her support. - ¶9 says Hubbard's tweet "led to a perception that maybe" Mullenweg controlled Slack but not the company. The causal link from tweet to perception isn't sourced. - Also in ¶9: "Numerous Automatticians" tweeted support and Mullenweg reposted each one, "effectively drowning out" tweets that backed his ouster. No count and no links. #### 📄 ¶10-¶11 Statement from Automattic - Heading ¶10, then ¶11: "An official statement was issued just after 5 PM EST on Saturday, September 12." The colon leads to a blockquote the capture lost. #### 📄 ¶12-¶17 Comparing the two statements - ¶12: the second statement differs "greatly" from the first in tone, word choice and structure. - ¶14: the first is three sentences covering Mullenweg's status, his successor, and full board confidence. This is the only description of the first statement's content in the capture. - ¶16: the second is informal, reads as a personal assertion, and invites the reader to go online to verify it instead of stating the fact. - ¶17: the second is a single run-on sentence that is persuasive with "an argumentative edge." #### 📄 ¶18-¶19 The second communication and the question - ¶18 introduces the Saturday statement. The text after the colon is missing. - ¶19 asks the authorship question and gives no answer. #### 📄 ¶20-¶22 Responses - Heading ¶20. ¶21 says "Many from Automattic" posted supportive tweets, "like this one from @jamesgrierson." - ¶22 quotes one tweet: a 10-year contributor and sponsor relationship while at Bluehost, then 10 years as a coworker at Automattic, and a bright outlook for Automattic and WordPress. No link in the captured markup. #### 📄 ¶23 Featured image caption - A caption for the featured image: a keynote fireside chat with Mullenweg. The image itself and its alt text aren't in the capture. ## 📚 References The link list has three entries. Each is cited here by URL. - [SEJ, "Automattic put Matt Mullenweg on paid leave"](https://www.searchenginejournal.com/wordpress-co-founder-matt-mullenweg-ousted-from-automattic/589009/): SEJ's own earlier article on the Sept 9 board action. It is linked from the anchor "Automattic put Matt Mullenweg on paid leave." The anchor text reads like the ¶3 phrase "put Matt Mullenweg on paid leave," so the link most likely sits there (inference; the list doesn't say which paragraph). - [TechCrunch, Sept 11 report](https://techcrunch.com/2026/09/11/matt-mullenweg-tells-automattic-staff-in-slack-hes-back-in-control-after-ceo-ouster/): linked from the anchor "reported" (¶6). The article quotes its headline. - [Mary Hubbard's tweet](https://x.com/4thhubbard/status/2098489405874823179?s=20): linked from the anchor "tweeted" (¶7). The article quotes the tweet text in ¶8. Claims with no link in the captured markup: the spokesperson confirmation (¶1), the 50-minute notice (¶3), the Slack takeover and admin removals (¶5), the employee posts and reposts (¶9), both official statements (¶3, ¶11, ¶18), and @jamesgrierson's tweet (¶22). **Primary report on the Saturday statement (per the earlier note, not linked by SEJ):** TechCrunch, "Automattic confirms Mullenweg has returned as CEO after attempted ouster by board," 2026-09-12: https://techcrunch.com/2026/09/12/automattic-confirms-mullenweg-has-returned-as-ceo-after-attempted-ouster-by-board/. The earlier note puts it about 22 hours before SEJ published. **Details in that report that SEJ leaves out (per the earlier note):** - Mullenweg posted "I'm a pirate now" in Slack. - Automattic didn't respond to reports about board member Toni Schneider stepping down. - TechCrunch hears the board's composition "still may be in flux." **Earlier notes on this story in the vault:** - [[3. Resources/Readwise/Articles/Matt Mullenweg Tells Automattic Staff in Slack He's Back in Control After CEO Ouster TechCrunch|TechCrunch, Sept 11: Mullenweg tells staff he's back in control]] - [[3. Resources/Readwise/Articles/Automattic’s Matt Mullenweg Claims He’s Back 'In Control'|404 Media: Mullenweg claims he's back "in control"]] - [[3. Resources/Readwise/Articles/Matt Mullenweg Reportedly Returns as Automattic CEO Two Days After Getting Booted|The Verge: Mullenweg reportedly returns as CEO]] - [[3. Resources/Readwise/Articles/Matt Mullenweg Put on Leave as Automattic CEO|WP Tips: Mullenweg put on leave]] - [[3. Resources/Readwise/Articles/Mullenweg Back at Automattic Helm After Board Standoff Ends in 48 Hours - Northeast Times|Northeast Times: aggregation of the same week]] - [[3. Resources/Readwise/Tweets/I'm Relieved and Pleased to See Matt Mullenweg Return As...|Mary Hubbard's post]] - [[3. Resources/Readwise/Tweets/Founder Advice If You Don't Have a Coup Attempt Every...|Mullenweg's "coup attempt" post]] - [[3. Resources/Readwise/Articles/Rumors Say Toni Schneider Resigned From the Automattic Board|goblin.band Schneider rumor]]: per the earlier note, TechCrunch now hears the same reports, still unconfirmed by Automattic or Schneider. **Unverified detail:** the earlier note says a CMSWire search snippet names Automattic spokesperson Megan Fox as sending the statement by email at 5:05 p.m. on Sept 12. Only the snippet was read, not the article, so treat the name and time as unconfirmed. ## 🗣️ Paraphrase SEJ reports that Automattic confirmed Matt Mullenweg is back in charge after a three-day stretch. On Wednesday, September 9 the board put him on paid leave and made CFO Mark Davies the CEO. Mullenweg then posted in Slack that he was back in control, which TechCrunch covered on Friday, September 11 with a headline asking whether he was trolling. Mary Hubbard tweeted her support for his return, and employees posted support that Mullenweg reposted. On Saturday, September 12 Automattic issued a second statement. The article says it reads differently from the first: the first was formal and short, the second informal, persuasive and one long sentence. The article asks whether Mullenweg wrote it. It gives no evidence either way. The captured copy doesn't include the text of either statement. ## 📰 Newsletter **A confirmation, a hedge and a question: how SEJ covered Mullenweg's return.** Search Engine Journal says an Automattic spokesperson confirmed Matt Mullenweg is back as CEO. The headline says "apparently" and the first paragraph says "confirmed." The article doesn't say who the spokesperson spoke to, and it doesn't link the TechCrunch report that, per our earlier note, published the statement about 22 hours earlier. Read it for the sourcing, not the verdict. Named sources: a TechCrunch headline, a Mary Hubbard tweet, one employee tweet. Unsourced in the text: the 50-minute notice, the Slack takeover, the volume of employee posts. The piece's main move is a tone comparison between two official statements and the question of who wrote the second. A change in tone shows a different drafting process. It doesn't name a drafter. For the Saturday statement itself, go to TechCrunch's Sept 12 report: [techcrunch.com](https://techcrunch.com/2026/09/12/automattic-confirms-mullenweg-has-returned-as-ceo-after-attempted-ouster-by-board/). ## ✅ Action items Each line ties to this source or says plainly that no action follows. #### DevRel - Developer advocacy: no direct action. If you cite this story in a talk, credit TechCrunch for the Saturday statement and mark the 50-minute notice as Mullenweg's own account. - Education: use ¶3 to ¶9 as a worked example in a "read the news critically" session: highlight each hedge, then each claim that has no named source. - Developer experience: none. The article isn't about tooling. - Developer marketing: none. Don't repeat the authorship question as fact in public posts. - Community management: if the story comes up in community channels, link primary reports, not the SEJ summary, and keep authorship speculation out of the thread. - Internal/external/cross-project: none from this source. #### OSPO - Policy and governance: the episode raises a question about who controls shared internal systems (the Slack workspace, ¶5) during a leadership dispute. An OSPO can check how its own admin rights are revoked and by whom. - License compliance: none. The article raises no license question. - Security management: nearest relevance: account and admin access after a role change (¶5). No direct action from the article. - Software inventory: none. - Developer support: none. - Community engagement: none from this source. - Strategic alignment: Hubbard's tweet ties Automattic's financial support to WordPress project continuity (¶8). An OSPO that depends on a single corporate sponsor can note that dependence in its risk register. #### Community - Maintainers: no direct action. Nearest relevance: maintainers who work at Automattic may get questions the article can't answer. - Contributors: none. - Sponsors: Hubbard calls Automattic "the largest financial contributor to the WordPress project" (¶8). That is her claim; the article gives no figure. Sponsors can ask for the numbers before relying on it. - Ecosystem: none from this source. #### WordPress - Core: no direct action. - Core Performance: none. - Core AI: none. - **Core Program Team:** none. - Mobile: none. - Playground: none. - Community: no direct action. Nearest relevance: community leaders may get questions about the story, and TechCrunch's reports are better primary links than the SEJ summary. - Training: none. - Marketing: none. Avoid repeating "back in control" claims as established without a named source. - Support: none. - Design: none. - Documentation: none. - Photos: none. - TV: none. - Polyglots: none. - Accessibility: none from this source. - Meta: none. - CLI: none. - Hosting: none. The article doesn't touch hosting. - Tide: none. - Openverse: none. - Themes: none. - Plugins: none. #### The WPOCC - Programs: none directly. - Projects: none. - Funding experiments: nearest relevance: the article's one funding claim (¶8) is a reminder that project funding depends on a sponsor's governance stability. No direct action. ### FAIR - Technical independence: none. The article says nothing about packages or signing. - Policies and covenants: none directly. The episode shows how a leadership dispute at a sponsor can raise continuity questions for a project. A governance document can state what happens to commitments when sponsor leadership changes. That is an idea, not something the article says. - Productized governance artifacts: none from this source. ## 🧪 Hypotheses 1. News reports on fast-moving corporate disputes drop attribution on contested claims more often than on uncontested ones, because the contested claim is the one the outlet hasn't confirmed itself (the 50-minute notice, ¶3). 2. Pairing a hedged headline with an unhedged first paragraph, as here, makes readers rate the central claim as more certain than readers who see only the headline. 3. Readers who see the missing statement text can't reproduce the article's tone comparison, and readers who do see it agree with the "informal versus formal" description at a rate well above their agreement on authorship. 4. Tone differences between two statements are explained by a different approver or drafting process at least as often as by a different named author. 5. The number of employee posts that backed Mullenweg, once counted, is smaller than "numerous" implies, because the article cites one post (¶22) and links none. 6. Saved copies of news articles in read-later tools drop blockquoted primary documents at a measurable rate, and the loss is highest for statements and quotes set apart from the body text. ## 📊 Methodology - **H1.** Take a sample of 30 to 50 news reports about corporate leadership disputes. Code each contested claim for attribution (named, hedged only, flat) and compare rates. Two coders, with agreement reported. - **H2.** Show two reader groups the same article with and without the opening confirmation, then ask how certain the central claim is on a 1 to 5 scale. Compare means. - **H3.** Show readers the two statements (from TechCrunch's report) and ask them to rate tone on formality, then ask who they think wrote each. Compare agreement across the two questions. - **H4.** Collect cases where a company's authorship of a statement became known later. Compare how often tone predicted the drafter versus the signer. - **H5.** Count public posts by Automattic employees on the dates in the article, for and against, using platform search and dated screenshots. State the method and the gaps. - **H6.** Compare Reader's saved copy with the live page for 100 articles. Count blockquotes present on the page and absent from the copy. - **Controls throughout.** Date-stamp every capture and record the capture method. Don't use the article's own framing to select the sample. ## ❓ Questions - Who at Automattic sent the spokesperson statement, and to which outlets (¶1)? - Where did SEJ get the 50-minute notice detail (¶3), and is it Mullenweg's own account? - What exactly did the first and second statements say? The capture drops both (¶3, ¶11, ¶18). - Which tweets "supported his ouster" (¶9), and how many were there compared with the supportive ones? - Why does the headline say "apparently" while ¶1 says "has confirmed"? - What did the board do after Sept 12? The article doesn't say whether the board accepted the outcome. - Does the "perception" in ¶9 come from any named reader or outlet, or from the author? - What would settle the authorship question, and does anyone with knowledge of the drafting say anything on the record? ## 🔮 Future research - **Statement provenance.** Find who issued the Saturday statement and on which channel. The earlier note's CMSWire snippet is a lead, not a source. - **Board composition.** The earlier note records TechCrunch hearing that the board "still may be in flux" and unconfirmed reports about Toni Schneider. Track what Automattic or the individual confirms. - **Sourcing practice.** Compare how SEJ, TechCrunch, 404 Media and The Verge each attribute the contested claims. The vault has notes on the last three. - **Capture fidelity.** Test whether the Readwise capture can keep blockquotes, since primary-document quotes carry the argument in pieces like this. - **Tone analysis.** If the statements are available, a simple readability and sentence-count comparison could replace the article's impressionistic comparison. ## 💡 Implications - **Practice.** Cite the primary report for the Saturday statement, not the secondary summary. For any contested fact, write who said it. - **Policy.** Newsrooms and bloggers covering disputes can adopt a line: "hedges don't replace attribution." The 50-minute claim is the example here. - **Security.** The article's Slack episode (¶5) is an access-control case: removal from a workspace and removal of its admins are separate actions. The article reports that one happened and not the other, which, if accurate, is a gap in offboarding. That is an inference, and the article doesn't discuss offboarding. - **Education.** The piece works as a teaching example for separating reported fact, outlet voice and interpretation. The Main content ledger shows how. - **Funding.** Hubbard's tweet ties sponsor stability to project funding (¶8). The article supplies no figures, so it supports no funding conclusion. ## 🧠 Learning styles assessment - **Reading level estimate.** About grade 15 on the Flesch-Kincaid Grade Level and about 35 on Flesch Reading Ease, from a script count on the 20 full sentences in the capture with a heuristic syllable counter. Treat it as an approximation. Short paragraphs and plain vocabulary keep the text easy to scan, while long sentences like ¶9 push the score up. #### 👀 Visual learners - Present: one featured image (¶23), per its caption, and embedded tweets (¶8, ¶22). - Improve: a timeline of Sept 9 to Sept 12, like the table in Main content, would show the sequence. The statements, now missing, should appear as visible blockquotes. #### 🔊 Aural learners - Present: no audio is referenced. - Improve: a short read-aloud of the two statements would let listeners hear the tone difference the article describes. #### 🗣️ Verbal learners - Present: short headed sections (Catching Up, Review, Comparison, Responses) with plain prose. - Improve: quote the two statements next to each other so the verbal comparison isn't left to description. #### 🧩 Kinesthetic learners - Present: none. The article isn't a procedure. - Improve: ask readers to mark each claim in the piece as named source, hedged, or flat, then check the links. #### 🧠 Logical learners - Present: a clear compare-and-contrast structure in ¶12 to ¶17. - Improve: state the evidence for authorship, or say there is none. As written, the inference runs from tone to author with no middle step. #### 🧑‍🤝‍🧑 Social learners - Present: a "Responses" section with an employee tweet (¶21, ¶22). - Improve: add counter-voices. The section shows support only. #### 🧘‍♀️ Solitary learners - Present: a short, self-contained piece that stands alone. - Improve: add a one-line timeline at the top so a cold reader doesn't need the earlier coverage. #### 🌿 Naturalistic learners - Present: nothing relevant. - Improve: none needed for this topic. ## 📊 Accessibility assessment Judged as captured. The capture is a text view of the page, so markup, alt text and contrast can't be seen. #### Screen reader semantics - Present: the section titles (¶2, ¶4, ¶10, ¶13, ¶15, ¶20) read as headings in sequence. Whether they are real heading elements isn't visible in the capture. - Improve: the headings use title case and one carries an ellipsis character (¶4), which some screen readers announce awkwardly. The quoted statements, which carry the argument, are missing from the capture; if they are blockquotes on the live page, that is a capture problem, not a page problem. WCAG 1.3.1 (Info and Relationships) applies if the live page marks quotes with styling only. #### Keyboard navigation - Present: not assessable from the captured text. - Improve: three links appear in the link list (anchors "Automattic put Matt Mullenweg on paid leave," "reported," "tweeted"). Embedded tweets, if present on the live page, need a keyboard path in and out (WCAG 2.1.2, No Keyboard Trap). That can't be verified here. #### Contrast and readability - Present: unknowable from text. Page styling isn't captured. - Improve: none to assess. Embedded tweet widgets usually bring their own styling. #### Text resizing and reflow - Present: the capture reflows as plain text with short paragraphs. - Improve: the live page's reflow at 400% zoom (WCAG 1.4.10) can't be verified here. #### Media and captions - No video or audio is referenced in the captured text. The featured image has a caption (¶23). Whether it has alt text isn't visible (WCAG 1.1.1). Two embedded tweets (¶8, ¶22) appear as text. #### Forms and interactions - Present: none. No form appears in the capture. - Improve: none needed. #### Standards reference - Candidate gaps against WCAG 2.2 AA, each unverified: **2.4.4** (Link Purpose in Context): the anchors "reported" and "tweeted" are vague out of context, although "Automattic put Matt Mullenweg on paid leave" is descriptive. **1.1.1** (Non-text Content): alt text for the featured image isn't visible. **1.3.1**: how the quoted statements are marked up on the live page isn't visible. **2.4.6** (Headings and Labels): headings are readable; the heading text is descriptive. ## 🌍 DEIB assessment #### Cultural breadth - Present: a US-centered tech-industry story told in English. The text has no multilingual content and doesn't address a global audience. The time zone label (EST, ¶11) assumes an Eastern US reader. - Improve: give times in UTC as well, as the earlier note's sources did, so a global community can place the sequence. #### Inclusive language - Present: neutral reporting language. The article uses "Automatticians" for employees (¶9), which is the community's own term. - Improve: define "Automatticians" on first use for outside readers. "Trolling" in the TechCrunch headline (¶6) is quoted, not endorsed. #### Neurodiversity support - Present: short paragraphs, a predictable heading structure, and a clear section for responses. - Improve: put the two statements in view. Without them, a reader holds the comparison in memory, which adds load. #### Representation - Present: named people are Mullenweg, Davies, Hubbard and @jamesgrierson. The article uses no pronouns for Davies, Hubbard or Montti. It uses "he" and "his" for Mullenweg, as the source does (¶3, ¶5). - Improve: the responses section shows employee support only (¶21, ¶22). Voices that backed the board aren't quoted, so the piece represents one side of the workforce. #### Psychological safety - Present: the article doesn't name any employee as opposed to Mullenweg. - Improve: the question about who wrote the statement (¶19) invites speculation about a named person without evidence. Readers should avoid guessing about individuals, including the spokesperson. The CMSWire name in References is unconfirmed and shouldn't be repeated as fact. ## ✅ Logical validity Source type: news report with commentary. It reports with partial attribution, then argues from tone. Its commercial context is a search-industry news site covering a WordPress story, with no stated interest in the outcome. #### Strong reasoning - **Clear compare-and-contrast, ¶12 to ¶17.** The article sets out three dimensions for the comparison (tone, word choice, structure) and names features of each statement: three sentences versus one, third person versus personal, informing versus persuading. A reader with both statements could check each feature. - **Hedges where the article is unsure, ¶1, ¶3, ¶9.** "Apparently," "appeared" and "maybe" mark the points the author can't confirm. The hedging is honest even where the attribution is thin. - **Quoting primary text in full, ¶8, ¶22.** Hubbard's and @jamesgrierson's tweets appear in full, and Hubbard's links to the status. - **Linking its own prior coverage, ¶3.** The Sept 9 background is linked instead of re-reported. #### Fallacies - **Loaded question (insinuation), ¶19 and ¶1.** "Was the second announcement dictated or authored by Matt Mullenweg himself?" Why weak: the question plants a claim and offers no evidence for either answer, and ¶1 states it as "reads as if." Fix: say the statement reads unlike a vetted corporate statement and stop there, or cite someone with knowledge of who drafted it. - **Inference from style to author, ¶1, ¶16, ¶17.** "Sounds like a personal assertion." Why weak: informal style shows a different drafting process or approver, not a specific writer. Per the earlier note, a spokesperson delivered the statement by email. Fix: name what the style change indicates and drop the author claim. - **Unattributed causal claim, ¶9.** Hubbard's tweet "led to a perception." Why weak: no source reports that perception, and the sequence of tweet and perception isn't dated. Fix: attribute the perception to named commentators or call it the author's reading. - **Unquantified generalization, ¶9 and ¶21.** "Numerous Automatticians" and "Many from Automattic." Why weak: one tweet is quoted and none are linked. Fix: give a count or a link list. - **Unmeasured effect, ¶9.** "Effectively drowning out the tweets that supported his ouster." Why weak: no ouster-supporting tweets are linked or counted, so "drowning out" can't be checked. Fix: cite counts or reach for both sets. - **Dropped attribution, ¶3.** The 50-minute notice and the denied delay read as near-fact with one "apparently." Per the earlier note, WP Tips reports these as Mullenweg's own Slack account. Fix: write "Mullenweg said." - **Framing tension, title versus ¶1.** The headline hedges and the lede asserts a confirmation. Fix: choose one level of certainty. #### Tone of voice - Plain, journalistic and mildly editorial. Evaluative words appear in the comparison: "differs greatly" (¶12), "Most strangely" (¶17), "argumentative edge" (¶17). The reporting paragraphs (¶3, ¶6) are neutral. ## 🛡️ DARVO analysis Not applicable to this source. DARVO describes a response to an accusation, and this article is a news report, not a response to one. **Deny:** the article denies nothing on its own behalf. **Attack:** it attacks no one. It describes Automattic's second statement as having "an argumentative edge" (¶17), but the statement's text isn't in the capture, so any attack or denial inside it can't be assessed here. **Reverse victim/offender:** no such move appears. Per the earlier note, the Saturday statement asserts board support and points readers to supportive posts online. That is an assertion of status rather than a reply to a specific accusation, and it comes from the earlier note, not this capture. ## 🎯 Conclusion The article's one checkable new fact is that an Automattic spokesperson confirmed Mullenweg as CEO on Saturday, September 12 (¶1, ¶11). The article doesn't name who spoke to whom or link the primary report. Per the earlier note, TechCrunch published that report about 22 hours earlier. Cite TechCrunch for the statement, not SEJ. Named-source claims in the article are few: a TechCrunch headline, a Mary Hubbard tweet and one employee tweet. The 50-minute notice, the Slack takeover, the volume of employee posts and the reposting effect carry no named source in the text. The tone comparison between the two statements is fair as observation. The authorship question (¶19) is speculation, since style shows a different drafting process, not a specific author. **Next steps for readers:** read TechCrunch's Sept 12 report for the statement, find the actual text of both statements (the capture lost them), and track the open items the earlier note lists: the board's composition and the unconfirmed reports about Toni Schneider's departure. ## 🔄 Refactor Appendix — Matt Mullenweg apparently back in charge at Automattic > Density: 2–5 Literature atoms (H1 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 5 Literature, 2 Permanent. Resonance filter applied: section headings, the featured > image caption and the two embedded tweets were dropped as non-argument text. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] The article infers authorship from tone alone > [!quote] [¶1] > Yet the statement itself reads as if it were dictated or authored by Mullenweg himself. **Context & use**: - ¶1, the lede. The question returns in ¶19. - The article offers style as its only evidence. Use this to separate "reads like" from "was written by." **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H2] The 50-minute claim carries a hedge, not a source > [!quote] [¶3] > Mullenweg was apparently given fifty minutes’ prior notification of the meeting **Context & use**: - ¶3. Per the earlier note, WP Tips reported this as Mullenweg's own account, so the text drops that attribution. - A model case for "apparently" standing in for a name. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H3] A Slack lockout claim arrives without a named source > [!quote] [¶5] > Automattic however had failed to remove Mullenweg from the company Slack workspace and he took control of it **Context & use**: - ¶5. "Failed to remove" is the article's inference. Per the earlier note, TechCrunch confirmed the admin removals but not this framing. - Pair with the Security note in Implications: removing a user and removing their admin rights are separate steps. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H4] Reposting volume gets described as drowning out dissent > [!quote] [¶9] > with Mullenweg reposting each post to amplify their comments across social media, effectively drowning out the tweets that supported his ouster. **Context & use**: - ¶9. No count of either set of tweets, and no tweets linked. - Useful as an example of an effect claim with no measure behind it. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H5] The comparison rests on style, not drafting evidence > [!quote] [¶16] > The second statement is written in an informal style that sounds like a personal assertion and not an official corporate communication. **Context & use**: - ¶16. A fair description of tone if the statements are visible. They are missing from the capture, so the reader can't check it here. - A style description supports "different process or approver," not "different author." **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] A hedge is not a source **Claim** (one sentence, Courtney's voice): A hedge like "apparently" tells me the author is unsure, and it doesn't tell me who said it. **Evidence pointer**: [[#H2]] · [[#H3]] **Scope & conditions**: Holds for fast-moving news where the first report cites no one. Breaks when a hedge sits beside a named source that carries the claim. Both uses in this article are the unsourced kind. **Links**: - [[3. Resources/Readwise/Articles/Matt Mullenweg Put on Leave as Automattic CEO|WP Tips: Mullenweg put on leave]] — because evidence-for where the 50-minute claim traces to Mullenweg's own account - [[Sourcing discipline]] — because extends the habit of writing who said it - [[Summaries of fast-moving news]] — because contrasts on whether the primary report is linked <!-- atomicity: 1 idea ✓ --> #### [P2] A tone change shows a process change, not a person **Claim** (one sentence, Courtney's voice): When two statements from one organization differ in tone, I can say the drafting or approval changed, and I can't say who wrote the second. **Evidence pointer**: [[#H1]] · [[#H5]] **Scope & conditions**: Applies to corporate statements delivered by a spokesperson. Breaks if someone with knowledge of the drafting goes on record. This article gives no such source. **Links**: - [[Corporate communications]] — because applies-in - [[Authorship attribution]] — because contrasts on style as evidence versus provenance <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Pull TechCrunch's Sept 12 report and compare its attribution to SEJ's lede, line by line #fleeting #inbox - [F2] Open question: who at Automattic sent the spokesperson statement, and to whom (¶1)? #fleeting #inbox - [F3] A one-page "named source, hedged, or flat" checklist built from the Main content ledger #fleeting #inbox #articleseed ### → Things 3 (max 2 actions) - [ ] Read TechCrunch's Sept 12 Automattic confirmation report and note who received the statement, Mullenweg story tracking #things - [ ] Draft a short sourcing-discipline checklist using this article's ledger of named, hedged and flat claims, writing practice #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Matt Mullenweg Apparently Back in Charge at Automattic.md|Matt Mullenweg Apparently Back in Charge at Automattic by Roger Montti]] ## Highlights - A spokesperson from Automattic has confirmed that Matt Mullenweg is back in charge of Automattic. The statement follows a period of days when it appeared that Mullenweg had gained access to the Automattic Slack account but not Automattic itself. Yet the statement itself reads as if it were dictated or authored by Mullenweg himself. ([View Highlight](https://read.readwise.io/read/01m2ee3raa8dbfgq1hhec8zn2j)) - Note: Thesis: Automattic confirmed the return, but the statement's style suggests Mullenweg wrote it. The article doesn't say where the statement was issued. - Tags: atom/literature/h1 - On Wednesday, September 9, the Board of [Automattic put Matt Mullenweg on paid leave](https://www.searchenginejournal.com/wordpress-co-founder-matt-mullenweg-ousted-from-automattic/589009/) for unspecified reasons and put the CFO, Mark Davies, into the CEO seat. Mullenweg was apparently given fifty minutes’ prior notification of the meeting, and his request for a delay to have an attorney review the move was denied. Mullenweg was subsequently ousted, and Automattic issued the following three-sentence statement: ([View Highlight](https://read.readwise.io/read/01m2ee3v87hpdah87vbgv10v40)) - Note: The 50-minute notice and denied attorney review come from Mullenweg's own Slack account (per WP Tips); "apparently" is the only hedge. - Tags: atom/literature/h3 - Most strangely, the first official statement is informative but the second statement consists of a single run-on sentence that is persuasive and contains an argumentative edge to it. ([View Highlight](https://read.readwise.io/read/01m2ee3yy28nc22dh6erd8rswy)) - Note: Style comparison as authorship evidence: a tone shift between statements shows a different drafting process, not a specific author. - Tags: atom/zettel/z1