The Most Expensive 33 Hours in WordPress History...  🔗 **Source:** [The Most Expensive 33 Hours in WordPress History...](https://www.youtube.com/watch?v=ylO0DQeVEBQ) > [!note]+ Document Notes > tags: [automattic, wordpress-governance, founder-control, board-removal, wp-engine-dispute, executive-severance] > author: Jeff Delaney (Fireship) > source: Fireship (YouTube) > reference: https://www.youtube.com/watch?v=ylO0DQeVEBQ > date created: 2026-09-23 19:02 > > > [!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: The most expensive 33 hours in WordPress history... > <!-- 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--the-most-expensive-33-hours-in-wordpress-history) ## 📝 Summary - **What happened.** Fireship (Jeff Delaney) published a 5:23 Code Report episode on 2026-09-23 recounting how Automattic's board voted to remove co-founder Matt Mullenweg as CEO on September 9, 2026, and how he returned 33 hours later by replacing the board. No chapters, no on-screen citations in the transcript; every event and figure below is the narrator's claim unless marked otherwise. - **The claim.** The board gave Mullenweg 50 minutes' notice, refused time for his lawyer, and installed CFO Mark Davies as CEO. Mullenweg, who the narrator says holds 84% of the voting power, replaced the board, was reinstated by "early Friday morning," then fired Davies and the chief legal officer (captions: "Andy Masaan"). The two had drafted severance terms during the interregnum that the narrator prices above $8 million. - **Why it matters.** At 00:02:08 the narrator describes wordpress.org as a site Mullenweg owns personally, from which "every WordPress install downloads its plugins, themes, and security updates," and reads one tweet as a plan to move it off Automattic servers. That link between a company board fight and the ecosystem's distribution layer is the load-bearing detail, not the pirate flag. - **Key stakeholders.** Automattic (WordPress.com, Tumblr, WooCommerce); board members as captioned (Sue Decker, Ann Dunwoody, Tony Schneider) and CFO Mark Davies; Mullenweg; WP Engine and its backer Silver Lake, whom Mullenweg is quoted as suspecting; Automattic employees with no explanation; the community relying on wordpress.org. - **Risks and tradeoffs.** Character attacks at 00:00:00 and 00:01:25 carry no evidence; precise numbers (80%, 84%, $8 million, 42 years) arrive unsourced; the board gets no airtime beyond "they never gave him a reason." Against that, he labels "one theory," "Matt's theory," and what Automattic "confirmed" separately. - **Bottom line.** A well-sequenced index of claims to verify, not a record. The one argument that stands on its own logic: a board can't durably remove a CEO who can replace the board. Everything else needs Automattic's statements, the WP Engine docket, TechCrunch, and Mullenweg's own posts. ## 📖 Main content **What the video is.** One narrator, fast cuts, a sponsor read in the last minute. About 15 events and 15 figures are asserted; none arrive with a named document. Where reporting is attributed, it is TechCrunch (00:00:00, 00:03:34). **Caption problems.** The auto-captions spell the company "Automattic" (00:00:00, 00:00:42) and "Automatic" (00:02:08, 00:03:34), and render two names as "Tony Schneider" and "Andy Masaan." The description names nobody but Mullenweg, so every personal name below is a caption spelling pending a check against Automattic's leadership page. Quotes preserve caption text. **The timeline the narrator asserts.** Dates come only from the transcript. Where a weekday appears without a date, the derived date assumes the September 9 return and the vote fall on the same day, which the transcript implies but doesn't state; September 9, 2026 is a Wednesday, so "Friday" is September 11 and "Saturday" September 12. That derivation is mine and is the first thing to check. | # | When (narrator) | Event (narrator's claim) | Time | Verify against | |---|---|---|---|---| | 1 | Labor Day weekend (derived Sept 5 to 7) | Mullenweg at Burning Man while the board seeks a replacement | 00:00:42 | His posts | | 2 | "Earlier this month" | Board removes him; CFO to CEO; "full confidence" statement; employees "ecstatic" to TechCrunch | 00:00:00 | Automattic; TechCrunch | | 3 | Sept 9 | Written proposal on return: vote in 50 minutes | 00:01:25 | Any filing quoting it | | 4 | Sept 9 | Asks "a few hours" for his lawyer; board says no | 00:01:25 | Same | | 5 | Sept 9, 50 min later | Vote by CFO Mark Davies with Sue Decker, Ann Dunwoody ("retired four-star general"), Tony Schneider (first CEO, "business soulmate") | 00:01:25 | Board roster; press | | 6 | Sept 9 (implied) | Slack: skipping next day's leadership meeting; Davies "conspired with the board behind his back" | 00:01:25 | Screenshots | | 7 | "The next day" (derived Sept 10) | Tweet: security researchers to move "stuff off automatic servers"; narrator infers wordpress.org | 00:02:08 | The tweet | | 8 | Within the 33 hours | Slack: pirate, cursing, "turncoats"; removes other admins; moves to wordpress.org Slack with pirate flag emoji | 00:02:51 | Screenshots; Make Slack | | 9 | Undated | Reddit: could fill board seats whenever, "but that wasn't the point" | 00:02:51 | Reddit | | 10 | "Early Friday morning" (derived Sept 11) | Slack announcements: board "back in agreement," he is "back in control" | 00:02:51 | Screenshots; Automattic | | 11 | Same window | Tweet on coup attempts and "strong enough leaders"; to TechCrunch: "not a troll, he's a pirate" | 00:03:34 | Tweet; TechCrunch | | 12 | "By Saturday" (derived Sept 12) | Automattic confirms him as CEO with full board support | 00:03:34 | Automattic | | 13 | Omitted from that confirmation | Entire prior board gone; Davies and the CLO fired | 00:03:34 | Leadership page; press | | 14 | During the 33 hours | Davies and CLO draft severance: a year's salary, a year of health insurance, full vesting; "over $8 million" | 00:03:34 | No source named | | 15 | After | Employees told to wait; receive a blog post about buying a houseboat | 00:04:16 | His blog | **Figures asserted, all unsourced in the transcript.** 33 hours and over $8 million (00:00:42, 00:03:34). 42 years without swearing (00:00:42, 00:02:51). 84% voting power (00:02:51). 80% devaluation (00:00:42). 50 minutes' notice, 21 years since founding (00:01:25). WordPress co-created at 19, "the last 2 years" of legal war (00:00:00). 20 months of Signal history and two phones (00:02:08). Sponsor read: 50 free reviews a month, "several million developers" (00:04:16 to 00:04:58). **Causal claims and hedges.** Three explanations at 00:02:08, each marked: the board's (none); "one theory," owned by nobody (removing "the guy who may have destroyed evidence might make a judge go easier on the company"); "Matt's theory" (Silver Lake "was involved in a plan to destroy his life"). The narrator endorses none. That discipline is the most useful thing in the source. **The wordpress.org detail.** At 00:02:08 two claims share one sentence: an inference about a tweet, flagged "most likely," and a flat description of wordpress.org as personally owned and the source of every install's plugins, themes, and security updates. The second names a single distribution point outside the company whose board just acted; check it against Make WordPress posts and any court filings. **Omissions.** No board member's statement; nothing from WP Engine or Silver Lake; no account of why a board facing a controlling shareholder would vote at all; nothing on operations during the 33 hours or on WordPress project governance beyond the pirate flag. The severance is one-sided: executives "drafted their own severance agreements" while "running the company," implying self-dealing without saying who approved them. The Greptile sponsor read from 00:04:16 is disclosed and has no bearing on the WordPress material. ## 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=0) The setup and the OpenAI comparison - Narrator was migrating his blog to Kubernetes when Automattic's board "tried to pull an open AI and fire their founder out of nowhere." - On paper it "went great": CFO to CEO, statement of full confidence, employees "ecstatic" per TechCrunch. No count, no names. - Framing: Mullenweg "co-created WordPress at 19," spent "the last 2 years" fighting WP Engine, and has "a martyrdom complex that would make Al-Qaeda proud." A joke, not evidence. - An inserted Mullenweg clip (captions mark it ">>") is the only Mullenweg audio in the transcript. > [!quote] [00:00:00] > One thing is if you're really open in open source, sometimes you have to stand up to bullies and you have to fight to protect your open source ideals. #### ⏱️ [00:00:42](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=42) Three promises and the board primer - Promises: the 33-hour return, "$8 million in severance," and why "a man who hasn't sworn in 42 years" calls himself a pirate. Dateline: "It is September 23rd, 2026." - Primer: the board sits above the CEO so the company has recourse if the CEO "decides to get into a petty legal battle that devalues the company by 80%." No source or baseline. - Mullenweg at Burning Man over Labor Day weekend; returns September 9. #### ⏱️ [00:01:25](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=85) The 50-minute vote - Vote in 50 minutes on a company "he started 21 years ago." He asks hours for his lawyer; "The board said no." - Participants per captions: CFO Mark Davies; Sue Decker; Ann Dunwoody, "a retired four-star general"; "Tony Schneider," first CEO and once his "business soulmate." Spellings unverified. - A Survivor clip ("The tribe has spoken") marks the outcome. First response: a Slack post skipping the next day's leadership meeting because Davies "conspired with the board behind his back." > [!quote] [00:01:25] > he received a written proposal from his board stating that in 50 minutes, they'd be voting to remove him as CEO of a company he started 21 years ago. #### ⏱️ [00:02:08](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=128) Three theories and the wordpress.org tweet - No reason given. Mullenweg's assumption: the WP Engine case, where WP Engine "spent the summer accusing him of destroying evidence" after "20 months of his signal history and two of his phones went missing." Attributed to WP Engine. - "One theory" (unowned): removal helps with the judge. "Matt's theory": Silver Lake plotted "to destroy his life." - Next-day tweet about moving "stuff off automatic servers"; narrator's inference: wordpress.org. #### ⏱️ [00:02:51](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=171) Pirate, turncoats, and 84% - Slack: the cursing line below; "The Slack smells funny like turncoats." Removes every other admin; moves to the wordpress.org Slack with a pirate flag emoji. - Reddit: could fill board seats whenever, "but that wasn't the point." - Mechanism: 84%; board out, new board in, "which is exactly what happened." "Early Friday morning": announcements post, back in control. > [!quote] [00:02:51] > and I quote, "Oh, since I'm a pirate now, I curse." After 42 years of never uttering a curse word, it's kind of fun. > [!quote] [00:02:51] > And he's not wrong because he holds 84% of Automattic's voting power. #### ⏱️ [00:03:34](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=214) Reinstatement, firings, and the severance bill - Tweet: no coup attempt every few years means "not hiring strong enough leaders." To TechCrunch: "not a troll, he's a pirate." - "By Saturday" Automattic confirms him. Unmentioned, per the narrator: the whole prior board is gone; Davies and CLO "Andy Masaan" fired. Absence: 33 hours. - Severance drafted by "the two executives running the company while Matt was out"; "over $8 million." No document or reporter named. > [!quote] [00:03:34] > had drafted their own severance agreements where if they were fired, they'd be paid out a full year's salary, a year of health insurance, and all of their stock would immediately vest. #### ⏱️ [00:04:16](https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=256) Aftermath and the Greptile read, to the end - Employees have no answer; told to wait for a message, they get "a blog post about him trying to buy a houseboat." - Segue: "Although they're still in the dark, you don't have to be with Greptile." Sponsor claims: a "T-Rex mode" sandbox, an Axios promise bug caught, 50 free reviews a month. - Sign-off at 00:04:58: "This has been the Code Report." ## 📚 References The transcript itself contains no links; the following come from the video description or are primary sources for named entities. - [The most expensive 33 hours in WordPress history... — Fireship](https://www.youtube.com/watch?v=ylO0DQeVEBQ) — the source, 5:23, uploaded 2026-09-23, no chapters. - [Greptile](http://greptile.com/go/fireship) — sponsor link from the description; the only link the narrator points to ("the link below," 00:04:58). - [Automattic](https://automattic.com) — primary source for the statements paraphrased at 00:00:00 and 00:03:34 and for checking five caption-spelled names. - [WordPress.org](https://wordpress.org) and [Make WordPress](https://make.wordpress.org) — the site described at 00:02:08 and where any project-side statement would appear. - [WP Engine](https://wpengine.com) — the litigant said to allege evidence destruction (00:02:08). The court docket, unnamed in the video, is the primary source for "20 months" and "two phones." - [Silver Lake](https://www.silverlake.com) — the firm Mullenweg is quoted as blaming (00:02:08). No statement mentioned. - [TechCrunch](https://techcrunch.com) — cited twice (00:00:00, 00:03:34). - [Matt Mullenweg's blog](https://ma.tt) — likely home of the houseboat post (00:04:16); verify. ## 🗣️ Paraphrase Fireship's account: Automattic's board waited until its founder-CEO was at Burning Man, lined up a replacement, and on the day he returned handed him a proposal with a vote 50 minutes out. He asked for time for a lawyer; they refused; the CFO became CEO; the company said it had full confidence. Nobody told him why; he guessed the WP Engine lawsuit and blamed the private-equity firm behind it. Then he used the lever the board couldn't take. With 84% of the votes he could replace the directors, the new directors could reinstate him, and within 33 hours that happened. Automattic's Saturday statement said he was CEO with the board's full support; it didn't say the board was new or that the CFO and chief legal officer were out. Those two had written themselves severance terms while in charge, and the bill, the narrator says, is over $8 million. ## 📰 Newsletter **Thirty-three hours, one pirate flag, and a question about wordpress.org.** Fireship's Code Report recaps the Automattic board's attempt to remove Matt Mullenweg on September 9 and his return by that Friday. The jokes land, the sequencing is clear, and none of it is sourced on screen, so treat it as a checklist to confirm. The key mechanism: the narrator says Mullenweg holds 84% of the voting power, so a board that votes him out gets replaced by one that votes him back in. The part that matters for people who ship WordPress: at 00:02:08 the video describes wordpress.org as personally owned and the place every install pulls plugins, themes, and security updates from, and reads one tweet as a plan to move it. That reading is the narrator's inference, flagged "most likely." If a colleague asks: plausible timeline, unverified; 84%, $8 million, and 80% unsourced; board's reasons unknown. Read [the video](https://www.youtube.com/watch?v=ylO0DQeVEBQ), then [Automattic](https://automattic.com), then [Make WordPress](https://make.wordpress.org), in that order. ## ✅ Action items #### DevRel - Developer advocacy: prepare a sourced answer to "what changed for developers." Until primary sources land: nothing the video documents; the wordpress.org line at 00:02:08 is an inference. - Education: use the 84% argument at 00:02:51 in governance sessions: cap tables, not org charts, decide control. - Developer experience: none from this source; nearest relevance: update-channel docs would need review if distribution ever moved, and the video reports no move. - Developer marketing: don't repeat 84%, $8 million, or 80% externally without a citation. - Community management: pin a short "verified vs claimed" note where the video circulates. - Internal/external/cross-project: keep one dated list of Automattic statements and TechCrunch pieces. #### OSPO - Policy & governance: assess from public sources which WordPress project assets have written ownership and continuity terms. - License compliance: none from this source. - Security management: "security updates" is named among what every install pulls from wordpress.org (00:02:08). Add "distribution-point control change" to the threat register as a labeled scenario. - Software inventory: confirm which internal systems pull from wordpress.org and whether each has a documented fallback. - Developer support: a plain-language note on "controlling shareholder" for engineers who will read this as a hostile takeover. - Community engagement: read any FAIR or independent-distribution response before forming a house position. - Strategic alignment: track upstream governance events in executive reporting. #### Community - Maintainers: none direct; nearest relevance: maintainers publishing through wordpress.org should know the claim exists and is unverified. - Contributors: the wordpress.org Slack appears at 00:02:51; contributors may ask whether project Slack administration changed. The video doesn't say it did. - Sponsors: none from this source. - Ecosystem: a candidate incident for a cross-host update-channel tabletop. #### WordPress - Core: none; no codebase or release change is described. - Core Performance: none. - Core AI: none. - **Core Program Team:** track whether any Make team publishes on the events at 00:02:51 (Slack admins) or 00:02:08 (infrastructure). - Mobile: none. - Playground: none. - Community: a shared FAQ pointing at primary sources for WordCamp organizers. - Training: none direct; nearest relevance: the timeline table works as a "claim vs source" exercise. - Marketing: none; don't amplify. - Support: expect "is wordpress.org going away." The video doesn't say so. Prepare one line. - Design: none. - Documentation: none. - Photos: none. - TV: none. - Polyglots: none. - Accessibility: none. - Meta: closest to the infrastructure described at 00:02:08; any clarification would come from here. - CLI: none. - Hosting: check that fallback documentation for the update source exists. - Tide: none. - Openverse: none. - Themes: the theme directory is one of three asset types named at 00:02:08. Awareness only. - Plugins: same, for the plugin directory. #### The WPOCC - Programs: none direct; nearest relevance: The WP Open Community Collective's case for independent community funding gets a fresh illustration here. - Projects: a governance clinic could open with this video: 15 events, zero on-screen sources, one valid deduction. - Funding experiments: none from this source. ### FAIR - Technical independence: the 00:02:08 description (single site, personally owned, every install depends on it) is the condition FAIR's independent-distribution work addresses. Cite the video as illustration of the perception, not evidence of change. - Policies and covenants: check whether anti-capture language covers founder control, not only acquirer control. - Productized governance artifacts: an operator scorecard row for "who can unilaterally change the update source" would have made this risk legible in advance. ## 🧪 Hypotheses 1. If Mullenweg holds a majority of the voting power (narrator: 84%), the September 9 vote couldn't produce a removal lasting longer than board reconstitution, so the 33 hours reflect logistics, not a contest of control. 2. The 80% devaluation refers to a published valuation change over the two-year dispute window; if no such valuation is public, the number is unverifiable and should be dropped. 3. Automattic's confirmation names the reconstituted board; if not, "the entire existing board was gone" rests on uncited reporting. 4. The tweet read as concerning wordpress.org doesn't name wordpress.org; if so, the inference is the narrator's and must be labeled as such in any summary. ## 📊 Methodology - **H1.** Find any public statement of Automattic's share structure (funding-round coverage, company statements, WP Engine litigation filings). If a controlling stake is documented, reconstruct the director-appointment timeline from dated statements and posts. - **H2.** Search for published Automattic valuations, 2024 to 2026. Two data points give a change; none gives "no public basis," and the figure retires. - **H3.** Read the confirmation statement in full; enumerate named directors; diff against the pre-September-9 roster. - **H4.** Retrieve the September 10 tweet; text-match "wordpress.org"; record the result beside the narrator's hedge. - **Controls.** Record retrieval dates. Separate what a document says from what a reporter says it says. Mark video-only items "narrator only." ## ❓ Questions - What reason, if any, did the board give in writing, and has any director spoken since? - Does Mullenweg hold 84% of voting power, through what share class or agreement, and who holds the rest? - Who approved the severance agreements, and who had authority to during the 33 hours? - What did the September 10 tweet say, and did any infrastructure change follow? - Is the 00:02:08 description of wordpress.org accurate in every particular, and where is that documented? - What does the WP Engine court record allege about Signal history and phones, and when? - Did any Make WordPress team or the WordPress Foundation publish anything during or after the 33 hours? ## 🔮 Future research - **Founder-controlled boards as governance theater.** If 84% holds, this is a natural case for what a board does when it can't remove the CEO. Dual-class charter provisions and director interviews would show whether the vote had any path to sticking. - **Distribution-point concentration in open source.** How many ecosystems route updates through infrastructure owned by one person or company? A registry survey would place WordPress on a spectrum. - **Explainers as first draft of record.** Tracking how often 84%, $8 million, and 80% reappear in later coverage without independent confirmation would quantify the effect. ## 💡 Implications - **Practice.** The DevRel deliverable is a verified timeline, not a take. Every colleague question maps to a table row with a "verify against" cell. Answer from primary sources or say "unverified." - **Policy.** Governance documents that don't name who controls the update channel, and under what conditions it can move, are incomplete. - **Security.** Contested control of the channel that delivers "security updates" (00:02:08) is a supply-chain scenario and belongs in a threat model as one, even though the video reports no actual change. - **Education.** The 84% deduction is a one-sentence governance lesson. The rest is a media-literacy lesson: precise numbers, no sources, attribution discipline in the middle, character attacks at the edges. - **Funding models.** Independent community funding (The WPOCC, FAIR) gains a resilience argument from any episode where one company's dispute reaches project infrastructure in public. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level on the transcript: approximately grade 11. Sentences average 25 to 30 words and several exceed 50 (the 00:00:42 board primer runs past 60). Vocabulary is plain, so Flesch Reading Ease lands near 55. The viewer is assumed to know what a board, voting power, and vesting are; none is defined. #### 👀 Visual learners - Present: meme cuts and clips (Survivor at 00:01:25, Mullenweg at 00:00:00); screenshots implied at 00:02:51. - Improve: no timeline graphic, no board/CEO/shareholder diagram, no cap-table visual for the 84% claim. #### 🔊 Aural learners - Present: continuous narration; two inserted voices. - Improve: no pause after any figure. #### 🗣️ Verbal learners - Present: the board-over-CEO relationship in one sentence (00:00:42); the voting mechanism in two (00:02:51). - Improve: "severance," "vest," "voting power," and "chief legal officer" go undefined. #### 🧩 Kinesthetic learners - Present: nothing to do. - Improve: a linked list of primary documents would let viewers rebuild the timeline themselves. #### 🧠 Logical learners - Present: a chronological spine, one explicit deduction (00:02:51), theories sorted by owner (00:02:08). - Improve: no source for any figure. Show where 84% comes from and a logical learner can check the rest. #### 🧑‍🤝‍🧑 Social learners - Present: YouTube comments; a newsletter link in the description. - Improve: no discussion prompt. "Would you have voted with the board?" would start one. #### 🧘‍♀️ Solitary learners - Present: short, self-contained, rewatchable. - Improve: a reflection question would make it an exercise. #### 🌿 Naturalistic learners - Present: none beyond the desert setting used for jokes. - Improve: one distribution point feeding every install is a monoculture argument; the raw material is at 00:02:08. ## 📊 Accessibility assessment #### Screen reader semantics - Present: YouTube landmarks and player controls; machine-readable auto-transcript; plain-text description. - Improve: memes, clips, and screenshots carry unspoken meaning. WCAG 2.2 AA 1.1.1 and 1.2.5 aren't met. #### Keyboard navigation - Present: the player is keyboard operable with visible focus. - Improve: nothing in the content adds barriers; 2.1.1 and 2.4.7 pass via the platform. #### Contrast and readability - Present: unverifiable from the transcript; white-on-dark house style typically passes 1.4.3. - Improve: meme captions and screenshots risk failing 1.4.3 (Contrast Minimum) on mobile. #### Text resizing and reflow - Present: the player scales; captions resize independently. - Improve: burned-in text doesn't resize. 1.4.4 (Resize Text) and 1.4.10 (Reflow) fail for anything baked into the frame. #### Media and captions - Present: an auto-transcript exists and is the basis of this analysis. - Improve: captions spell the company two ways, render two names in unverified forms ("Tony Schneider," "Andy Masaan"), and mark inserted clips with ">>" and no speaker label. A 1.2.2 (Captions, Prerecorded) failure in substance; corrected captions for 5:23 are cheap. No chapters exist. #### Forms and interactions - Present: none in-video; the sponsor link is "the link below." - Improve: not applicable in-video; 3.3.2 (Labels or Instructions) applies to the sponsor landing page. #### Standards reference - Primary gaps against WCAG 2.2 AA: **1.2.2** (inaccurate captions on names), **1.2.5** (no audio description for screenshots and clips), **1.1.1** (visual jokes conveyed visually only), **1.4.4 / 1.4.10** (burned-in text). The caption fix is highest impact and lowest cost. ## 🌍 DEIB assessment #### Cultural breadth - Present: US-centric by nature (a California company, Burning Man, Labor Day); assumes familiarity with the OpenAI board episode and Survivor. - Improve: one non-US founder-control example would show the pattern isn't local. #### Inclusive language - Present: no slurs or gendered generics; second person throughout. - Improve: "martyrdom complex that would make Al-Qaeda proud" (00:00:00) uses a terrorist group as a punchline; "microdosing homelessness" (00:00:42) makes homelessness the joke; "covered in feces" (00:01:25) is a bodily insult at a named person. None carries information. #### Neurodiversity support - Present: strict chronology and a three-part structure announced at 00:00:42. - Improve: a joke every 10 to 15 seconds and figures with no pause are a processing load. No chapters. #### Representation - Present: one narrator; two inserted voices, one of them Mullenweg. - Improve: no board, employee, WP Engine, or Silver Lake voice; only the winner is quoted at length. #### Psychological safety - Present: causal claims hedged ("one theory," "Matt's theory," "most likely"). - Improve: employees "still in the dark" (00:04:16) become a sponsor segue; viewers who depend on wordpress.org get no statement of what did or didn't change operationally. ## ✅ Logical validity #### Strong reasoning - **Deductive, 00:02:51.** If one shareholder holds 84% of the votes, that shareholder can replace the board, and a replaced board can reinstate the CEO. The conclusion follows from the premise. The premise is unsourced; the inference is valid and is the spine of the story. Clarify by naming where 84% comes from. - **Attribution discipline, 00:02:08.** Three explanations sorted by owner: the board gave none; "one theory" (unowned) concerns the litigation; "Matt's theory" concerns Silver Lake. He endorses none. This is how to present competing causal claims you can't adjudicate. - **Marked inference, 00:02:08.** "most likely referring to wordpress.org" flags the reading as the narrator's own. The hedge does real work and should survive any summary. - **Reading the omission, 00:03:34.** Automattic's "full support of the board" omitted that the board was new: a fair observation, if both facts hold, about a statement being true and incomplete at once. - **Analogical, 00:00:00.** "tried to pull an open AI" compresses a structural parallel (board removes founder, founder returns, board changes) into three words. It breaks on mechanism: by the narrator's own 84% point, this founder returned through votes, not pressure. #### Fallacies - **Ad hominem by loaded comparison, 00:00:00.** "a martyrdom complex that would make Al-Qaeda proud." Characterizes motive through comparison to a terrorist group; no evidence about events; primes the viewer to read later actions as performance. *Fix:* cite the statements that show a martyrdom framing (the "stand up to bullies" clip is one) and let the viewer judge. - **Appeal to ridicule, 00:00:42 and 00:01:25.** "microdosing homelessness at Burning Man"; "seemingly still covered in feces from the playa." Mockery in place of the relevant fact (he was away when the board acted). *Fix:* state the fact, drop the imagery. - **Bare assertion of quantified claims, throughout.** 80% (00:00:42), 84% (00:02:51), "over $8 million" (00:03:34), 42 years (00:00:42, 00:02:51), 20 months and two phones (00:02:08). No document, filing, or reporter named for any. *Fix:* attribute each on screen or in the description; name the docket where the source is a filing. - **Insinuation of motive without evidence, 00:03:34.** "had drafted their own severance agreements... A good work if you can get it." Implies self-dealing; the transcript never says who approved the terms or whether they're standard for interim leadership. *Fix:* state who approved them or say it's unknown. - **Speculative causation with no owner, 00:02:08.** "removing the guy who may have destroyed evidence might make a judge go easier on the company." Two modal hedges on an unsourced causal chain. Labeling it "one theory" mitigates but doesn't remove the problem. *Fix:* attribute it or cut it. - **Hasty generalization, 00:00:00.** "employees told TechCrunch they were ecstatic." An unstated number speaks for a workforce of unstated size. *Fix:* "some employees," or a count. - **Mixed evidentiary status in one sentence, 00:02:08.** The tweet's meaning is hedged; wordpress.org's ownership and function are stated flat, in the same breath. *Fix:* source the ownership claim separately. #### Tone of voice - Sardonic, fast, second-person, in Fireship's standard register. Every party is mocked: the board for the 50-minute ultimatum, Mullenweg for the pirate framing, the executives for the severance, the employees for the houseboat post. The contempt is even-handed; the evidence isn't: only one side is quoted at length (00:02:51, 00:03:34), and the board's reasoning is represented by its absence. The most careful stretch is 00:02:08 to 00:02:51, where theories are sorted by owner and the narrator flags his own inference; the least careful are the open (00:00:00 to 00:01:25) and the severance line at 00:03:34, where jokes replace sources. Reading rule: trust the sequencing, verify the numbers, discard the adjectives. ## 🛡️ DARVO analysis Two layers need separating. The narrator is not an accused party and mounts no defense, so DARVO as a speaker's self-defense pattern doesn't apply to the video's own argument. But the video narrates a live dispute in which several statements attributed to the parties fit the template, and it characterizes them. Each item below describes what the narrator reports, not what anyone actually said, and needs the underlying post checked. - **Deny.** Narrator: nothing to deny; he makes no claims about his own conduct and hedges his inferences. Narrated parties: the board "never gave him a reason" (00:02:08), which is silence, not denial. Automattic's Saturday statement, as read at 00:03:34, affirms "full support of the board" without saying the board changed; the narrator treats this as minimization by omission. Mullenweg's reported "not a troll" line (00:03:34) denies a characterization, not an accusation of wrongdoing. Verify: the statement text; the TechCrunch exchange. - **Attack.** Narrator: he attacks Mullenweg's character (00:00:00, 00:01:25) and the executives' motives (00:03:34), but as a commentator, not as a party deflecting an accusation, so these are ad hominem fallacies (above), not DARVO moves. Narrated parties: Mullenweg's reported Slack posts call colleagues "turncoats" (00:02:51) and his reported claim that Davies "conspired with the board behind his back" (00:01:25 to 00:02:08) impugn the loyalty of those who voted. WP Engine's reported evidence-destruction accusation (00:02:08) is an attack in the legal sense, attributed to WP Engine. Verify: published screenshots; the court record. - **Reverse victim and offender.** Narrator: none; he claims no victim status. Narrated parties: the narrator reports Mullenweg's theory that Silver Lake "was involved in a plan to destroy his life" (00:02:08) and his tweet framing the vote as a "coup attempt" that signals "strong enough leaders" (00:03:34). Both recast the removed CEO as target of a plot and the board as instruments of an outside offender, the structural shape of a reversal. The narrator's "martyrdom complex" (00:00:00) is his editorial label for the pattern. Whether the reframing is accurate isn't decidable from this source; the pattern is present in the narration regardless. The inserted clip at 00:00:00 ("stand up to bullies... protect your open source ideals") frames his conduct as community defense; its original context isn't given. Verify: the tweet, the Reddit post, the clip's source. - **Emotional cues and rhetoric.** The narrator's register is ridicule, not grievance. Reported rhetoric from Mullenweg (pirate, cursing after 42 years, turncoats, coup) is grievance and defiance as presented. The board and executives have no reported rhetoric. Any DARVO reading from this video weighs one side's public voice against the other's silence: a reason to seek the board's account, not a conclusion about who wronged whom. ## 🎯 Conclusion The video's durable contribution is one deduction and one description. The deduction, at 00:02:51: a CEO with 84% of the votes can't be durably removed by a board that serves at that shareholder's pleasure. If the figure is right, the vote was a gesture with a 33-hour half-life. The description, at 00:02:08: wordpress.org as a personally owned single point of distribution for every install's plugins, themes, and security updates, with a tweet from the removed CEO read by the narrator as a plan to move it. The reading is flagged as inference; the description under it is the thing to verify, because it links a private company's board fight to the ecosystem's supply chain. Everything else is claim. Fifteen events and 15 figures arrive with no on-screen source; the board's reasoning is represented by silence; the fired executives are implied to have self-dealt without any statement of who approved their terms; the character attacks at 00:00:00, 00:00:42, and 00:01:25 carry no information. **Next steps for readers:** work the table's "verify against" column before answering anyone: Automattic's statements, TechCrunch, the tweet and Reddit post, the WP Engine docket, then Make WordPress. Where a row has no primary source, say "Fireship reports" and nothing stronger. Keep two questions apart: what happened to Automattic's board, and what, if anything, happened to wordpress.org. On the second, the video reports a tweet and an inference, not a change. ## 🔄 Refactor Appendix — The most expensive 33 hours in WordPress history... > Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 3 Literature, 1 Permanent. Resonance filter applied: the severance, > 80% devaluation, and 42-years-without-swearing claims went to Fleeting as > unsourced figures rather than reusable ideas. > > 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] Founder voting control makes board removal reversible > [!quote] [00:02:51] > And he's not wrong because he holds 84% of Automattic's voting power. **Context & use**: - 00:02:51, explaining the Reddit post in which Mullenweg says he could fill board seats whenever he wanted. - The one deductively valid argument in the video. If 84% is right, the vote was a signal, not a removal. The number is unsourced; the mechanism is sound. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H2] wordpress.org is a personally owned single distribution point > [!quote] [00:02:08] > most likely referring to wordpress.org, the site he owns personally, where every WordPress install downloads its plugins, themes, and security updates from. **Context & use**: - 00:02:08, the narrator's reading of a tweet about moving "stuff off automatic servers." - Two claims with different status in one sentence: the tweet's meaning is hedged; wordpress.org's ownership and function are stated flat. Verify the second against Make WordPress and any court record before reuse. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H3] A 50-minute notice period defines the board's process > [!quote] [00:01:25] > he received a written proposal from his board stating that in 50 minutes, they'd be voting to remove him as CEO **Context & use**: - 00:01:25, the return from Burning Man, followed by the refused request for time for a lawyer. - The procedural fact colleagues will ask about first, and the one the board's side would need to answer. Unsourced; the written proposal, if it surfaces, is the primary document. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] A board the CEO can replace is a signaling body, not a check **Claim** (one sentence, Courtney's voice): When one person holds majority voting power, the board's power to remove them is ceremonial, so real accountability has to come from outside the company: courts, customers, or the community that depends on its infrastructure. **Evidence pointer**: [[#H1]] · [[#H3]] **Scope & conditions**: Holds when a single holder controls a majority of votes with no sunset, no independent-director veto, and no protective provision minority holders can enforce. Breaks under sunset clauses, supermajority rules for director changes, or a credible fiduciary-duty suit. The narrator's 84% is the unverified premise; the claim stands or falls with it here. **Links**: - [[Open source governance]] — because extends - [[FAIR anti-capture covenants]] — because applies-in distribution infrastructure under one controlling person - [[OpenAI board crisis 2023]] — because contrasts on mechanism of return, pressure versus votes <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Verify the five caption-spelled names ("Tony Schneider," "Andy Masaan," and the three others) against Automattic's leadership page before naming anyone — https://www.youtube.com/watch?v=ylO0DQeVEBQ&t=85 #fleeting #inbox - [F2] Confirm whether the September 9 return and the vote were the same day; my derived dates (Friday Sept 11, Saturday Sept 12) depend on it #fleeting #inbox - [F3] Find the source for "over $8 million" and the severance terms at 00:03:34, and for the 80% devaluation at 00:00:42; retire any figure with no source #fleeting #inbox - [F4] Retrieve the September 10 tweet and check whether it names wordpress.org; "most likely" at 00:02:08 is an inference #fleeting #inbox - [F5] Article seed: "Trust the sequencing, verify the numbers, discard the adjectives," a reading rule for comedic explainers that become the first draft of record #fleeting #inbox #articleseed ### → Things 3 (max 2 actions) - [ ] Verify the timeline table against Automattic's statements, the two TechCrunch pieces, and the Sept 10 tweet, marking each row verified or narrator-only — WP governance, 45 min #things - [ ] Draft a one-page "verified vs what Fireship claims" note for colleagues, leading with the wordpress.org distinction — DevRel, 30 min #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/The Most Expensive 33 Hours in WordPress History....md|The Most Expensive 33 Hours in WordPress History... by Fireship]] ## Highlights - [00:01:25] seemingly still covered in feces from the playa, he received a written proposal from his board stating that in 50 minutes, they'd be voting to remove him as CEO of a company he started 21 years ago. Then he asked for a few hours so his lawyer could read their proposal. The board said no. Then 50 minutes later, CFO Mark Davies, with the help of board members Sue Decker, a retired four-star general named Ann Dunwoody, and Tony Schneider, the same guy Matt hired to be Automattic's first CEO and who he once called his business soulmate, sealed his fate. >> The tribe has spoken. >> And so then Matt did what any of us would do in a similar situation if we were filthy rich and HR hadn't cut our Slack access yet. He posted that he wouldn't be at the leadership meeting the next day because Davies had [00:02:08] conspired with the board behind his back. And though they never gave him a reason, Matt assumed it was because of his ongoing legal issues with WP Engine, which spent the summer accusing him of destroying evidence in the case after 20 months of his signal history and two of his phones went missing. So, one theory is the board figured removing the guy who may have destroyed evidence might make a judge go easier on the company. But Matt's theory is that Silver Lake, the private equity firm behind WP Engine, was involved in a plan to destroy his life. Then the next day, he tweeted that he needed to hire security researchers to move some of his stuff off automatic servers, most likely referring to wordpress.org, the site he owns personally, where every WordPress install downloads its plugins, themes, and security updates from. Then things got even weirder in Slack. Matt wrote, ([View Highlight](https://read.readwise.io/read/01m3898n4ym2yw5x2d8jr9z8dr)) - Note: [H2] wordpress.org is a personally owned single distribution point - Tags: atom/literature/h2 - [00:02:51] and I quote, "Oh, since I'm a pirate now, I curse." After 42 years of never uttering a curse word, it's kind of fun. Then he said, "The Slack smells funny like turncoats." Removed every other admin and moved to the wordpress.org Slack where a pirate flag emoji appeared next to his name. But the more insightful post came from Reddit where he told someone asking about replacing the board that he could fill seats on the board whenever he wanted, but that wasn't the point. And he's not wrong because he holds 84% of Automattic's voting power. The board can vote him out and he can replace the board with members who will vote him right back in, which is exactly what happened. Early Friday morning, he returned to the announcements channel in Slack and posted that the board was back in agreement and he was back in control. He then tweeted that if you don't have a [00:03:34] coup attempt every few years, you're not hiring strong enough leaders. TechCrunch asked if he was trolling and he eventually told them that he's not a troll, he's a pirate. By Saturday, Automattic confirmed Matt was CEO again and had full support of the board. But what they didn't mention was that the entire existing board was gone and Matt fired Davies and chief legal officer Andy Masaan as well. In total, Matt was gone for 33 hours, but in that time, Davies and Masaan, the two executives running the company while Matt was out, had drafted their own severance agreements where if they were fired, they'd be paid out a full year's salary, a year of health insurance, and all of their stock would immediately vest. Then Matt came back, fired them both, and Automatic now owes them over $8 million. A good work if you can get it. ([View Highlight](https://read.readwise.io/read/01m3898jv53b5605jc2xm4n4zr)) - Note: [H1] Founder voting control makes board removal reversible - Tags: atom/literature/h1