Semantic Drift

Core Summary Simon Willison highlights a critical internal policy by Sophie Alpert regarding AI-assisted engineering documentation. The central thesis: natural language undergoes "lossy" transformation when processed by LLMs, mandating that human authors maintain total accountability for every word and nuance in the final output. ▶ Rewriting as Re-encoding: LLM-based polishing is not a benign grammar check; it is a probabilistic reconstruction that risks losing subtle technical nuances or original intent. ▶ Non-Transferable Liability: Authorship equals accountability. Using AI as a "ghostwriter" does not absolve the human signatory from errors, hallucinations, or logic gaps introduced by the model. Bagua Insight While the industry obsesses over factual hallucinations, this perspective flags a more insidious threat: Semantic Drift. In high-stakes engineering environments, the "hallucination of tone or logic" is as dangerous as the hallucination of facts. We are witnessing a fundamental shift in the definition of professional competence. As LLMs lower the barrier to "fluent" writing, the value of a professional now lies in their editorial integrity. Sophie Alpert’s stance challenges the "autopilot" hype, asserting that in the loop of human-AI collaboration, the human is not a passenger but the Chief Auditor. If you can't defend a sentence the AI wrote, you didn't write the document—you merely prompted it. Actionable Advice Adopt a "Review-Before-Commit" Protocol: Treat AI-generated text as a draft that requires 100% manual verification. Never accept "Refine" suggestions without a side-by-side diff analysis. Prioritize Precision over Fluency: In technical communication, a clunky but accurate sentence is infinitely superior to a polished but vague one. Train teams to spot where AI "smooths over" necessary complexity. Implement Attribution Standards: For internal documentation, consider tagging sections that were AI-enhanced to alert reviewers to potential semantic drift points.