# Episode 31: Brent Toderash (Community and Code) > [!question] Lingering Questions > - Does TYPO3 v14's FAIR integration actually touch protocol core, or is the extension boundary confirmed clean? (the episode asserts it, but the commit-range verification is unpublished) > - Who pays for federated mirror operation at scale — the episode never addresses the funding question, and it's load-bearing for the whole federation model. > - Does the "everything's been done before, it's all proven" claim survive integration testing, where composed supply-chain systems usually fail? Component-proof isn't composition-proof. > - What is the trust model for a new mirror joining the federation, and who can revoke one? > [!tip] Article Ideas > - "Liability, not ideology" — a piece for WordPress agency owners reframing FAIR/supply-chain-independence adoption as a procurement/liability decision rather than a factional one. > - Short post on how misattribution travels through secondary quotation (Toderash attributes "write one to throw away" to *The Cathedral and the Bazaar*; it's Fred Brooks, *The Mythical Man-Month* — Raymond quotes Brooks, likely the source of the conflation). > [!link] Cross Reference > - [[3. Resources/MOCs/Open Source Governance MOC]] — FAIR/TYPO3 protocol governance, multi-consumer standards > - [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]] — already promoted from this source (2026-08-01); the core claim of the episode > - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — "leverage, don't delegate" AI framing > [!quote] Vocabulary > - **protocol extension** — FAIR's mechanism for CMS-specific behavior; kept out of protocol core so a second CMS (TYPO3) could adopt the protocol without core changes > - **federation** — a network of independently-operated mirrors serving packages, as opposed to a single canonical repository > - **phoning home** — recurring callback requests a WordPress site makes to .org; FAIR Connect suppresses these ## Metadata - Source: [[3. Resources/Readwise/Articles/Episode 31 Brent Toderash|Episode 31 - Brent Toderash]] - Host: Chris Reynolds; Guest: Brent Toderash (FAIR technical steering committee, WordPress agency co-owner) - URL: https://www.youtube.com/watch?v=Lfs9E13Ozbc ## Author's thesis FAIR was never a WordPress project — it's a software-supply-chain protocol for digital goods, with all WordPress-specific behavior living in protocol extensions rather than core. TYPO3 v14 shipping FAIR support in core converts that design claim into a demonstrated one: a second, independent CMS adopted the protocol through the same extension mechanism. Toderash's own path into FAIR was risk management — a professional-liability response to a September 2024 WordPress supply-chain risk exposure, not an ideological choice. A separate AI-adoption thread runs alongside: "leverage, don't delegate," evidenced by a self-reported 40% cost saving on a client estimate, and the claim that cheap AI-assisted regeneration weakens the sunk-cost trap that keeps people committed to wrong technical paths. ## Key arguments (≤3) 1. **Portability is proven by a second implementer, not by design intent.** FAIR's core/extension separation was, for a year, an untested assertion; TYPO3's arrival through the identical extension mechanism converted it into a checkable claim, since a cosmetic extension layer couldn't have absorbed a genuinely independent CMS. 2. **Liability, not ideology, is what moved a working consultant to adopt supply-chain infrastructure.** Toderash frames his FAIR participation explicitly as risk management: the concrete fear is a client saying "you're the professional, you told me to build on this" after a platform's distribution channel became uncertain. 3. **Cheap AI-assisted regeneration weakens the sunk-cost trap.** "Write one to throw away" felt prohibitively expensive before; if restarting is now cheap, commitment to a wrong technical path — including accumulated technical debt — has a lower switching cost, extending even to defensive security work (using AI to find and patch vulnerabilities as attackers use it to find them). ## Claim atoms ### FAIR targets supply chains, not WordPress > [!quote] ID: rw_01kywpaqnq7wfvtb4mqx9e02ra > it's not a WordPress thing. And there's a lot of misconception here Where/why: ~57:13, immediately preceding the TYPO3 v14 announcement. All WordPress-specific behavior is protocol extensions, never baked into core — the claim TYPO3 adoption converts from assertion to evidence. ### Proven components, unproven composition > [!quote] ID: rw_01kywpaqnq7wfvtb4mqx9e02ra > it's all the Lego bricks that you can imagine and they're all proven, but nobody's seen this thing before Where/why: ~55:15, the "gold standard" passage. The honest, narrower version of FAIR's novelty claim — and also its weak point, since integration is where composed supply chains typically fail. ### Leverage AI; do not delegate to it > [!quote] ID: rw_01kywpaqnq7wfvtb4mqx9e02ra > AI is something you leverage. It's not something you just delegate to. Where/why: ~20:08, the pivot of the AI thread. Task comprehension is the binding constraint on prompting — if you can't understand the task, you can't write the prompt. ### Consultant liability drove FAIR participation > [!quote] ID: rw_01kywpaqnq7wfvtb4mqx9e02ra > You gave me bad advice and I trusted you as a professional. Where/why: ~45:39, answering "what attracted you to FAIR" with "risk management." Reframes supply-chain independence as a procurement/liability question rather than an ideological one. ### Cheap regeneration dissolves sunk-cost attachment > [!quote] ID: rw_01kywpaqnq7wfvtb4mqx9e02ra > But with AI, that equation has just changed like drastically. Where/why: ~39:48, on "write one to throw away" (misattributed in-episode to Raymond; the line is Brooks's). The economic claim underneath the AI thread — if restarting is cheap, commitment to a wrong path weakens. ## Permanent candidates - **Portability is proven by a second implementer, not by design intent** — already promoted: [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]]. Do not duplicate. - **Task comprehension bounds delegation quality** ("leverage, don't delegate") — distinct from the existing [[3. Resources/Permanent Notes/Delegation Difficulty Is Scoping Not Capability]] (that note is about auditability/permissioning; this is about prompt quality requiring task understanding). Promoted below. - **Liability is a faster adoption lever than ideology** — no existing note captures this. Promoted below. ## Processing checklist - [ ] Diff TYPO3 v14's FAIR integration against protocol core to verify the extension-boundary claim - [ ] Ask FAIR TSC for a published threat model covering mirror compromise and content divergence - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Open Source Governance MOC]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — FAIR/TYPO3 multi-consumer protocol governance - [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]] — the episode's central claim, already promoted