> [!question] Lingering Questions > - Was any level-0 objection ever evaluated on its technical merits before being classified as principled opposition? No criterion is offered for exiting the category by argument. > - What actually distinguishes level 0 from level 1 operationally — zero usage, or expressed disagreement? > [!tip] Article Ideas > - "Write the informed-dissent branch before you need it" — for anyone designing a tool-adoption programme, built on this clip's central gap. > [!link] Cross Reference > - **Already fully captured as Permanent notes** — [[3. Resources/Permanent Notes/Structural Power Claims the Position of the Party Being Acted Upon]] and [[3. Resources/Permanent Notes/Loyalty Tests Recode Dissent as Betrayal]] both source this exact clip. This Literature note connects the source properly; no new Permanent note is warranted here (connect, don't duplicate). > - Sibling clip [[3. Resources/Literature Notes/The CEO Goes First]] — the incentive half of the same programme; read as a pair, since either alone misrepresents it. > - Sibling clip [[3. Resources/Literature Notes/The Machine Doesn't Cook for You]] — supplies the sympathetic psychological account of the exact behaviour this clip penalises. > [!quote] Vocabulary > - **adoption maturity scale** — internal 0–3 levels; 1–3 treated as a skill gap, 0 ("not engaged") treated as opposition > - **not engaged** — the company's term for employees who dismiss AI as hype or decline to use it for security work ## Metadata - Source: [[3. Resources/Readwise/Articles/A Disagreement on Principles, Not on Skills]] - Category: Video (YouTube short-form clip) - Published: 2026-07-31 ## Author's thesis Employees who hadn't yet gotten good with AI tooling were treated with patience; employees who held a position — dismissing AI as hype, or judging it unsuitable for security work — were reclassified as opposing the company's direction, escalated to HR, and some left. ## Key arguments 1. **The skill/will split is real but binary where it needed a third branch**: incapacity gets time; opposition gets HR; there is no category for "evaluated it and judged it unsuitable." 2. **Both named examples of "not engaged" are positions, not refusals to try** — one of them a professional judgement about tool suitability in the company's own domain, which is exactly what senior security staff are hired to make. 3. **Reclassifying a technical disagreement as a loyalty question removes it from the reach of evidence** — principles aren't settled by benchmarks, so the objection becomes unanswerable rather than answered. ## Claim atoms ### Non-engagement is reclassified from skill gap to values opposition > [!quote] ID:rw_01kywpajsmrdsa6m0qmda653p0 > If you're in level zero though, if you're not engaged, that means you're fighting back against the company. It means that uh, you are you have not adopted the vision and the direction that the company is now going in. *Where:* ~00:00:00. *Why:* the pivot the whole policy turns on — everything above this line gets patience, everything at it gets HR. ### The examples given are positions, not refusals > [!quote] ID:rw_01kywpajsmrdsa6m0qmda653p0 > if you dismiss AI as hype, if you refuse to use AI for security work. This is a disagreement on principles, not on skills. *Where:* ~00:00:00. *Why:* the second example is a professional judgement in the firm's own domain; the framework has no category for it being correct. ### The consequence is stated without euphemism > [!quote] ID:rw_01kywpajsmrdsa6m0qmda653p0 > for people that were stuck in the not engaged category, we had hard conversations with our HR team, and uh, there were people that left the company *Where:* ~00:00:31. *Why:* candour worth crediting — most organizations describe this as attrition; note the passive framing that locates cause in the employee's "stage." ## Permanent candidates - Already captured: [[3. Resources/Permanent Notes/Structural Power Claims the Position of the Party Being Acted Upon]] (the DARVO-adjacent inversion — the company holds all the power yet frames itself as the party being fought). - Already captured: [[3. Resources/Permanent Notes/Loyalty Tests Recode Dissent as Betrayal]] (the skill/will reclassification mechanism). ## Processing checklist - [ ] Find the parent talk for the maturity-scale definition - [ ] Check whether Trail of Bits has written publicly about the adoption programme - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Commons & Community Governance MOC]] - [x] Confirmed existing Permanent notes already cover this source's central claims — no duplicate created ## Links - [[3. Resources/MOCs/Commons & Community Governance MOC]] — how institutions describe those who disagree with them. - [[3. Resources/MOCs/AI Agent Safety MOC]] — the corporate instance concerns an AI-adoption mandate and who bears the cost of doubting it. - [[3. Resources/Permanent Notes/Structural Power Claims the Position of the Party Being Acted Upon]] — existing Permanent note, this source is one of its four cited instances. - [[3. Resources/Permanent Notes/Loyalty Tests Recode Dissent as Betrayal]] — existing Permanent note, directly applicable mechanism.