AM-017
← Back to ledgerNot holding·last review28 Apr 2026
Agentic AI's durable enterprise pattern is redeployment-first, not replacement-first. The Salesforce Agentforce sequence — announce redeployment paths before automation ships, fund retraining from the automation budget, co-locate accountability — is the working template most enterprises are copying. Replacement-first announcements produce measurably worse adoption + sales-cycle outcomes.
Based on 2025-2026 public-case distribution: Salesforce/Microsoft/Google following redeployment-first pattern with positive signals, IBM-style replacement-first showing adoption drag. Stanford DEL 2026 + Gartner Q1 2026 as analytical anchors. 60-day review cadence because workforce-transition frames can shift quickly with any major public reversal.
Source piece
Salesforce's 9,000-person redeployment: the template most enterprises will copyRead piece →Correction log
- 19 Apr 2026Article predates the Holding-up standard. Retroactive claim assigned on 19 Apr 2026. Initial verdict 'Partial' — spine is defensible, per-claim numeric verification deferred to +60d review. Body not rewritten per AGENTMODE_PHASE2_BRIEF §114.
- 19 Apr 2026Anchor verification complete (see audit/ANCHOR_VERIFICATION_2026-04-19.md). The Salesforce Agentforce redeployment of ~9,000 support engineers is a real, widely-reported Benioff-era story, but the specific text-message transcript in the article is a fabricated dramatisation. Spine (opt-in beats mandate) is defensible at principle level, but the Salesforce story is not the right case for it — that transition was management-directed. Rewrite flagged for before 18 Jun 2026 review.
- 19 Apr 2026Body rewritten. Fabricated text-message transcript removed. Claim spine retargeted from 'workforce opt-in beats mandate' (Salesforce is not that case) to 'redeployment-first beats replacement-first' (the pattern Salesforce actually executed). Status moves from Partial to Up. Next review 60 days out (18 Jun 2026) to check for counter-evidence — see Holding-up note in the rewritten body.
- 28 Apr 2026Article retracted 28 Apr 2026. Slug premise ('asked to be replaced') is the dramatized framing the body had to remove on 19 Apr 2026. The Salesforce 9,000-person redeployment is a real, defensible event but the slug attaches an invented framing to it. Body preserved in archived/. Google has independently rejected the URL. URL now redirects to /retractions/?retired=the-day-9000-people-asked-to-be-replaced. Claim withdrawn — status moves to Not holding, no further reviews scheduled.
Permalink
/holding/AM-017/Embed this claimiframe + oEmbed
HTML iframe
Paste-the-URL (Substack, Medium, Notion, WordPress)
The card auto-updates when the claim's status, last-reviewed date, or correction log changes. Embedders never need to refresh — the card is rendered live from the canonical record.