# Liability Is a Faster Adoption Lever Than Ideology ## Claim A practitioner who carries advisory responsibility to a third party adopts infrastructure independence faster when framed as professional-liability management than when framed as a principled or ideological stance, because the liability framing converts an abstract preference into a concrete, personally-owned risk. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds where the practitioner has explicit advisory or professional responsibility to a third party (a client, an employer, a board) who could later hold them accountable for a recommendation. - Requires the alternative infrastructure to have comparable switching cost to the status quo — if the "safer" option is dramatically more expensive or disruptive, liability alone may not overcome that gap. - Breaks for hobbyists, in-house teams with no external client relationship, or anyone without a third party who could plausibly say "you told me to build on this" — the liability channel doesn't exist for them, so the lever has nothing to pull. - Doesn't establish that ideological arguments are ineffective generally — only that liability moves this specific population (practitioners with advisory exposure) faster than principle does. ## Evidence Brent Toderash answers "what attracted you to FAIR" with a single word — "risk management" — drawing directly on a prior career as an insurance broker analyzing risk. The concrete fear he names is professional liability: a client who was advised by him, as a professional, to build an application on WordPress, later saying "you gave me bad advice." A September 2024 WordPress supply-chain risk exposure is what triggered the search for alternatives; blog posts explaining how to self-host a package repository didn't move him because they didn't address the liability, only the technical possibility. > [!quote] > You gave me bad advice and I trusted you as a professional. ## Links - [[3. Resources/Permanent Notes/Structural Power Claims the Position of the Party Being Acted Upon]] — because contrasts; that note is about institutional power reframing dissent as aggression, this note is about an individual practitioner's own liability exposure driving a genuinely defensive infrastructure choice — different actors, different direction of the framing. - [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]] — because applies-in; the liability motive is why Toderash personally cared whether FAIR's portability claim was real rather than asserted — his exposure depended on the answer. - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; adoption-driver analysis for infrastructure decisions. ## Tests / falsifiers - Survey agency/consultant adoption of FAIR (or comparable supply-chain-independence tooling) and check whether adoption correlates with client-application complexity and advisory exposure, as the liability framing predicts, rather than with contributor status or ideological alignment with open source. - Find a comparable case where a principled/ideological pitch produced adoption at a rate matching or exceeding a liability-framed pitch to the same population — if common, "liability is faster" doesn't generalize as strongly as this single case suggests. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Episode 31 - Brent Toderash (Community and Code)]] — Brent Toderash's "risk management" answer and the client-liability framing for his FAIR participation.