把大模型纠错当系统运维，建立可持久化的错误治理机制
Tuning the Stochastic Machine: A Systems Engineer's Operating Model for Human-AI Engineering
- 将大模型系统类比为硬件设备，引入版本控制与追溯机制
- 发现纠错规则常因无淘汰机制而反成危害，如某控制自毁式失效
- 适合从事AI工程化、系统级部署的工程师参考
当专家修正大模型错误时，修正结果通常随会话消失，错误类别反复出现。这并非工具问题，而是操作管理缺失：已有持久化修正机制在部署，但缺乏版本追踪、重复监测、反向指标和过时规则退役等治理规范。作者以三十年系统工程经验，将大模型栈映射到已有工业系统（固件、可加载模块、持久配置、易失内存），指出其失败点在于随机生成、概率绑定配置，且默认无通用验证或退役阶段。由此提炼出包含七原则的运营准则，核心为闭环纠错机制。三个实践案例说明该机制，其中一例显示控制逻辑最终演变为它本要防范的伤害。最后提出相应的度量框架及需开展的实验室研究。
原文摘要 · Abstract (English)
When an expert corrects an LLM assistant's error, the correction usually dies with the session, and the error class returns. I argue this is an operations problem, not a tooling problem: mechanisms for persisting corrections exist and are shipping, but the discipline for governing them -- versioning with provenance, recurrence monitoring, counter-metrics, retirement of stale rules -- does not. Writing as a systems engineer of thirty years, I map the LLM stack onto the machines my profession already operates (frozen silicon, firmware, loadable modules, persistent configuration, volatile memory), identify where the mapping fails (stochastic generation, configuration that binds only probabilistically, no general-purpose retirement (verification) stage by default), and derive from the failures a seven-principle operating discipline with an error loop at its core. Three cases from my own practice illustrate the mechanism, among them a control that silently became the exact harm it was built to prevent. I close with the measurement framework this view implies and the lab study required to test it.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。