怎么把安全要求写进采购条款How to Write Safety Requirements into a Procurement Contract

文档交付写具体：要求提供模型卡或系统卡、使用说明，写明版本号与发布日期；「详见官网」不算交付。

变更通知写条件与提前量：模型替换、数据保留策略调整、子处理方变更，分别写明在哪个节点、以什么方式通知你。

数据条款写流向：日志保留多久、是否用于训练、能否限定处理区域、导出与删除的时限与格式。

事件义务写清能拿到什么：安全事件的通报义务、你能导出哪些日志作为证据、责任与整改怎么归属。

退出写条件：数据与配置的导出格式、合同终止后的删除证明、历史记录的处置方式；没有退出条款的接入会把依赖写进架构。

法规相关文本交给法务定稿：AI Act 的分阶段义务、国内办法与标识义务如何落到你的业务，条款里只写「谁承担哪部分义务、由谁出证明」。

举个例子（虚构条款）：输入是对方的合同草案，只写了「提供高质量模型」→ 处理是逐条替换成四个交付点（版本化文档、约定提前量的变更通知、日志不用于训练且可导出、删除证明与时限）→ 结果判断是当场提问「出事时我能拿到哪些日志证明输入与输出」，答不出来就记为条款缺口 → 下一步是把缺口列成待议清单走法务与供应商对齐，不用口头承诺补上。

Make document delivery concrete: require model cards or system cards and usage documentation, with version numbers and publication dates. "See our website" is not a deliverable.

State change-notice conditions and lead time: model replacement, data-retention changes, subprocessor changes each get a point in the process and a notification method.

Write data flow into the clause: log retention period, whether data trains models, whether processing can stay in a chosen region, and the deadline and format for export and deletion.

Define incident obligations by what evidence you can obtain: notification duties, which logs you can export as evidence, how responsibility and remediation are assigned.

Give exit real teeth: export formats for data and configuration, proof of deletion after termination, disposition of historical records. A connection without exit terms writes the dependency into your architecture.

Hand regulatory wording to legal: how the AI Act's staged duties and China's Measures and labeling rules land on your business is their call; the clause only states who bears which duty and who produces the proof.

Worked example (fictional clause): input is a draft contract that only promises "a high-quality model" -> processing replaces it clause by clause with the four levers (versioned documents, change notice with agreed lead time, logs not used for training and exportable, deletion proof with deadlines) -> the check asks on the spot "which logs can I obtain to prove inputs and outputs after an incident"; no answer means a clause gap -> next step: turn the gaps into a list for legal and the vendor to work through, rather than accepting a verbal promise.