Corrections · Agent Mode AI

The public record of every correction applied to an Agent Mode AI article. When a tracked claim moves from Holding to Partial or Not holding, the correction is dated and listed here — and never removed. If a piece is retracted entirely (fabricated sources, unfixable errors), that goes on /retractions/ instead.

Date	Kind	Claim / Article	Note
19 Apr 2026	Partial	Salesforce's 9,000-person redeployment: the template most enterprises will copy AM-017	Anchor 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 2026	Partial	Salesforce's 9,000-person redeployment: the template most enterprises will copy AM-017	Body 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.
19 Apr 2026	Partial	Back-office vs front-office: where agentic AI's economics actually compound AM-018	Anchor verification complete (see audit/ANCHOR_VERIFICATION_2026-04-19.md). 'Sarah Chen' and the 2 AM Munich-hotel scenario are fully fabricated — the article's narrative protagonist does not correspond to any real executive. The underlying framework (back-office cost compounding faster than front-office wins; per-action delta × frequency) IS defensible against McKinsey + Futurum operational-AI-ROI data. Rewrite required before the article can move to Holding.
19 Apr 2026	Partial	Back-office vs front-office: where agentic AI's economics actually compound AM-018	Body rewritten. Fabricated 'Sarah Chen' narrative frame removed entirely. Claim spine sharpened: original was 'back-office cost compounding faster than front-office'; new version adds the structural explanation (per-action × frequency × task-specification × measurement instrumentation) and specific 2026 benchmark anchors (Stanford DEL 12%/88%, Gartner 28%, Futurum 71% vs 40%). Status moves from Partial to Up. Cross-links to AM-020 (TCO), AM-021 (measurement discipline), AM-022 (bimodal ROI) explicitly drawn in the body. Next review 18 Jun 2026.
19 Apr 2026	Partial	Manufacturing 4.0: How multi-agent systems reduce downtime by 30% AM-019	Body rewritten. Original headline number (30% downtime reduction) survives against current case-study data. New analytical spine: the audit-trail architecture separates wins from stalls. Status moved from rewrite-in-progress Partial placeholder to Up. Next review 60 days out because architectural claims age slower than pricing claims.
19 Apr 2026	Partial	The hidden costs of agentic AI: a CFO's guide to true TCO and ROI modeling AM-020	Body rewritten from WP-era slop. Status moves from rewrite-in-progress placeholder to Up. New analytical spine: the TCO underestimate is cross-departmental cost-attribution failure, not hidden costs. Five cost categories named with budget owners. 60-day review cadence.
19 Apr 2026	Partial	From DMAIC to AI agents: how traditional optimization methods accelerate agentic AI success AM-021	Body rewritten from WP-era slop. Status moves from rewrite-in-progress placeholder to Up. New thesis: the causation runs the opposite direction from the vendor narrative — the measurement discipline was the prerequisite, the methodology name doesn't matter. 60-day review.
19 Apr 2026	Partial	The agentic AI success formula: what 171% average ROI actually hides AM-022	Body rewritten from WP-era slop (7-patterns vendor framework with fabricated case studies). New thesis: bimodal distribution, not normal — the 171% average describes no specific deployment. Business-line kill-switch ownership is the single distinguishing factor. Cross-links to AM-020 + AM-021 on the shared organisational-precondition thread.
19 Apr 2026	Partial	Google AI Mode restaurant booking: the template for every partner-aggregation vertical AM-023	Body rewritten from WP-era slop (the '$50 Billion Revolution' headline and 'act within 90 days' crisis-FOMO framing were both fabrications). New thesis: restaurant booking is a template, not the story. Named 5 enterprise-relevant aggregation verticals (business travel, expense, procurement, ATS, HR service) and the API-backend-vs-destination choice incumbents face. Next review in 60 days.

Correction policy → editorial standards · Retractions → permanent record