Compare commits
1 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| a4fafd94b3 |
@@ -0,0 +1,389 @@
|
||||
# AI 法务平台内容智力升级执行方案 v2
|
||||
|
||||
## 1. 本版直接拍板结果
|
||||
|
||||
本方案不再等待老板逐项确认,按当前平台目标与商业价值直接定案。
|
||||
|
||||
### 1.1 战略定位
|
||||
平台内容升级主线定位为:
|
||||
- 先做“企业商事合同法务大脑”
|
||||
- 再向全行业、全法律门类扩展
|
||||
- 先把审查与生成做深,再把覆盖面做宽
|
||||
|
||||
### 1.2 首批优先行业
|
||||
按商业价值、复用率、平台差异化与资料可获得性排序:
|
||||
1. SaaS/软件服务
|
||||
2. AI/数据服务
|
||||
3. 电商/代运营
|
||||
4. 人力资源/劳务外包
|
||||
5. 建工/装修
|
||||
|
||||
### 1.3 首批优先模板
|
||||
第一批模板直接确定为:
|
||||
1. 保密协议(NDA)
|
||||
2. 服务合同
|
||||
3. 技术服务合同
|
||||
4. 技术开发合同
|
||||
5. 软件开发合同
|
||||
6. SaaS 服务协议
|
||||
7. 数据处理委托协议
|
||||
8. 采购框架协议
|
||||
9. 销售框架协议
|
||||
10. 劳动合同
|
||||
11. 劳务合同
|
||||
12. 顾问/兼职顾问协议
|
||||
|
||||
### 1.4 首批优先内容方向
|
||||
直接锁定为:
|
||||
- 企业商事合同法务
|
||||
- 合同审查
|
||||
- 合同生成
|
||||
- 条款替换与风险修订
|
||||
- 数据合规与知识产权合规
|
||||
|
||||
### 1.5 建设顺序
|
||||
必须按以下顺序推进:
|
||||
1. 法律法规与司法解释
|
||||
2. 审查规则库
|
||||
3. 条款库
|
||||
4. 模板库
|
||||
5. FAQ 问答库
|
||||
6. 行业知识包
|
||||
7. 训练与反馈闭环
|
||||
|
||||
### 1.6 内容边界拍板
|
||||
直接采用以下边界:
|
||||
- 官方公开模板:只作为参考来源,平台统一改写为平台版
|
||||
- 裁判文书:不做全文库,只做规则摘要、争议焦点、裁判要旨与原文回链
|
||||
- 行业资料/标准/协会材料:不做全文库,只做摘要、索引、引用
|
||||
- 客户私有合同/资料:默认不进入公共训练或公共内容;仅在单独授权且脱敏后进入私有训练资产
|
||||
|
||||
### 1.7 商业化优先级拍板
|
||||
先做内部能力底座,再做对外可卖内容包:
|
||||
- 第一阶段目标:让平台真的更懂法务
|
||||
- 第二阶段目标:把成熟内容打包成行业化可销售资产
|
||||
|
||||
## 2. 当前平台的真实问题定义
|
||||
|
||||
当前问题不是功能按钮不够,而是内容智力不足,具体表现为:
|
||||
- 法规与司法解释没有形成结构化底座
|
||||
- 模板库数量和质量都不够
|
||||
- 条款库几乎空白
|
||||
- 审查规则库没有真正成体系
|
||||
- FAQ 与行业知识不足
|
||||
- 训练框架已具备,但缺少高质量内容输入
|
||||
|
||||
因此本阶段不再以“新增功能模块”为主,而以“内容中台与法务知识资产建设”为主。
|
||||
|
||||
## 3. 第一阶段总体目标
|
||||
|
||||
用 90 天把平台从“幼儿园智力”提升到“可商用高级法务助理智力”,形成以下闭环:
|
||||
|
||||
法源依据 -> 审查规则 -> 条款建议 -> 模板生成 -> FAQ 解释 -> 行业增强
|
||||
|
||||
第一阶段成功标准:
|
||||
1. 平台对高频企业合同具备可引用的法律依据
|
||||
2. 平台对高频风险点具备稳定审查规则
|
||||
3. 平台能给出替代条款与修改建议
|
||||
4. 平台能基于结构化模板生成可用合同初稿
|
||||
5. 平台能对 SaaS/AI/电商三类行业给出更专业输出
|
||||
|
||||
## 4. 首批建设内容总表
|
||||
|
||||
### 4.1 法律法规与司法解释底座
|
||||
首批 24 个主题源:
|
||||
1. 民法典合同编核心条文
|
||||
2. 民法典总则编与民事法律行为相关条文
|
||||
3. 公司法
|
||||
4. 劳动合同法
|
||||
5. 劳动法
|
||||
6. 社会保险法用工相关条文
|
||||
7. 仲裁法
|
||||
8. 民事诉讼法合同争议相关条文
|
||||
9. 电子签名法
|
||||
10. 消费者权益保护法
|
||||
11. 反不正当竞争法
|
||||
12. 著作权法
|
||||
13. 商标法
|
||||
14. 专利法
|
||||
15. 网络安全法
|
||||
16. 数据安全法
|
||||
17. 个人信息保护法
|
||||
18. 招标投标法
|
||||
19. 建筑法
|
||||
20. 最高法合同效力相关司法解释
|
||||
21. 最高法担保相关司法解释
|
||||
22. 最高法违约责任相关司法解释
|
||||
23. 最高法买卖合同相关司法解释
|
||||
24. 最高法劳动争议相关司法解释
|
||||
|
||||
### 4.2 首批审查规则库
|
||||
先建设 36 条高频规则:
|
||||
1. 主体资格审查
|
||||
2. 签约权限审查
|
||||
3. 合同名称与交易实质不一致
|
||||
4. 标的不明确
|
||||
5. 服务范围不明确
|
||||
6. 交付成果定义不清
|
||||
7. 验收标准缺失
|
||||
8. 验收流程缺失
|
||||
9. 付款节点不清
|
||||
10. 发票义务不清
|
||||
11. 自动续约风险
|
||||
12. 单方变更权过强
|
||||
13. 单方免责/责任失衡
|
||||
14. 违约责任过轻
|
||||
15. 违约责任过重
|
||||
16. 赔偿上限缺失
|
||||
17. 赔偿上限明显不利
|
||||
18. 保密范围过宽
|
||||
19. 保密范围过窄
|
||||
20. 知识产权归属不清
|
||||
21. 知识产权侵权担保缺失
|
||||
22. 数据处理角色不清
|
||||
23. 个人信息处理合法性不足
|
||||
24. 数据出境/第三方共享缺失
|
||||
25. 网络与系统安全义务缺失
|
||||
26. 解约条件失衡
|
||||
27. 终止后义务缺失
|
||||
28. 不可抗力约定失衡
|
||||
29. 通知送达机制不明
|
||||
30. 争议解决约定不利
|
||||
31. 法律适用与管辖冲突
|
||||
32. 附件与主合同冲突
|
||||
33. 印章/签字页完整性缺失
|
||||
34. 生效条件不明
|
||||
35. 行业许可/资质前置条件缺失
|
||||
36. 外包/转委托限制不清
|
||||
|
||||
### 4.3 首批条款库
|
||||
首批做 48 个条款单元,每个条款单元至少包含:
|
||||
- 中性版
|
||||
- 甲方有利版
|
||||
- 乙方有利版
|
||||
- 风险说明
|
||||
- 适用场景
|
||||
- 关联法源
|
||||
- 关联审查规则
|
||||
|
||||
优先条款类别:
|
||||
1. 定义
|
||||
2. 标的
|
||||
3. 服务范围
|
||||
4. 交付成果
|
||||
5. 项目周期
|
||||
6. 验收
|
||||
7. 价款
|
||||
8. 付款节点
|
||||
9. 发票
|
||||
10. 保密
|
||||
11. 知识产权归属
|
||||
12. 知识产权侵权担保
|
||||
13. 数据处理
|
||||
14. 个人信息保护
|
||||
15. 网络安全与系统义务
|
||||
16. 人员管理与驻场
|
||||
17. 分包/转委托
|
||||
18. 陈述与保证
|
||||
19. 违约责任
|
||||
20. 赔偿责任限制
|
||||
21. 免责条款
|
||||
22. 不可抗力
|
||||
23. 变更管理
|
||||
24. 自动续约
|
||||
25. 终止/解除
|
||||
26. 终止后协助
|
||||
27. 审计权/检查权
|
||||
28. 竞业限制/不招揽
|
||||
29. 合规承诺
|
||||
30. 反商业贿赂
|
||||
31. 争议解决
|
||||
32. 法律适用
|
||||
33. 通知送达
|
||||
34. 附件优先级
|
||||
35. 生效条款
|
||||
36. 完整协议条款
|
||||
37. 可分割性条款
|
||||
38. 权利保留条款
|
||||
39. 税费承担
|
||||
40. 售后与支持
|
||||
41. 服务等级/响应时间
|
||||
42. 数据留存与删除
|
||||
43. 开源软件与第三方素材责任
|
||||
44. 算法/模型输出免责声明
|
||||
45. 数据来源合法性承诺
|
||||
46. 培训与交接
|
||||
47. 客户配合义务
|
||||
48. 证据留存与日志协助
|
||||
|
||||
### 4.4 首批模板库
|
||||
第一阶段模板定为 12 个:
|
||||
1. NDA
|
||||
2. 通用服务合同
|
||||
3. 技术服务合同
|
||||
4. 技术开发合同
|
||||
5. 软件开发合同
|
||||
6. SaaS 服务协议
|
||||
7. 数据处理委托协议
|
||||
8. 采购框架协议
|
||||
9. 销售框架协议
|
||||
10. 劳动合同
|
||||
11. 劳务合同
|
||||
12. 顾问协议
|
||||
|
||||
### 4.5 首批 FAQ
|
||||
第一阶段 FAQ 定为 60 条,分 8 组:
|
||||
- 付款与发票
|
||||
- 验收与交付
|
||||
- 自动续约与终止
|
||||
- 违约金与赔偿责任
|
||||
- 保密与知识产权
|
||||
- 数据合规与个人信息
|
||||
- 劳动/劳务用工
|
||||
- SaaS/软件/AI 数据服务
|
||||
|
||||
### 4.6 首批行业包
|
||||
第一阶段只要求 3 个行业包上线:
|
||||
1. SaaS/软件行业法务包
|
||||
2. AI/数据服务行业法务包
|
||||
3. 电商/代运营行业法务包
|
||||
|
||||
## 5. 来源策略
|
||||
|
||||
### 5.1 一级权威来源
|
||||
1. 国家法律法规数据库
|
||||
2. 中国政府网
|
||||
3. 最高人民法院官网
|
||||
4. 人民法院案例库
|
||||
5. 最高人民检察院官网
|
||||
|
||||
### 5.2 二级监管来源
|
||||
1. 国家网信办
|
||||
2. 市场监管总局
|
||||
3. 司法部
|
||||
4. 人力资源和社会保障相关公开来源
|
||||
5. 国家税务总局
|
||||
6. 国家金融监督管理总局
|
||||
7. 中国证监会
|
||||
8. 国家知识产权局
|
||||
|
||||
### 5.3 三级参考来源
|
||||
1. 仲裁机构公开规则与示范条款
|
||||
2. 贸促会公开示范材料
|
||||
3. 主管机关办事指南与公开模板
|
||||
4. 行业主管机关公开合规指引
|
||||
|
||||
### 5.4 来源使用策略
|
||||
- 法规/司法解释:结构化入库
|
||||
- 指导案例/典型案例:摘要化入库
|
||||
- 裁判文书:规则提炼与回链
|
||||
- 官方模板:只做参考,不直接原样作为平台模板
|
||||
- 行业资料:只做摘要与规则提炼
|
||||
|
||||
## 6. 30/60/90 天执行路径
|
||||
|
||||
### 6.1 前 30 天
|
||||
目标:跑通底座
|
||||
|
||||
交付:
|
||||
1. 来源注册表 v2
|
||||
2. 首批执行资产清单
|
||||
3. 法规与司法解释主题清单
|
||||
4. 36 条审查规则清单
|
||||
5. 48 个条款单元清单
|
||||
6. 12 个模板清单
|
||||
7. 60 条 FAQ 选题清单
|
||||
8. 3 个行业包大纲
|
||||
|
||||
### 6.2 第 31-60 天
|
||||
目标:跑通结构化内容生产
|
||||
|
||||
交付:
|
||||
1. 法规底座首批包
|
||||
2. 审查规则包 v1
|
||||
3. 通用条款库 v1
|
||||
4. 通用模板库 v1
|
||||
5. FAQ 包 v1
|
||||
6. SaaS/AI/电商行业包初版
|
||||
|
||||
### 6.3 第 61-90 天
|
||||
目标:接入训练、审查、生成闭环
|
||||
|
||||
交付:
|
||||
1. 规则与条款映射
|
||||
2. 模板与变量映射
|
||||
3. FAQ 与法源映射
|
||||
4. 行业包增强映射
|
||||
5. 训练样本生成规则
|
||||
6. 平台内容升级验收报告
|
||||
|
||||
## 7. 内容生产工作流
|
||||
|
||||
统一采用以下内容流水线:
|
||||
1. 选题立项
|
||||
2. 来源搜集
|
||||
3. 原文归档
|
||||
4. 结构化清洗
|
||||
5. 法务编辑改写
|
||||
6. 审校复核
|
||||
7. 结构化入库
|
||||
8. 训练化映射
|
||||
9. 上线验收
|
||||
10. 更新巡检
|
||||
|
||||
每类资产的工作要求:
|
||||
- 法规:必须保留权威来源、发布日期、施行状态
|
||||
- 规则:必须有法律依据、触发条件、建议修法
|
||||
- 条款:必须有适用场景、风险解释、版本差异
|
||||
- 模板:必须绑定变量、必选条款、可选条款、审查规则
|
||||
- FAQ:必须反链规则或法源
|
||||
- 行业包:必须同时包含法源、规则、条款、模板、FAQ
|
||||
|
||||
## 8. 验收标准
|
||||
|
||||
本阶段不以“录了多少份文件”为主要成功指标,而以“是否形成智力闭环”为标准。
|
||||
|
||||
### 8.1 法源层验收
|
||||
- 能回答结论背后的法律依据
|
||||
- 能识别现行有效与失效状态
|
||||
- 能定位关联审查主题
|
||||
|
||||
### 8.2 规则层验收
|
||||
- 能稳定识别高频合同风险
|
||||
- 能给出理由、风险等级、修订建议
|
||||
|
||||
### 8.3 条款层验收
|
||||
- 能输出可直接替换的条款文本
|
||||
- 能体现甲乙方立场差异
|
||||
|
||||
### 8.4 模板层验收
|
||||
- 能在主要场景生成可用合同初稿
|
||||
- 能按行业加载增强条款
|
||||
|
||||
### 8.5 FAQ 层验收
|
||||
- 能给出有依据、非空泛的解释型回答
|
||||
|
||||
## 9. 当前执行决策总结
|
||||
|
||||
最终拍板如下:
|
||||
- 聚焦企业商事合同法务
|
||||
- 首批行业先做 SaaS、AI 数据、电商
|
||||
- 首批模板先做 12 个高频模板
|
||||
- 官方模板统一改写为平台模板
|
||||
- 裁判文书不做全文库,只做摘要和规则提炼
|
||||
- 行业资料不做全文库,只做索引、摘要、引用
|
||||
- 客户私有资料默认不进入公共训练
|
||||
- 先做内部能力底座,再做商业化内容包
|
||||
|
||||
## 10. 下一步落地动作
|
||||
|
||||
下一步直接进入以下三类产物建设:
|
||||
1. 扩展来源注册表
|
||||
2. 固化首批执行资产清单
|
||||
3. 按包结构逐步生产首批法规、规则、条款、模板、FAQ、行业包
|
||||
|
||||
## 11. 2026-05-04 草案补齐
|
||||
|
||||
- 已补齐 `review_rules_cn_contract_v1.json` 当前全部 fallback 所需的 13 个通用条款。
|
||||
- 已补建 3 个首批行业包草案文件:`industry_pack_cn_saas_software_v1.json`、`industry_pack_cn_ai_data_services_v1.json`、`industry_pack_cn_ecommerce_operations_v1.json`。
|
||||
- 当前剩余缺口主要集中在电商专属模板、行业化 FAQ、AI 训练/跨境数据等专用附件,以及更细分的垂直规则扩展。
|
||||
@@ -0,0 +1,561 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "legal_content_first_execution_assets_v1",
|
||||
"domain": "sources",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Draft execution backlog for the first 90 days of China legal-content production, organized by deliverable type, priority, and downstream package target."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"group": "regulations_and_rules",
|
||||
"count": 19,
|
||||
"assets": [
|
||||
{
|
||||
"asset_id": "reg_cn_civil_code_contract_core",
|
||||
"name": "民法典合同编核心条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "结构化法条卡 + 生效状态 + 引用锚点",
|
||||
"primary_use": "通用合同审查与模板生成底座"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_company_law_core",
|
||||
"name": "公司法核心条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "治理、出资、股权转让相关法条卡",
|
||||
"primary_use": "股权转让、投融资、主体资格审查"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_labor_contract_law",
|
||||
"name": "劳动合同法核心条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_mhrss", "src_cn_local_hrss"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "订立、履行、解除、赔偿条文卡",
|
||||
"primary_use": "劳动合同、解除、竞业限制与用工FAQ"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_labor_law_social_insurance",
|
||||
"name": "劳动法与社会保险法用工关键条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P1",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_mhrss", "src_cn_local_hrss"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "工时、工资、社保义务结构化摘要",
|
||||
"primary_use": "HR行业包和劳动FAQ支持"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_e_signature_law",
|
||||
"name": "电子签名法核心条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "电子签约效力与例外规则卡",
|
||||
"primary_use": "在线签约流程与证据链说明"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_arbitration_cpl_contract",
|
||||
"name": "仲裁法与民事诉讼法合同争议关键条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P1",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_spc"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "争议解决与保全执行条文卡",
|
||||
"primary_use": "争议解决条款和诉仲衔接FAQ"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_data_security_triplet",
|
||||
"name": "网络安全法+数据安全法+个人信息保护法核心条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_cac", "src_cn_miit", "src_cn_mps"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "数据分类、个人信息处理、委托处理条文卡",
|
||||
"primary_use": "SaaS、AI/数据服务、数据处理协议"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_consumer_advertising_competition",
|
||||
"name": "消费者权益保护法+广告监管+反不正当竞争规则包",
|
||||
"asset_type": "law",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_samr", "src_cn_local_market_regulators"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "营销、宣传、平台经营风险规则卡",
|
||||
"primary_use": "电商/代运营/广告投放行业包"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_copyright_trademark_patent",
|
||||
"name": "著作权法+商标法+专利法核心条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_cnipa"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "知识产权归属、许可、侵权责任条文卡",
|
||||
"primary_use": "软件开发、品牌推广、IP授权模板"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_bidding_construction",
|
||||
"name": "招标投标法与建筑法关键条文包",
|
||||
"asset_type": "law",
|
||||
"priority": "P2",
|
||||
"target_window": "D46-D60",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_gov_state_council"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "招采、分包、工期责任条文卡",
|
||||
"primary_use": "建工/装修行业包"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_spc_contract_validity_interp",
|
||||
"name": "最高法合同效力相关司法解释包",
|
||||
"asset_type": "judicial_interpretation",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_spc"],
|
||||
"downstream_package": "judicial_interpretations_cn_contract_v1.json",
|
||||
"deliverable": "效力、撤销、格式条款、证据规则摘要",
|
||||
"primary_use": "合同效力审查与风险提示"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_spc_guarantee_default_interp",
|
||||
"name": "最高法担保与违约责任相关司法解释包",
|
||||
"asset_type": "judicial_interpretation",
|
||||
"priority": "P1",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_spc"],
|
||||
"downstream_package": "judicial_interpretations_cn_contract_v1.json",
|
||||
"deliverable": "保证、担保、违约损失裁判规则卡",
|
||||
"primary_use": "借款合同、保证合同、违约责任条款"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_cac_data_export_and_algorithm",
|
||||
"name": "网信办数据出境/算法/个人信息配套规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_cac"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "配套办法、评估要求、合同触发点摘要",
|
||||
"primary_use": "AI/数据服务行业包与DPA模板"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_miit_telecom_software_rules",
|
||||
"name": "工信部电信与软件服务规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_miit"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "电信业务、App合规、软件服务注意事项摘要",
|
||||
"primary_use": "SaaS服务协议、平台服务条款"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_samr_standard_terms_rules",
|
||||
"name": "市场监管合同格式条款与促销规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_samr", "src_cn_local_market_regulators"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "格式条款、公平交易、促销宣传风险规则摘要",
|
||||
"primary_use": "通用买卖、平台、广告、电商场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_mhrss_local_termination_rules",
|
||||
"name": "人社部+重点城市解除/裁员/竞业配套规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P1",
|
||||
"target_window": "D46-D60",
|
||||
"source_registry_ids": ["src_cn_mhrss", "src_cn_local_hrss"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "北京/上海/深圳等本地执行口径摘编",
|
||||
"primary_use": "劳动合同、离职协议、竞业FAQ"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_finance_payment_rules",
|
||||
"name": "人民银行/金融监管总局支付与金融外包规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P2",
|
||||
"target_window": "D61-D75",
|
||||
"source_registry_ids": ["src_cn_pbc", "src_cn_nfra"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "支付、清算、外包、消费者金融义务摘要",
|
||||
"primary_use": "支付服务与金融合作模板"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_foreign_trade_investment_rules",
|
||||
"name": "商务部外贸外资合规规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P2",
|
||||
"target_window": "D61-D75",
|
||||
"source_registry_ids": ["src_cn_mofcom"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "跨境交易、外包、合作准入提示卡",
|
||||
"primary_use": "跨境服务、渠道合作、投资意向书"
|
||||
},
|
||||
{
|
||||
"asset_id": "reg_cn_healthcare_advertising_rules",
|
||||
"name": "药监局医疗/药品宣传与交易规则包",
|
||||
"asset_type": "regulatory_rule",
|
||||
"priority": "P3",
|
||||
"target_window": "D76-D90",
|
||||
"source_registry_ids": ["src_cn_nmpa", "src_cn_samr"],
|
||||
"downstream_package": "laws_cn_core_v1.json",
|
||||
"deliverable": "医疗广告、药械推广限制摘要",
|
||||
"primary_use": "医疗健康客户专项补充"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"group": "clauses_and_templates",
|
||||
"count": 17,
|
||||
"assets": [
|
||||
{
|
||||
"asset_id": "tpl_cn_general_sales_purchase",
|
||||
"name": "通用买卖合同模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_standard_contract_examples", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "标准模板 + 可选风险位说明",
|
||||
"primary_use": "高频交易场景起步模板"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_procurement_framework",
|
||||
"name": "采购框架协议模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_standard_contract_examples", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "框架+订单联动结构模板",
|
||||
"primary_use": "采购与供应链统一底稿"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_service_agreement",
|
||||
"name": "服务合同模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_standard_contract_examples", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "通用服务合同模板",
|
||||
"primary_use": "服务采购与输出基础模板"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_saas_service_agreement",
|
||||
"name": "SaaS服务协议模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_miit", "src_cn_cac", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_saas_v1.json",
|
||||
"deliverable": "主协议 + 数据处理附件位",
|
||||
"primary_use": "SaaS行业包与软件交付场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_software_development",
|
||||
"name": "软件开发合同模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_cnipa", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_saas_v1.json",
|
||||
"deliverable": "开发、验收、知识产权分配完整模板",
|
||||
"primary_use": "定制开发项目"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_data_processing_agreement",
|
||||
"name": "数据处理委托协议模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_cac", "src_cn_npc_lawdb", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_saas_v1.json",
|
||||
"deliverable": "DPA模板 + 安全措施条款位",
|
||||
"primary_use": "个人信息和数据委托处理"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_nda",
|
||||
"name": "保密协议NDA模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "单向/双向保密模板",
|
||||
"primary_use": "项目前置签约与尽调"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_employment_contract",
|
||||
"name": "劳动合同模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_standard_contract_examples", "src_cn_local_hrss", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "通用劳动合同 + 地方必备项提示",
|
||||
"primary_use": "人力资源行业包"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_consultant_and_labor_service",
|
||||
"name": "劳务/兼职顾问协议模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_mhrss", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "劳务关系边界版模板",
|
||||
"primary_use": "外部顾问与灵活用工"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_channel_cooperation",
|
||||
"name": "渠道合作协议模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_mofcom", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "渠道授权、结算、区域保护模板",
|
||||
"primary_use": "销售渠道与分销场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_advertising_and_mcn",
|
||||
"name": "广告投放/MCN达人合作模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_samr", "src_cn_local_market_regulators", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "广告合规位+内容审核位模板",
|
||||
"primary_use": "广告、电商、直播推广"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_ecommerce_operation",
|
||||
"name": "电商代运营协议模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_samr", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "店铺运营、内容投放、数据归属模板",
|
||||
"primary_use": "电商/代运营行业包"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_commercial_lease",
|
||||
"name": "商用房屋租赁合同模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P1",
|
||||
"target_window": "D46-D60",
|
||||
"source_registry_ids": ["src_cn_standard_contract_examples", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "租金、物业、装修责任模板",
|
||||
"primary_use": "办公场地租赁场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_loan_and_guarantee",
|
||||
"name": "借款合同与保证合同模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P1",
|
||||
"target_window": "D46-D60",
|
||||
"source_registry_ids": ["src_cn_spc", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "借款+保证组合模板",
|
||||
"primary_use": "融资、关联借款、履约保障"
|
||||
},
|
||||
{
|
||||
"asset_id": "tpl_cn_equity_transfer_and_loi",
|
||||
"name": "股权转让协议与投资意向书模板",
|
||||
"asset_type": "template",
|
||||
"priority": "P2",
|
||||
"target_window": "D61-D75",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_csrc", "src_internal_authored"],
|
||||
"downstream_package": "contract_templates_cn_official_v1.json",
|
||||
"deliverable": "股权交易主协议+LOI基础版",
|
||||
"primary_use": "融资并购和治理场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "clause_cn_general_library",
|
||||
"name": "通用条款库首版",
|
||||
"asset_type": "clause_library",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_internal_authored", "src_cn_standard_contract_examples"],
|
||||
"downstream_package": "clause_library_cn_general_v1.json",
|
||||
"deliverable": "20个核心条款标准版+偏买方/偏卖方变体",
|
||||
"primary_use": "模板拼装与审查建议生成"
|
||||
},
|
||||
{
|
||||
"asset_id": "clause_cn_data_ip_employment_variants",
|
||||
"name": "数据/IP/劳动敏感条款变体包",
|
||||
"asset_type": "clause_library",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_internal_authored", "src_cn_cac", "src_cn_cnipa", "src_cn_local_hrss"],
|
||||
"downstream_package": "clause_library_cn_general_v1.json",
|
||||
"deliverable": "高风险条款替代文本与适用说明",
|
||||
"primary_use": "高风险合同定制与建议替换"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"group": "rules_faq_and_industry_packs",
|
||||
"count": 12,
|
||||
"assets": [
|
||||
{
|
||||
"asset_id": "rule_cn_contract_review_core20",
|
||||
"name": "合同审查20条核心规则包",
|
||||
"asset_type": "review_rule",
|
||||
"priority": "P0",
|
||||
"target_window": "D1-D15",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_spc", "src_internal_authored"],
|
||||
"downstream_package": "review_rules_cn_contract_v1.json",
|
||||
"deliverable": "规则条件+风险等级+建议动作",
|
||||
"primary_use": "通用合同审查引擎首发"
|
||||
},
|
||||
{
|
||||
"asset_id": "rule_cn_data_and_privacy_review",
|
||||
"name": "数据合规与个人信息审查规则包",
|
||||
"asset_type": "review_rule",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_cn_cac", "src_cn_npc_lawdb", "src_internal_authored"],
|
||||
"downstream_package": "review_rules_cn_contract_v1.json",
|
||||
"deliverable": "收集、委托、出境、留存风险规则",
|
||||
"primary_use": "AI/数据、SaaS、委托处理合同"
|
||||
},
|
||||
{
|
||||
"asset_id": "rule_cn_employment_review",
|
||||
"name": "劳动用工审查规则包",
|
||||
"asset_type": "review_rule",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_mhrss", "src_cn_local_hrss", "src_internal_authored"],
|
||||
"downstream_package": "review_rules_cn_contract_v1.json",
|
||||
"deliverable": "入职、离职、竞业、赔偿规则集",
|
||||
"primary_use": "劳动合同与HR问答"
|
||||
},
|
||||
{
|
||||
"asset_id": "rule_cn_marketing_ecommerce_review",
|
||||
"name": "广告营销与电商代运营审查规则包",
|
||||
"asset_type": "review_rule",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_samr", "src_cn_local_market_regulators", "src_internal_authored"],
|
||||
"downstream_package": "review_rules_cn_contract_v1.json",
|
||||
"deliverable": "宣传、促销、平台责任规则集",
|
||||
"primary_use": "广告投放、直播、代运营场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "faq_cn_contract_review_top10",
|
||||
"name": "合同审查高频FAQ首版",
|
||||
"asset_type": "faq",
|
||||
"priority": "P0",
|
||||
"target_window": "D16-D30",
|
||||
"source_registry_ids": ["src_internal_authored", "src_cn_public_casebooks"],
|
||||
"downstream_package": "faq_cn_contract_review_v1.json",
|
||||
"deliverable": "10-20问结构化FAQ",
|
||||
"primary_use": "产品首批问答能力"
|
||||
},
|
||||
{
|
||||
"asset_id": "faq_cn_saas_and_data",
|
||||
"name": "SaaS/软件开发/数据合规FAQ",
|
||||
"asset_type": "faq",
|
||||
"priority": "P1",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_cac", "src_cn_miit", "src_internal_authored"],
|
||||
"downstream_package": "faq_cn_contract_review_v1.json",
|
||||
"deliverable": "系统交付、验收、数据责任FAQ",
|
||||
"primary_use": "SaaS行业包和销售支持"
|
||||
},
|
||||
{
|
||||
"asset_id": "faq_cn_labor_and_termination",
|
||||
"name": "劳动用工与解除争议FAQ",
|
||||
"asset_type": "faq",
|
||||
"priority": "P1",
|
||||
"target_window": "D46-D60",
|
||||
"source_registry_ids": ["src_cn_local_hrss", "src_cn_local_high_courts", "src_internal_authored"],
|
||||
"downstream_package": "faq_cn_contract_review_v1.json",
|
||||
"deliverable": "解除、赔偿、竞业限制FAQ",
|
||||
"primary_use": "HR包与劳动争议解答"
|
||||
},
|
||||
{
|
||||
"asset_id": "pack_cn_saas_software",
|
||||
"name": "SaaS/软件行业法务包",
|
||||
"asset_type": "industry_pack",
|
||||
"priority": "P0",
|
||||
"target_window": "D31-D45",
|
||||
"source_registry_ids": ["src_cn_miit", "src_cn_cac", "src_internal_authored"],
|
||||
"downstream_package": "industry_saas_software_cn_v1.json",
|
||||
"deliverable": "法规摘要+模板+条款+规则+FAQ组合包",
|
||||
"primary_use": "首个可销售/可演示行业包"
|
||||
},
|
||||
{
|
||||
"asset_id": "pack_cn_ai_data_services",
|
||||
"name": "AI/数据服务行业法务包",
|
||||
"asset_type": "industry_pack",
|
||||
"priority": "P0",
|
||||
"target_window": "D46-D60",
|
||||
"source_registry_ids": ["src_cn_cac", "src_cn_npc_lawdb", "src_internal_authored"],
|
||||
"downstream_package": "industry_ai_data_services_cn_v1.json",
|
||||
"deliverable": "数据治理重点清单+协议组合包",
|
||||
"primary_use": "AI场景试点客户"
|
||||
},
|
||||
{
|
||||
"asset_id": "pack_cn_ecommerce_operations",
|
||||
"name": "电商/代运营行业法务包",
|
||||
"asset_type": "industry_pack",
|
||||
"priority": "P1",
|
||||
"target_window": "D61-D75",
|
||||
"source_registry_ids": ["src_cn_samr", "src_cn_local_market_regulators", "src_internal_authored"],
|
||||
"downstream_package": "industry_ecommerce_operations_cn_v1.json",
|
||||
"deliverable": "营销合规+代运营模板+争议FAQ组合包",
|
||||
"primary_use": "电商客户和直播推广场景"
|
||||
},
|
||||
{
|
||||
"asset_id": "pack_cn_hr_outsourcing",
|
||||
"name": "人力资源/劳务外包行业法务包",
|
||||
"asset_type": "industry_pack",
|
||||
"priority": "P1",
|
||||
"target_window": "D61-D75",
|
||||
"source_registry_ids": ["src_cn_mhrss", "src_cn_local_hrss", "src_internal_authored"],
|
||||
"downstream_package": "industry_hr_outsourcing_cn_v1.json",
|
||||
"deliverable": "劳动模板+规则+FAQ组合包",
|
||||
"primary_use": "HR服务与灵活用工客户"
|
||||
},
|
||||
{
|
||||
"asset_id": "pack_cn_construction_fitout",
|
||||
"name": "建工/装修行业法务包",
|
||||
"asset_type": "industry_pack",
|
||||
"priority": "P2",
|
||||
"target_window": "D76-D90",
|
||||
"source_registry_ids": ["src_cn_npc_lawdb", "src_cn_gov_state_council", "src_internal_authored"],
|
||||
"downstream_package": "industry_construction_fitout_cn_v1.json",
|
||||
"deliverable": "招采、工期、验收、结算组合包",
|
||||
"primary_use": "建工客户专项演示"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,91 @@
|
||||
{
|
||||
"version": 2,
|
||||
"metadata": {
|
||||
"package_name": "legal_content_release_index_v2",
|
||||
"domain": "sources",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v2",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Release index v2 for the legal content workspace. Priorities rebased toward review-ready SaaS/data/commercial contract assets with explicit phase gating.",
|
||||
"release_strategy": "ship seed-first packages that can support contract review, guided drafting, and FAQ retrieval before broad law corpus expansion"
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"package_name": "review_rules_cn_contract_v1.json",
|
||||
"domain": "rules",
|
||||
"status": "seed_ready",
|
||||
"priority": 1,
|
||||
"phase": "phase_1_review_core",
|
||||
"rationale": "Highest leverage for immediate contract review quality and can power issue spotting before full law ingestion.",
|
||||
"depends_on": ["source_registry_v1.json"],
|
||||
"recommended_seed": "seeds/rules/review_rules_cn_saas_high_risk_seed_v1.json"
|
||||
},
|
||||
{
|
||||
"package_name": "contract_templates_cn_saas_v1.json",
|
||||
"domain": "templates",
|
||||
"status": "seed_ready",
|
||||
"priority": 2,
|
||||
"phase": "phase_1_review_core",
|
||||
"rationale": "SaaS and software delivery templates are commercially frequent and pair directly with review rules and variable-driven drafting.",
|
||||
"depends_on": ["source_registry_v1.json", "review_rules_cn_contract_v1.json"],
|
||||
"recommended_seed": "seeds/templates/contract_templates_cn_saas_msa_seed_v1.json"
|
||||
},
|
||||
{
|
||||
"package_name": "faq_cn_data_compliance_v1.json",
|
||||
"domain": "faq",
|
||||
"status": "seed_ready",
|
||||
"priority": 3,
|
||||
"phase": "phase_1_review_core",
|
||||
"rationale": "Data processing, cross-border flow, and vendor allocation questions recur in SaaS and AI deals and are valuable for support and self-serve triage.",
|
||||
"depends_on": ["source_registry_v1.json", "review_rules_cn_contract_v1.json"],
|
||||
"recommended_seed": "seeds/faq/faq_cn_data_compliance_seed_v1.json"
|
||||
},
|
||||
{
|
||||
"package_name": "laws_cn_core_v1.json",
|
||||
"domain": "laws",
|
||||
"status": "outline_ready",
|
||||
"priority": 4,
|
||||
"phase": "phase_2_authority_backbone",
|
||||
"rationale": "Core authority set remains essential, but broad law ingestion is less immediately actionable than rules/templates/faq for the next release.",
|
||||
"depends_on": ["source_registry_v1.json", "first_100_assets_v1.json"]
|
||||
},
|
||||
{
|
||||
"package_name": "judicial_interpretations_cn_contract_v1.json",
|
||||
"domain": "laws",
|
||||
"status": "outline_ready",
|
||||
"priority": 5,
|
||||
"phase": "phase_2_authority_backbone",
|
||||
"rationale": "Needed to strengthen legal basis explanations and conflict resolution for review outputs after phase 1 seeds are stabilized.",
|
||||
"depends_on": ["source_registry_v1.json", "laws_cn_core_v1.json"]
|
||||
},
|
||||
{
|
||||
"package_name": "clause_library_cn_general_v1.json",
|
||||
"domain": "clauses",
|
||||
"status": "planned",
|
||||
"priority": 6,
|
||||
"phase": "phase_3_clause_system",
|
||||
"rationale": "Clause normalization should follow validated template/rule pairings so reusable clause IDs reflect real drafting needs.",
|
||||
"depends_on": ["contract_templates_cn_saas_v1.json", "review_rules_cn_contract_v1.json"]
|
||||
},
|
||||
{
|
||||
"package_name": "contract_templates_cn_official_v1.json",
|
||||
"domain": "templates",
|
||||
"status": "planned",
|
||||
"priority": 7,
|
||||
"phase": "phase_3_clause_system",
|
||||
"rationale": "Official/public template curation is useful but lower priority than platform-authored commercial templates tuned for AI drafting and review.",
|
||||
"depends_on": ["laws_cn_core_v1.json", "clause_library_cn_general_v1.json"]
|
||||
},
|
||||
{
|
||||
"package_name": "industry_pack_cn_ai_data_services_v1.json",
|
||||
"domain": "templates",
|
||||
"status": "planned",
|
||||
"priority": 8,
|
||||
"phase": "phase_4_industry_expansion",
|
||||
"rationale": "High-value vertical pack should combine templates, rules, and FAQ only after core horizontal assets are coherent.",
|
||||
"depends_on": ["contract_templates_cn_saas_v1.json", "faq_cn_data_compliance_v1.json", "clause_library_cn_general_v1.json"]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,60 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "faq_cn_data_compliance_seed_v1",
|
||||
"domain": "faq",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Focused FAQ seed for SaaS/data/AI commercial contract negotiations and contract review assistance."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"faq_id": "faq_cn_data_001",
|
||||
"question": "SaaS合同里只写“服务商应保障数据安全”为什么不够?",
|
||||
"short_answer": "因为这类表述只有原则,没有分工、范围、时限和补救机制,发生事故时很难据此判断谁负责、怎么配合、赔多少。",
|
||||
"long_answer": "一份可执行的数据安全条款至少应回答五件事:处理什么数据、各方是什么角色、采取哪些最低安全措施、发生事件后多久通知、合作终止后数据如何返还或删除。如果合同只有“保障数据安全”之类的笼统义务,服务商可能无法判断合规基线,客户也无法要求具体整改;一旦发生泄露、误删或接口滥用,双方会在通知时点、日志保留、第三方配合和损失承担上产生争议。对B2B SaaS而言,建议以单独的数据处理附件承载这些内容。",
|
||||
"topic_tags": ["data_security", "contract_review", "saas"],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》委托处理相关规则", "《中华人民共和国数据安全法》数据安全管理义务"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ seed."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_002",
|
||||
"question": "客户要求“项目产生的所有成果、数据、代码均归甲方所有”时,SaaS服务商最该先审什么?",
|
||||
"short_answer": "先审归属对象有没有分层:客户数据、定制成果、预存平台、底层代码、模型能力、第三方组件不能一概而论。",
|
||||
"long_answer": "这类条款常把不同层级的资产打包处理,表面上简洁,实务上风险极高。SaaS服务商至少要把五类对象拆开:一是客户上传和业务运行形成的数据;二是为客户定制的报表、配置、接口或文档;三是服务商原有平台、底层代码、算法模型和通用组件;四是第三方软件或开源依赖;五是基于匿名化统计形成的运营洞察。如果不分层,客户可能主张取得服务商核心平台或模型相关权益,服务商则可能因保留条款过宽而无法满足客户的数据迁移和持续使用诉求。更稳妥的做法是:客户数据归客户,服务商预存IP归服务商,定制成果按项目性质单独约定所有权或使用许可。",
|
||||
"topic_tags": ["ip", "saas", "drafting"],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国著作权法》软件及作品权利归属基本规则", "《中华人民共和国民法典》合同解释与履行规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ seed."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_003",
|
||||
"question": "为什么SaaS实施项目要单独约定验收,不适合只靠“上线即完成交付”?",
|
||||
"short_answer": "因为上线不等于功能稳定、接口可用或培训完成;没有验收结构,价款支付、维保起算和违约认定都会失去客观锚点。",
|
||||
"long_answer": "很多SaaS或软件实施争议并不是“有没有上线”,而是“上线后能不能按约使用”。如果合同只写上线即交付完成,客户容易在后续以功能不达标为由拒付,服务商则会主张系统已开通、义务已履行,双方都缺乏清晰证据。更合理的设计是将交付、试运行、正式验收拆分开,分别明确测试环境、接口联调、关键缺陷定义、整改轮次、反馈期限和逾期推定规则。这样既能防止客户无限期拖延验收,也能避免服务商在重大缺陷未修复时过早触发收款。",
|
||||
"topic_tags": ["acceptance", "payment", "implementation"],
|
||||
"industry_tags": ["saas", "software"],
|
||||
"linked_rule_ids": ["rule_cn_saas_acceptance_001"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于全面履行、协作履行与违约责任的一般规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ seed."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,98 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "review_rules_cn_saas_high_risk_seed_v1",
|
||||
"domain": "rules",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "High-value seed rules for SaaS, software development, and data processing agreement review."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"rule_id": "rule_cn_saas_acceptance_001",
|
||||
"rule_name": "SaaS验收标准缺失或仅以甲方主观满意为准",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "implementation_service_agreement"],
|
||||
"clause_scope": ["acceptance", "delivery", "service_level"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["验收合格", "甲方满意", "上线即视为验收", "无异议视为验收"],
|
||||
"risk_description": "未约定可操作的验收口径、测试周期、缺陷分级和整改次数时,容易导致交付争议长期悬而未决;若仅以单方主观满意为标准,服务方难以证明已完成主要义务。",
|
||||
"review_question": "是否已经明确交付物清单、验收环境、测试方法、缺陷等级、整改期限,以及逾期不验收时的推定机制?",
|
||||
"suggested_fix": "将验收拆分为交付确认、试运行、正式验收三个节点;明确关键指标、书面异议期限、整改轮次和逾期未反馈视为阶段性通过的规则。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于全面履行、协作履行与违约责任的一般规则",
|
||||
"reason": "验收安排直接影响是否完成履行、是否存在违约以及损失认定。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:软件开发/信息化项目因验收标准不明引发价款争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_acceptance_saas_objective_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored review seed based on common commercial practice."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_saas_data_scope_002",
|
||||
"rule_name": "数据处理边界、角色分工与安全义务不清",
|
||||
"contract_scope": ["saas_service_agreement", "data_processing_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["data_processing", "data_security", "privacy"],
|
||||
"industry_scope": ["saas", "ai_data_services"],
|
||||
"severity": "critical",
|
||||
"trigger_pattern": ["数据安全", "个人信息", "委托处理", "接口数据", "训练数据"],
|
||||
"risk_description": "合同未区分控制者/处理者、委托处理范围、保存期限、删除返还义务及安全事件通知机制时,双方会在合规责任、客户索赔和监管应对上出现重大不确定性。",
|
||||
"review_question": "是否明确了数据类型、处理目的、处理方式、最小必要范围、子处理者限制、安全措施、泄露通知和终止后的删除/返还流程?",
|
||||
"suggested_fix": "新增专门的数据处理附件,逐项写明数据分类、处理角色、跨境限制、审计配合、事件通知时限、子处理者准入及终止后的数据处置义务。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国个人信息保护法》关于委托处理、处理规则透明化与处理者义务的规定",
|
||||
"reason": "涉及个人信息处理角色和委托链条时,合同需要支撑法定义务落地。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国数据安全法》关于数据安全管理义务的一般要求",
|
||||
"reason": "数据分类、保护措施和事件处置需要形成合同化约束。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:平台服务商与企业客户因数据导出、删除及泄露通知责任争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_data_processing_dpa_v1", "clause_cn_security_incident_notice_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored review seed informed by PRC data compliance practice."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_saas_ip_output_003",
|
||||
"rule_name": "平台预存知识产权与项目产出归属混同",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["intellectual_property", "deliverables", "license"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["知识产权归甲方所有", "平台", "底层代码", "模型", "接口", "成果归属"],
|
||||
"risk_description": "若将底层平台、预存代码、通用工具与定制交付成果一并约定为客户所有,可能导致服务方核心资产流失;若完全不区分客户专属成果,也会引发客户对使用权与迁移权的重大顾虑。",
|
||||
"review_question": "是否区分预存IP、第三方组件、通用能力、客户数据、定制成果及其对应的所有权、许可范围和退出迁移安排?",
|
||||
"suggested_fix": "采用分层归属结构:预存平台和通用能力归服务方,客户数据归客户,定制交付成果按约定归属或许可,并补充必要的内部使用、展示、接口调用及迁移协助条款。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于意思自治与合同解释的一般规则",
|
||||
"reason": "知识产权和成果归属需要通过明确约定避免重大解释争议。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国著作权法》关于作品和软件权利归属的基本规则",
|
||||
"reason": "代码、文档、模型相关成果的权利界定需要兼容著作权法框架。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:软件定制项目中底层代码与二次开发成果归属争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_ip_layered_allocation_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored review seed for software and AI delivery contracts."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,102 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "contract_templates_cn_saas_msa_seed_v1",
|
||||
"domain": "templates",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Seed package for high-frequency SaaS/commercial technology contract templates with reusable clause maps and intake variables."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"template_id": "tmpl_cn_saas_msa_neutral_001",
|
||||
"template_name": "SaaS主服务协议基础版",
|
||||
"contract_type": "saas_service_agreement",
|
||||
"industry": "saas",
|
||||
"scenario": "标准订阅式SaaS服务,含实施上线、账号开通、SLA和数据处理附件",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_parties_and_scope_v1", "required": true, "notes": "明确服务范围、开通方式与客户主体。"},
|
||||
{"clause_id": "clause_cn_service_term_and_renewal_v1", "required": true, "variant": "manual_renewal_default"},
|
||||
{"clause_id": "clause_cn_fees_and_invoice_saas_v1", "required": true},
|
||||
{"clause_id": "clause_cn_acceptance_saas_objective_v1", "required": true},
|
||||
{"clause_id": "clause_cn_sla_standard_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_processing_dpa_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_incident_notice_v1", "required": true},
|
||||
{"clause_id": "clause_cn_ip_layered_allocation_v1", "required": true},
|
||||
{"clause_id": "clause_cn_confidentiality_mutual_v1", "required": true},
|
||||
{"clause_id": "clause_cn_liability_cap_service_fees_v1", "required": true},
|
||||
{"clause_id": "clause_cn_termination_and_data_export_v1", "required": true}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "customer_entity_name", "type": "string", "required": true, "description": "客户签约主体全称"},
|
||||
{"name": "service_modules", "type": "string", "required": true, "description": "购买的产品模块/账号套餐"},
|
||||
{"name": "subscription_term_months", "type": "number", "required": true, "description": "首期订阅月数"},
|
||||
{"name": "implementation_required", "type": "boolean", "required": true, "description": "是否包含实施部署/培训"},
|
||||
{"name": "acceptance_days", "type": "number", "required": true, "description": "交付或上线后的验收反馈天数"},
|
||||
{"name": "uptime_target", "type": "string", "required": true, "description": "SLA可用性承诺,如99.9%"},
|
||||
{"name": "contains_personal_information", "type": "boolean", "required": true, "description": "是否处理个人信息"},
|
||||
{"name": "cross_border_transfer", "type": "boolean", "required": true, "description": "是否涉及跨境传输或境外访问"},
|
||||
{"name": "liability_cap_basis", "type": "enum", "required": true, "description": "赔偿上限基准", "enum_values": ["12_month_fees", "current_order_fees", "custom"]}
|
||||
],
|
||||
"generation_questions": [
|
||||
"客户购买的是标准订阅服务、私有化部署还是混合模式?",
|
||||
"是否需要按阶段实施、里程碑验收或接口联调清单?",
|
||||
"是否处理敏感个人信息、重要数据或客户侧限制出境的数据?",
|
||||
"客户是否要求源代码托管、数据迁移协助或退出过渡期支持?"
|
||||
],
|
||||
"review_rule_ids": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003"
|
||||
],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored seed template for future structured drafting."
|
||||
}
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_dpa_b2b_001",
|
||||
"template_name": "B2B数据处理附件基础版",
|
||||
"contract_type": "data_processing_agreement",
|
||||
"industry": "ai_data_services",
|
||||
"scenario": "作为主服务协议附件使用,明确委托处理、数据安全与事件响应",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_data_roles_and_instructions_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_categories_and_purposes_v1", "required": true},
|
||||
{"clause_id": "clause_cn_subprocessor_control_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_measures_baseline_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_incident_notice_v1", "required": true},
|
||||
{"clause_id": "clause_cn_audit_and_assistance_v1", "required": true},
|
||||
{"clause_id": "clause_cn_return_delete_on_exit_v1", "required": true}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "data_categories", "type": "string", "required": true, "description": "数据类别与字段范围说明"},
|
||||
{"name": "processing_purpose", "type": "string", "required": true, "description": "处理目的与业务功能"},
|
||||
{"name": "subprocessors_allowed", "type": "boolean", "required": true, "description": "是否允许子处理者"},
|
||||
{"name": "incident_notice_hours", "type": "number", "required": true, "description": "安全事件通知时限(小时)"},
|
||||
{"name": "return_or_delete_mode", "type": "enum", "required": true, "description": "终止后数据处置方式", "enum_values": ["return_then_delete", "delete_only", "customer_choice"]}
|
||||
],
|
||||
"generation_questions": [
|
||||
"哪些数据由客户控制、哪些数据由服务商独立决定处理?",
|
||||
"是否允许使用第三方云、短信、OCR、模型服务等子处理者?",
|
||||
"终止合作后,客户需要何种格式和时限的数据导出支持?"
|
||||
],
|
||||
"review_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored seed DPA attachment."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,599 @@
|
||||
{
|
||||
"version": 2,
|
||||
"metadata": {
|
||||
"package_name": "sources_cn_registry_v2",
|
||||
"domain": "sources",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v2",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Expanded registry for China legal content sourcing, covering official authorities, regulators, case/template references, and internal editorial sources with explicit risk and usage constraints."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"registry_id": "src_cn_npc_lawdb",
|
||||
"name": "国家法律法规数据库",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "event_driven",
|
||||
"homepage_url": "https://flk.npc.gov.cn/",
|
||||
"allowed_use": [
|
||||
"authority_reference",
|
||||
"law_text_check",
|
||||
"citation",
|
||||
"editorial_extraction"
|
||||
],
|
||||
"blocked_use": [
|
||||
"assume_unlimited_redistribution_without_review",
|
||||
"remove_source_attribution"
|
||||
],
|
||||
"notes": "Primary national source for laws, legal status, promulgation/effective dates, and many core normative texts. Highest priority for statute validation."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_gov_state_council",
|
||||
"name": "中国政府网",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.gov.cn/",
|
||||
"allowed_use": [
|
||||
"administrative_regulation_reference",
|
||||
"state_council_policy_reference",
|
||||
"citation",
|
||||
"effective_date_check"
|
||||
],
|
||||
"blocked_use": [
|
||||
"bulk_redistribution_without_review"
|
||||
],
|
||||
"notes": "Priority source for State Council regulations, decisions, policy releases, and official news notices relevant to regulatory timelines."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_moj_chinalaw",
|
||||
"name": "司法部中国法律服务网/司法行政公开资源",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.moj.gov.cn/",
|
||||
"allowed_use": [
|
||||
"department_rule_reference",
|
||||
"legal_service_guidance_reference",
|
||||
"editorial_extraction"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_as_single_source_of_truth_when_higher_authority_exists"
|
||||
],
|
||||
"notes": "Useful supplementary ministry source for departmental rules, policy interpretations, and public legal service guidance."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_spc",
|
||||
"name": "最高人民法院官网",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.court.gov.cn/",
|
||||
"allowed_use": [
|
||||
"judicial_interpretation_reference",
|
||||
"guiding_case_reference",
|
||||
"typical_case_reference",
|
||||
"citation"
|
||||
],
|
||||
"blocked_use": [
|
||||
"bulk_case_redistribution_without_review",
|
||||
"infer_binding_effect_beyond_published_scope"
|
||||
],
|
||||
"notes": "Priority source for judicial interpretations, guiding cases, typical cases, and adjudication policy signals."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_spc_judgments",
|
||||
"name": "中国裁判文书网",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "high",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://wenshu.court.gov.cn/",
|
||||
"allowed_use": [
|
||||
"case_pattern_research",
|
||||
"fact_pattern_reference",
|
||||
"non_binding_argument_mining"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_single_case_as_binding_rule",
|
||||
"bulk_copy_full_text",
|
||||
"process_personal_information_without_review"
|
||||
],
|
||||
"notes": "Use for dispute pattern and reasoning research only; pay attention to privacy, publication completeness, and non-binding nature."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_spc_enforcement_info",
|
||||
"name": "中国执行信息公开网",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "high",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "http://zxgk.court.gov.cn/",
|
||||
"allowed_use": [
|
||||
"counterparty_risk_reference",
|
||||
"enforcement_status_check"
|
||||
],
|
||||
"blocked_use": [
|
||||
"profile_building_without_purpose_limit",
|
||||
"bulk_personal_data_collection"
|
||||
],
|
||||
"notes": "Operational risk source for counterparty checks; sensitive because it may involve personal and corporate enforcement data."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_spp",
|
||||
"name": "最高人民检察院官网",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.spp.gov.cn/",
|
||||
"allowed_use": [
|
||||
"compliance_case_reference",
|
||||
"public_procuratorial_guidance_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_as_civil_binding_authority"
|
||||
],
|
||||
"notes": "Useful for compliance, anti-fraud, anti-corruption, and public-interest litigation trend monitoring."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_samr",
|
||||
"name": "国家市场监督管理总局",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.samr.gov.cn/",
|
||||
"allowed_use": [
|
||||
"competition_rule_reference",
|
||||
"advertising_rule_reference",
|
||||
"contract_supervision_reference",
|
||||
"compliance_alert_monitoring"
|
||||
],
|
||||
"blocked_use": [
|
||||
"assume_local_enforcement_alignment_without_check"
|
||||
],
|
||||
"notes": "Core regulator source for anti-unfair competition, advertising, consumer protection, standard contracts, and compliance enforcement notices."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_cac",
|
||||
"name": "国家互联网信息办公室",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.cac.gov.cn/",
|
||||
"allowed_use": [
|
||||
"data_compliance_rule_reference",
|
||||
"personal_information_rule_reference",
|
||||
"cybersecurity_policy_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"use_outdated_draft_as_effective_rule"
|
||||
],
|
||||
"notes": "Primary regulator source for CAC measures, draft consultations, and public guidance on data export, algorithms, and personal information protection."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_miit",
|
||||
"name": "工业和信息化部",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.miit.gov.cn/",
|
||||
"allowed_use": [
|
||||
"telecom_and_it_rule_reference",
|
||||
"software_service_policy_reference",
|
||||
"industry_compliance_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_industry_guidance_as_universal_contract_rule"
|
||||
],
|
||||
"notes": "Important for SaaS, telecom, platform, software, and industrial internet related sector rules and notices."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_mps",
|
||||
"name": "公安部",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.mps.gov.cn/",
|
||||
"allowed_use": [
|
||||
"cybersecurity_enforcement_reference",
|
||||
"public_security_compliance_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_press_release_as_complete_legal_rule"
|
||||
],
|
||||
"notes": "Supplementary source for cybersecurity enforcement trends and public security related compliance expectations."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_mofcom",
|
||||
"name": "商务部",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.mofcom.gov.cn/",
|
||||
"allowed_use": [
|
||||
"foreign_trade_reference",
|
||||
"foreign_investment_reference",
|
||||
"commercial_policy_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"use_as_only_source_for_cross_border_structuring"
|
||||
],
|
||||
"notes": "Useful for cross-border trade, foreign investment, e-commerce, and commercial policy materials."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_mhrss",
|
||||
"name": "人力资源和社会保障部",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.mohrss.gov.cn/",
|
||||
"allowed_use": [
|
||||
"employment_rule_reference",
|
||||
"social_insurance_rule_reference",
|
||||
"labor_policy_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"ignore_local_labor_rule_variation"
|
||||
],
|
||||
"notes": "Core source for national labor and social insurance rules; must be paired with local human resources bureaus for implementation detail."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_csrc",
|
||||
"name": "中国证券监督管理委员会",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.csrc.gov.cn/",
|
||||
"allowed_use": [
|
||||
"securities_compliance_reference",
|
||||
"fundraising_rule_reference",
|
||||
"listed_company_governance_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"apply_capital_market_rules_to_private_company_template_without_scope_check"
|
||||
],
|
||||
"notes": "Needed for equity transfer, financing, and governance packs that may touch capital markets or public company standards."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_pbc",
|
||||
"name": "中国人民银行",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "http://www.pbc.gov.cn/",
|
||||
"allowed_use": [
|
||||
"payments_compliance_reference",
|
||||
"financial_data_compliance_reference",
|
||||
"anti_money_laundering_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_sector_guidance_as_general_contract_default"
|
||||
],
|
||||
"notes": "Relevant for payment clauses, fintech operations, anti-money-laundering, and data governance in financial contexts."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_nfra",
|
||||
"name": "国家金融监督管理总局",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.cbirc.gov.cn/",
|
||||
"allowed_use": [
|
||||
"banking_insurance_compliance_reference",
|
||||
"consumer_finance_rule_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"apply_licensed_finance_rules_out_of_context"
|
||||
],
|
||||
"notes": "Sector regulator source for banking, insurance, consumer finance, outsourcing, and personal information handling in financial services."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_nmpa",
|
||||
"name": "国家药品监督管理局",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.nmpa.gov.cn/",
|
||||
"allowed_use": [
|
||||
"medical_advertising_reference",
|
||||
"drug_device_compliance_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"use_for_non_healthcare_templates_without_scope_check"
|
||||
],
|
||||
"notes": "Useful in healthcare, medical advertising, and regulated product transaction templates."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_cnipa",
|
||||
"name": "国家知识产权局",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.cnipa.gov.cn/",
|
||||
"allowed_use": [
|
||||
"ip_rule_reference",
|
||||
"trademark_patent_guidance_reference",
|
||||
"ip_administrative_case_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_exam_guidelines_as_contractual_default_rule"
|
||||
],
|
||||
"notes": "Core source for patent, trademark, and other IP administration guidance relevant to license and ownership clauses."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_namr_enterprise_credit",
|
||||
"name": "国家企业信用信息公示系统",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "high",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.gsxt.gov.cn/",
|
||||
"allowed_use": [
|
||||
"counterparty_identity_check",
|
||||
"corporate_status_check",
|
||||
"license_scope_check"
|
||||
],
|
||||
"blocked_use": [
|
||||
"bulk_profile_scraping",
|
||||
"identity_decisions_without_human_review"
|
||||
],
|
||||
"notes": "Important operational source for verifying business registration, abnormal status, and licensing scope of counterparties."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_local_high_courts",
|
||||
"name": "地方高院/法院公开平台",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN-local",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.court.gov.cn/",
|
||||
"allowed_use": [
|
||||
"local_adjudication_trend_reference",
|
||||
"local_typical_case_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"assume_nationwide_applicability_without_escalation"
|
||||
],
|
||||
"notes": "Use when labor, tenancy, construction, or platform disputes show strong regional practice differences."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_local_hrss",
|
||||
"name": "地方人社局/仲裁委公开资源",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "primary",
|
||||
"jurisdiction": "CN-local",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.mohrss.gov.cn/",
|
||||
"allowed_use": [
|
||||
"local_labor_rule_reference",
|
||||
"local_hr_guidance_reference",
|
||||
"arbitration_practice_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"apply_city_specific_policy_to_other_regions_without_check"
|
||||
],
|
||||
"notes": "Mandatory local supplement for employment, social insurance, dispatch, non-compete, and termination packs."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_local_market_regulators",
|
||||
"name": "地方市场监管局公开资源",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN-local",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.samr.gov.cn/",
|
||||
"allowed_use": [
|
||||
"local_enforcement_reference",
|
||||
"advertising_and_promotion_compliance_reference"
|
||||
],
|
||||
"blocked_use": [
|
||||
"assume_local_penalty_notice_equals_general_rule"
|
||||
],
|
||||
"notes": "Useful for ad-tech, e-commerce, live-streaming, and promotional template adjustments tied to local enforcement posture."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_standard_contract_examples",
|
||||
"name": "官方或准官方示范文本/示范合同",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "ad_hoc",
|
||||
"homepage_url": "https://www.gov.cn/",
|
||||
"allowed_use": [
|
||||
"template_structure_reference",
|
||||
"clause_benchmarking",
|
||||
"term_coverage_check"
|
||||
],
|
||||
"blocked_use": [
|
||||
"copy_as_final_customer_contract_without_editorial_review"
|
||||
],
|
||||
"notes": "Includes government and regulator-issued model agreements and filing templates. Useful as baseline structure, not turnkey output."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_cn_public_casebooks",
|
||||
"name": "法院/监管公开典型案例专栏",
|
||||
"source_type": "official_public",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "monthly",
|
||||
"homepage_url": "https://www.court.gov.cn/",
|
||||
"allowed_use": [
|
||||
"case_digest_authoring",
|
||||
"risk_scenario_reference",
|
||||
"faq_example_support"
|
||||
],
|
||||
"blocked_use": [
|
||||
"treat_typical_case_as_statute_or_binding_interpretation"
|
||||
],
|
||||
"notes": "Best suited for user-facing examples, FAQs, and risk spotting rather than direct rule statements."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_public_editorial_lawfirm_articles",
|
||||
"name": "公开律所实务文章/合规观察",
|
||||
"source_type": "public_editorial",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "high",
|
||||
"update_frequency": "weekly",
|
||||
"homepage_url": "https://www.example.com/",
|
||||
"allowed_use": [
|
||||
"issue_spotting",
|
||||
"practical_interpretation_reference",
|
||||
"terminology_normalization"
|
||||
],
|
||||
"blocked_use": [
|
||||
"copy_substantial_expression",
|
||||
"treat_editorial_view_as_authority"
|
||||
],
|
||||
"notes": "Use only as practical commentary or issue-spotting aid; independently verify all rules against official sources."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_public_editorial_industry_associations",
|
||||
"name": "行业协会公开规则/倡议/指引",
|
||||
"source_type": "public_editorial",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "monthly",
|
||||
"homepage_url": "https://www.example.com/",
|
||||
"allowed_use": [
|
||||
"industry_practice_reference",
|
||||
"soft_law_reference",
|
||||
"package_context_enrichment"
|
||||
],
|
||||
"blocked_use": [
|
||||
"portray_soft_law_as_mandatory_national_rule"
|
||||
],
|
||||
"notes": "Useful for industry package context, self-discipline standards, and operational expectations where no formal rule directly answers workflow questions."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_internal_authored",
|
||||
"name": "Internal authored legal content",
|
||||
"source_type": "internal_authored",
|
||||
"authority_level": "editorial",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "manual",
|
||||
"license_risk": "low",
|
||||
"update_frequency": "ad_hoc",
|
||||
"allowed_use": [
|
||||
"template_authoring",
|
||||
"rule_authoring",
|
||||
"faq_authoring",
|
||||
"clause_normalization",
|
||||
"industry_pack_compilation"
|
||||
],
|
||||
"blocked_use": [],
|
||||
"notes": "Platform-authored derivative content that synthesizes official sources, cases, and editorial judgment into reusable assets."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_customer_authorized_templates",
|
||||
"name": "客户授权脱敏模板/规则",
|
||||
"source_type": "customer_authorized",
|
||||
"authority_level": "customer_private",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "upload",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "ad_hoc",
|
||||
"allowed_use": [
|
||||
"tenant_customization",
|
||||
"playbook_alignment",
|
||||
"fallback_clause_comparison"
|
||||
],
|
||||
"blocked_use": [
|
||||
"public_export",
|
||||
"cross_customer_reuse_without_permission"
|
||||
],
|
||||
"notes": "Allowed only in private tenant workflows after authorization and de-identification review."
|
||||
},
|
||||
{
|
||||
"registry_id": "src_commercial_licensed_databases",
|
||||
"name": "商业授权法规/案例数据库",
|
||||
"source_type": "commercial_licensed",
|
||||
"authority_level": "secondary",
|
||||
"jurisdiction": "CN",
|
||||
"access_mode": "licensed_portal",
|
||||
"license_risk": "medium",
|
||||
"update_frequency": "daily",
|
||||
"homepage_url": "https://www.example.com/",
|
||||
"allowed_use": [
|
||||
"research_acceleration",
|
||||
"cross_check_indexing",
|
||||
"historical_version_lookup"
|
||||
],
|
||||
"blocked_use": [
|
||||
"redistribution_outside_license_scope",
|
||||
"treat_vendor_editorial_headnotes_as_authoritative"
|
||||
],
|
||||
"notes": "Optional productivity layer for retrieval and historical lookup; license terms must be checked per vendor before ingestion or export."
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,905 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "clause_library_cn_general_v1",
|
||||
"domain": "clauses",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Minimum viable Chinese clause library for SaaS, software, NDA, and AI data service contract templates with questionnaire/review linkage."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"clause_id": "clause_cn_parties_and_scope_v1",
|
||||
"clause_type": "parties_scope",
|
||||
"title": "合同主体与服务范围",
|
||||
"text": "双方确认以订单、服务说明、实施计划、数据处理附件及本协议共同构成完整交易文件。服务商按照订单所列产品模块、账号数量、开通环境、接口范围和服务边界向客户提供服务;未在订单或附件中明确列示的定制开发、现场驻场、第三方采购、数据治理或合规申报服务,不当然包含在本协议范围内。客户应保证签约主体、关联使用主体及管理员账号信息真实有效,并就其授权使用行为承担责任。",
|
||||
"plain_explanation": "先把签约主体、文件层级和服务边界说清,避免客户默认“买了平台就包含所有项目工作”。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": [
|
||||
"未区分订单范围与额外需求,导致范围蔓延",
|
||||
"关联公司使用但责任主体不清"
|
||||
],
|
||||
"negotiation_points": [
|
||||
"是否允许关联公司共同使用",
|
||||
"是否把实施、培训、接口接入列为基础服务或增值服务"
|
||||
],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"implementation_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》合同编关于合同内容和履行的一般规则"],
|
||||
"recommended_variants": ["standard_order_form", "affiliate_use_enabled"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored general scope clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_definitions_order_docs_v1",
|
||||
"clause_type": "definitions",
|
||||
"title": "定义与文件优先级",
|
||||
"text": "本协议项下“服务”“客户数据”“交付物”“预存知识产权”“安全事件”“工作日”等术语,以本协议及附件中的定义为准。若本协议、订单、实施计划、验收单、数据处理附件之间存在不一致,除双方另有书面约定外,按个别订单特别约定优先于主协议,数据处理事项优先适用数据处理附件,实施里程碑和验收标准优先适用经双方确认的实施/项目文件。",
|
||||
"plain_explanation": "为后续问卷生成和审查联动提供统一术语和文件优先级。",
|
||||
"risk_level": "low",
|
||||
"common_risks": ["多个附件冲突时无适用顺序"],
|
||||
"negotiation_points": ["订单与主协议冲突时谁优先"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"data_processing_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于合同解释的一般规则"],
|
||||
"recommended_variants": ["master_order_priority", "attachment_priority"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored definitions clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_service_term_and_renewal_v1",
|
||||
"clause_type": "term_renewal",
|
||||
"title": "期限、续约与暂停",
|
||||
"text": "服务期限自订单约定的开通日或验收通过日开始计算,首期服务期限、续费价格、自动续约或人工续约规则以订单为准。任何一方如不续约,应于当前期限届满前不少于三十日书面通知对方。客户逾期付款、严重超量使用或存在影响平台安全的行为时,服务商可在催告后暂停相应服务;暂停不影响客户已产生的付款义务。",
|
||||
"plain_explanation": "控制起算点、续约方式和暂停权。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["起算日不清导致服务期和维保期争议", "自动续约未充分提示"],
|
||||
"negotiation_points": ["是否自动续约", "暂停前通知期和补救期"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于期限和履行的一般规则"],
|
||||
"recommended_variants": ["manual_renewal_default", "auto_renewal_with_notice"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored term clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_fees_and_invoice_saas_v1",
|
||||
"clause_type": "fees_invoice",
|
||||
"title": "费用、付款与开票",
|
||||
"text": "客户应按照订单约定的订阅费、实施费、开发费、超量使用费或第三方资源费付款。除非订单另有约定,服务商在收到对应款项或达到约定里程碑后开具合法有效的增值税发票。客户对账单或发票有异议的,应在收到后五个工作日内提出书面说明;无正当理由逾期付款的,服务商有权要求客户按中国人民银行授权全国银行间同业拆借中心公布的一年期贷款市场报价利率为基础计收逾期违约金。",
|
||||
"plain_explanation": "把费用口径、开票触发点和逾期付款后果标准化。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["开票前置到收款前导致现金流压力", "超量使用计费口径不清"],
|
||||
"negotiation_points": ["预付款还是里程碑付款", "发票类型和开票节点"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于价款支付和违约责任的一般规则"],
|
||||
"recommended_variants": ["annual_prepay", "milestone_payment"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored fees clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_delivery_implementation_plan_v1",
|
||||
"clause_type": "delivery_implementation",
|
||||
"title": "实施计划、协作义务与交付条件",
|
||||
"text": "涉及实施、部署、培训、接口联调或数据迁移的,双方应确认项目负责人、实施计划、客户配合事项、依赖系统、测试环境和里程碑。客户未按时提供账号、接口文档、测试数据、决策反馈或现场资源的,相关时间表顺延,服务商不因此承担逾期交付责任;若客户需求变化导致工作量实质增加,双方应另行签署变更单并调整周期与费用。",
|
||||
"plain_explanation": "给实施项目设置配合前提和变更入口。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["客户不配合却主张服务商逾期", "需求蔓延未形成变更单"],
|
||||
"negotiation_points": ["项目计划是否写入合同", "顺延触发条件是否客观化"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"implementation_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于协作履行的一般规则"],
|
||||
"recommended_variants": ["simple_project_plan", "change_order_required"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored implementation clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_acceptance_saas_objective_v1",
|
||||
"clause_type": "acceptance",
|
||||
"title": "交付与验收标准",
|
||||
"text": "双方应以订单、需求清单、原型说明、接口文档、测试用例或上线检查表作为验收依据。服务商提交交付物或完成上线后,客户应在约定验收期内按双方确认的环境和方法进行测试,并一次性书面列明缺陷及对应依据;缺陷分为重大缺陷与一般缺陷,一般缺陷不影响阶段性验收通过,服务商应在合理期限内修复。客户逾期未反馈或仅以主观满意度拒绝验收的,视为对应阶段交付已通过验收。",
|
||||
"plain_explanation": "避免只写“甲方满意”或“上线即验收”,支持规则 rule_cn_saas_acceptance_001。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["验收标准主观化", "无限期拖延验收", "缺陷分级缺失"],
|
||||
"negotiation_points": ["验收期长度", "是否设置试运行期", "逾期视为通过机制"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"implementation_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于全面履行和违约责任的一般规则"],
|
||||
"recommended_variants": ["phase_acceptance", "go_live_plus_trial_run"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored acceptance clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_sla_standard_v1",
|
||||
"clause_type": "service_level",
|
||||
"title": "服务级别与支持响应",
|
||||
"text": "服务商应在约定维护窗口外尽商业上合理努力维持服务可用性达到订单约定指标,并提供工单、邮件或电话支持。因客户网络、第三方服务、计划维护、不可抗力、客户违规操作或超出约定使用上限导致的中断,不计入可用性统计。双方可按故障等级约定响应和恢复目标;除订单明确约定服务抵扣外,SLA违约的主要补救方式为服务积分、延期服务或合理整改,不当然构成客户解除全部合同的依据。",
|
||||
"plain_explanation": "把可用性统计口径和SLA补救方式标准化。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["把所有中断都计入SLA", "SLA违约直接触发无限赔偿"],
|
||||
"negotiation_points": ["可用性目标", "支持时间窗", "SLA补偿上限"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于继续履行和违约补救的一般规则"],
|
||||
"recommended_variants": ["99_5_standard", "99_9_business_critical"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored SLA clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_confidentiality_mutual_v1",
|
||||
"clause_type": "confidentiality",
|
||||
"title": "保密义务",
|
||||
"text": "任一方对在合作过程中获悉的商业秘密、技术信息、客户名单、价格条款、系统架构、接口文档、模型参数、测试结果及其他依法或按性质应视为保密的信息承担保密义务。接收方仅可为履行本协议之目的在知悉必要范围内向其员工、关联公司或经批准的分包商披露,并应确保其承担不低于本协议的保密义务。法律、监管或司法机关要求披露的,接收方应在法律允许范围内及时通知披露方。保密义务自信息披露之日起生效,并在协议终止后持续不少于三年;商业秘密依法长期受保护。",
|
||||
"plain_explanation": "可作为主协议中的保密条款,也可支持基础版NDA。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["保密信息范围过窄", "未覆盖员工和分包商", "保密期限过短"],
|
||||
"negotiation_points": ["例外范围", "残余知识条款", "保密期限"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"non_disclosure_agreement",
|
||||
"data_processing_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国反不正当竞争法》商业秘密保护规则"],
|
||||
"recommended_variants": ["mutual_standard", "customer_disclosure_only"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored confidentiality clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_data_processing_dpa_v1",
|
||||
"clause_type": "data_processing",
|
||||
"title": "数据处理附件适用",
|
||||
"text": "如服务涉及客户数据、个人信息、业务日志、训练样本或其他受监管数据的处理,双方同意以数据处理附件明确处理角色、处理目的、处理方式、数据类别、保存期限、安全措施、跨境限制、子处理者管理、事件通知以及终止后的返还删除要求;主协议与数据处理附件冲突时,就数据处理事项以附件为准。",
|
||||
"plain_explanation": "在主协议中嵌入DPA挂接点,方便模板联动。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["主协议未设置数据附件入口", "数据合规义务散落在多处且相互冲突"],
|
||||
"negotiation_points": ["是否必须单签DPA", "冲突时哪个文件优先"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》委托处理相关规则"],
|
||||
"recommended_variants": ["dpa_required", "short_form_data_schedule"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored DPA bridge clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_data_roles_and_instructions_v1",
|
||||
"clause_type": "data_roles",
|
||||
"title": "数据角色与处理指示",
|
||||
"text": "就客户提供或授权访问的数据,客户作为处理目的和方式的决定方,应保证其具有合法来源和处理依据;服务商按照客户书面指示及本协议约定在必要范围内处理相关数据,并不得超出约定目的擅自使用。若服务商就平台运行安全、计费结算、匿名化统计或法律要求而独立处理部分数据,双方应在附件中单独说明该等处理的性质和边界。",
|
||||
"plain_explanation": "区分控制者/处理者和服务商独立处理场景。",
|
||||
"risk_level": "critical",
|
||||
"common_risks": ["角色不清导致合规责任不明", "超目的使用数据"],
|
||||
"negotiation_points": ["是否存在服务商独立处理数据", "客户指示的形式和留痕方式"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》关于委托处理的规定"],
|
||||
"recommended_variants": ["processor_only", "mixed_roles"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored data role clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_data_categories_and_purposes_v1",
|
||||
"clause_type": "data_scope",
|
||||
"title": "数据类别、处理目的与保存期限",
|
||||
"text": "双方应在附件中列明数据主体类别、数据字段范围、是否包含敏感个人信息、重要数据或训练样本、处理目的、处理动作、访问权限、保存期限及删除触发条件。服务商仅在实现约定业务功能、保障安全、故障排查、计费结算和法律要求的范围内处理相关数据;超出前述范围的新增场景,应经双方书面确认。",
|
||||
"plain_explanation": "把数据范围和目的列成问卷项,支持审查规则 rule_cn_saas_data_scope_002。",
|
||||
"risk_level": "critical",
|
||||
"common_risks": ["数据范围描述过宽", "保存期限无限延长"],
|
||||
"negotiation_points": ["是否涉及敏感个人信息", "日志保存期限"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》最小必要原则", "《中华人民共和国数据安全法》分类分级管理要求"],
|
||||
"recommended_variants": ["pi_only", "pi_plus_training_data"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored data scope clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_security_measures_baseline_v1",
|
||||
"clause_type": "security_measures",
|
||||
"title": "安全措施基线",
|
||||
"text": "服务商应结合服务性质建立与风险相适应的管理和技术措施,包括账号权限控制、身份认证、日志留存、访问审计、漏洞修复、备份恢复、恶意代码防护、传输和存储安全、环境隔离以及人员保密和权限管理。除非订单另有约定,服务商不承诺达到客户内部未披露的专项安全标准;如客户要求通过特定认证、等保、专线、驻场或专属隔离环境,应作为专项服务另行约定。",
|
||||
"plain_explanation": "设定最低安全基线,同时避免被默认为承担客户全部内部安全要求。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["安全义务过于抽象", "默认承担未披露的客户标准"],
|
||||
"negotiation_points": ["是否要求等保/ISO/专线", "日志保留时长"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国数据安全法》一般安全管理义务"],
|
||||
"recommended_variants": ["baseline_standard", "enhanced_enterprise_security"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored security baseline clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_security_incident_notice_v1",
|
||||
"clause_type": "security_incident",
|
||||
"title": "安全事件通知与协同处置",
|
||||
"text": "一方发现可能影响客户数据、服务连续性或监管合规的安全事件后,应在约定时限内通知另一方,并提供已知影响范围、初步原因、临时控制措施、建议配合事项及后续更新安排。双方应按照各自责任边界开展调查、修复、取证、监管应对和客户通知。除法律另有规定或事故责任明确归属于服务商外,任何对外通报、媒体回应或向终端主体通知的内容和时点应由双方协商确定。",
|
||||
"plain_explanation": "明确通知时点和协作机制,避免事故发生后各说各话。",
|
||||
"risk_level": "critical",
|
||||
"common_risks": ["通知时限缺失", "对外通报权责不清", "事故处置分工不明"],
|
||||
"negotiation_points": ["通知时限按小时还是工作日", "是否必须提供根因报告"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》安全事件处置规则", "《中华人民共和国数据安全法》事件报告要求"],
|
||||
"recommended_variants": ["24h_notice", "48h_notice"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored incident response clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_subprocessor_control_v1",
|
||||
"clause_type": "subprocessor",
|
||||
"title": "分包与第三方处理者管理",
|
||||
"text": "服务商可在实现云基础设施、消息通知、身份验证、模型推理、客服支持、运维监控或其他必要功能的范围内使用分包商或第三方处理者,但应确保其承担与本协议不低于同等的数据保护和保密义务。涉及客户核心数据、敏感个人信息或境外访问权限的分包安排,应按附件约定履行提前通知、名单披露或客户合理异议程序。服务商对其分包商履行相关义务承担管理责任,但对客户自行选定的第三方系统或接口服务不承担超出自身过错范围的责任。",
|
||||
"plain_explanation": "处理云厂商、短信商、模型服务商等第三方链条。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["子处理者名单不透明", "客户自选第三方风险倒灌给服务商"],
|
||||
"negotiation_points": ["是否需事前同意", "可接受的异议机制"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》委托处理链条要求"],
|
||||
"recommended_variants": ["notice_only", "prior_consent_for_sensitive_data"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored subprocessor clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_audit_and_assistance_v1",
|
||||
"clause_type": "audit_assistance",
|
||||
"title": "审计配合与合规协助",
|
||||
"text": "在合理频次和不影响服务商正常运营的前提下,服务商可通过提供合规说明、第三方审计报告、问卷回复、访谈或受控远程审阅方式,协助客户完成与本协议相关的安全或合规评估。客户发起现场审计、渗透测试、监管专项核查协助或超出常规范围的材料整理的,双方应提前协商范围、保密安排、费用承担和时间表。",
|
||||
"plain_explanation": "给客户一定审计权,但避免无限制现场检查。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["审计频次无限制", "客户单方要求高成本配合"],
|
||||
"negotiation_points": ["优先提供SOC/ISO报告还是开放现场审计", "额外费用承担"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》协作履行规则"],
|
||||
"recommended_variants": ["documentation_first", "onsite_audit_limited"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored audit assistance clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_ip_layered_allocation_v1",
|
||||
"clause_type": "intellectual_property",
|
||||
"title": "知识产权分层归属与许可",
|
||||
"text": "服务商在签约前已拥有或在履约过程中独立形成的底层平台、通用代码、算法模型、模板、开发工具、接口框架、文档体系、匿名化统计方法及其改进,均归服务商或其许可方所有。客户依法享有其上传、提供或基于自身业务产生的客户数据及客户专有资料权益。双方就客户专属定制交付物,可在订单中约定由客户取得所有权、排他使用权或非排他永久使用权,但无论如何不影响服务商对其预存知识产权、通用能力和第三方组件的权利。服务商可在不识别客户身份且不泄露客户保密信息的前提下,将履约经验、通用功能和匿名化统计用于产品优化。",
|
||||
"plain_explanation": "把客户数据、定制成果、底层平台、第三方组件分层处理,支持规则 rule_cn_saas_ip_output_003。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["将底层平台一并转让", "客户对定制成果使用权不明确", "匿名化优化使用边界不清"],
|
||||
"negotiation_points": ["定制成果归属还是许可", "是否允许匿名化产品优化"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国著作权法》软件及作品权利归属规则", "《中华人民共和国民法典》合同解释规则"],
|
||||
"recommended_variants": ["layered_default", "customer_owned_custom_deliverables"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored IP layering clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_breach_and_indemnity_general_v1",
|
||||
"clause_type": "breach_liability",
|
||||
"title": "违约责任与补救",
|
||||
"text": "任一方违反本协议导致对方损失的,应在其过错范围内承担违约责任。违约方在收到书面通知后应于合理期限内采取补救措施;能够通过继续履行、修复、更换、重做、补开发票、补交资料或支付延期违约金弥补的,优先适用相应补救方式。若一方严重违反保密、数据处理、知识产权或付款义务且在催告后仍未改正,守约方有权解除相关订单或本协议并追究损失。",
|
||||
"plain_explanation": "先给补救路径,再落到严重违约解除。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["违约后果过重或过轻", "未区分可补救和不可补救违约"],
|
||||
"negotiation_points": ["补救期长度", "解除是否限于相关订单"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"non_disclosure_agreement",
|
||||
"data_processing_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于违约责任和解除的一般规则"],
|
||||
"recommended_variants": ["order_level_termination", "master_level_termination"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored breach clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_liability_cap_service_fees_v1",
|
||||
"clause_type": "liability_cap",
|
||||
"title": "责任限制与赔偿上限",
|
||||
"text": "除故意、重大过失、侵犯知识产权、违反保密义务、依法不得限制的个人信息侵权责任以及客户应付未付价款外,任一方因本协议承担的累计赔偿责任总额,以争议发生前十二个月内客户就相关订单已实际支付的费用总额为上限;服务抵扣、退款和违约金合并计算在该上限内。任一方对利润损失、商誉损失、机会损失、预期节省落空或其他间接损失不承担责任,但法律另有强制规定的除外。",
|
||||
"plain_explanation": "统一责任上限基准,并保留法定例外。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["上限过低被客户否决", "未列法定例外导致可执行性风险"],
|
||||
"negotiation_points": ["12个月费用还是当前订单费用", "是否排除间接损失"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"data_processing_agreement",
|
||||
"ai_service_agreement",
|
||||
"non_disclosure_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于违约损失和格式条款效力的一般规则"],
|
||||
"recommended_variants": ["12_month_fees", "current_order_fees"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored liability cap clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_dispute_resolution_cn_court_v1",
|
||||
"clause_type": "dispute_resolution",
|
||||
"title": "适用法律与争议解决",
|
||||
"text": "本协议的订立、效力、解释、履行及争议解决均适用中华人民共和国法律。双方因本协议发生争议的,应先友好协商;协商不成的,任一方可向被告住所地或订单约定的有管辖权的人民法院提起诉讼。争议解决期间,除争议事项外,双方仍应继续履行不受影响的条款。",
|
||||
"plain_explanation": "提供中国法+法院诉讼的默认路径。",
|
||||
"risk_level": "low",
|
||||
"common_risks": ["未约定管辖导致程序成本增加"],
|
||||
"negotiation_points": ["原告地还是被告地", "仲裁还是诉讼"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"non_disclosure_agreement",
|
||||
"data_processing_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》", "《中华人民共和国民事诉讼法》"],
|
||||
"recommended_variants": ["court_default", "arbitration_shanghai"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored dispute clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_termination_and_data_export_v1",
|
||||
"clause_type": "termination_exit",
|
||||
"title": "终止、退出过渡与数据导出",
|
||||
"text": "协议或订单到期、终止或解除后,客户在付清到期应付款项的前提下,可在约定过渡期内申请导出其客户数据、配置文件、约定报表及接口文档副本。服务商应按订单约定的格式、次数和协助强度提供合理的数据导出与迁移支持;超出基础导出范围的深度清洗、映射转换、现场支持或与替代供应商对接的工作,双方应另行计费。终止不影响双方在终止前已产生的付款、保密、知识产权、责任限制和争议解决义务。",
|
||||
"plain_explanation": "把退出支持和存续条款打通。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["未承诺导出导致客户阻力", "无限制迁移协助导致交付失控"],
|
||||
"negotiation_points": ["导出格式", "过渡期长短", "是否额外收费"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于合同终止后结算和附随义务的一般规则"],
|
||||
"recommended_variants": ["csv_export_basic", "assisted_migration_paid"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored termination and export clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_return_delete_on_exit_v1",
|
||||
"clause_type": "data_return_delete",
|
||||
"title": "终止后的返还与删除",
|
||||
"text": "在法律法规、审计留存或争议保全另有要求的情形外,服务商应在约定保留期届满后,对客户数据执行返还、导出后删除或按客户选择处置,并保留必要的处置记录。若出于备份轮换、灾备镜像或日志归档原因无法立即物理删除,服务商应限制访问、禁止继续业务性使用,并在系统覆盖周期内完成删除。",
|
||||
"plain_explanation": "细化数据删除可执行路径,兼顾备份现实。",
|
||||
"risk_level": "critical",
|
||||
"common_risks": ["只承诺删除但未考虑备份", "无处置留痕"],
|
||||
"negotiation_points": ["保留期时长", "删除证明形式"],
|
||||
"applicable_contract_types": [
|
||||
"data_processing_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》删除和委托处理终止要求"],
|
||||
"recommended_variants": ["return_then_delete", "delete_only"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored return/delete clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_third_party_services_dependency_v1",
|
||||
"clause_type": "third_party_dependency",
|
||||
"title": "第三方服务与外部依赖",
|
||||
"text": "如服务依赖客户自有系统、第三方云资源、短信/邮件通道、支付接口、地图服务、OCR能力、基础模型或其他外部供应商,双方应在订单或实施文件中列明依赖项、责任边界、可用性前提和费用承担。因客户指定的第三方服务中断、限流、封禁、价格调整或政策变更导致的性能下降、功能受限或进度延误,服务商在其无过错范围内不承担违约责任,但应提供合理替代建议或协助。",
|
||||
"plain_explanation": "解决AI和SaaS项目常见的外部API/云资源依赖问题。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["第三方故障被全部归责服务商", "价格变化无人承担"],
|
||||
"negotiation_points": ["替代方案义务", "第三方费用转嫁机制"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于过错责任和协作履行的一般规则"],
|
||||
"recommended_variants": ["customer_designated_dependency", "vendor_managed_dependency"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored third-party dependency clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_software_dev_deliverables_and_change_control_v1",
|
||||
"clause_type": "software_deliverables_change_control",
|
||||
"title": "软件开发交付物与需求变更控制",
|
||||
"text": "软件开发项目的交付物包括需求规格、原型/设计稿、源代码或目标代码、接口文档、部署文档、测试报告及验收材料,具体以项目清单为准。任何新增功能、范围调整、第三方系统变更、性能指标提升或安全整改要求,若导致工作量、周期或成本变化,应通过书面变更单确认后执行;未完成变更确认前,服务商有权按照原范围继续实施。",
|
||||
"plain_explanation": "为软件开发基础版补足交付清单和变更单机制。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["交付物不完整", "新增需求无偿化"],
|
||||
"negotiation_points": ["源代码交付范围", "变更单审批时限"],
|
||||
"applicable_contract_types": [
|
||||
"software_development_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["software", "saas"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于合同变更和履行的一般规则"],
|
||||
"recommended_variants": ["source_code_delivery", "binary_only_delivery"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored software development clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_maintenance_support_post_acceptance_v1",
|
||||
"clause_type": "maintenance_support",
|
||||
"title": "验收后维保与支持",
|
||||
"text": "软件开发项目验收通过后,服务商在约定维保期内对交付物中的缺陷提供修复支持,并可按订单约定提供功能优化、版本升级、运维值守或驻场支持。因客户自行修改代码、非授权第三方介入、客户基础设施故障或需求新增引起的问题,不属于免费维保范围。维保期届满后的支持服务,由双方另行签署运维或技术支持订单。",
|
||||
"plain_explanation": "区分缺陷修复、功能升级和后续运维服务。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["维保和新增需求边界不清", "客户改码后仍要求免费修复"],
|
||||
"negotiation_points": ["维保期长度", "响应时效", "是否含小版本升级"],
|
||||
"applicable_contract_types": [
|
||||
"software_development_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["software", "saas"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于瑕疵履行和补救的一般规则"],
|
||||
"recommended_variants": ["3_month_warranty", "12_month_support"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored maintenance clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_counterparty_authority_rep_v1",
|
||||
"clause_type": "counterparty_authority",
|
||||
"title": "主体资格与授权保证",
|
||||
"text": "各方陈述并保证其系依法成立并有效存续的主体,具有签署、履行本协议及其订单、附件所需的全部权利能力、行为能力和内部授权。签署人应确保已取得法定代表人、董事会、股东会、集团审批或其他必要授权;因主体资格瑕疵、超越权限签约、印章使用不当或授权文件失实导致协议无法履行、被撤销或使对方遭受损失的,违约方应负责补救、赔偿并使守约方免责。",
|
||||
"plain_explanation": "解决签约主体不对、经办人无授权和盖章瑕疵导致的效力风险。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["签约主体与实际履约主体不一致", "经办人无权签约导致合同效力争议"],
|
||||
"negotiation_points": ["是否要求提供授权链文件", "关联公司是否承担共同履约责任"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement",
|
||||
"non_disclosure_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于民事主体、代理和合同效力的一般规则", "《中华人民共和国公司法》关于公司授权和代表行为的一般规则"],
|
||||
"recommended_variants": ["simple_rep", "with_authority_documents"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored authority representation clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_payment_invoice_alignment_v1",
|
||||
"clause_type": "payment_invoice_alignment",
|
||||
"title": "付款节点、对账与开票匹配",
|
||||
"text": "双方应在订单或结算附件中明确每笔费用对应的付款条件、验收节点、对账口径、开票类型、税率和最迟开票时间。除非双方明确约定发票系付款的先决条件,客户不得以内部流程未完成、非关键对账未关闭或部分功能尚未使用为由无正当理由拒绝付款;服务商未按约定提供发票、验收单或结算材料的,客户可在合理范围内暂缓对应款项,待资料补齐后恢复支付。",
|
||||
"plain_explanation": "把付款、对账和开票口径锁定在同一套商业文件中,减少拖款争议。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["付款条件与验收条件脱节", "发票条款被用作无限期拖延付款理由"],
|
||||
"negotiation_points": ["发票是否为付款前提", "对账异议期限和默示确认机制"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于价款支付和协作履行的一般规则", "《中华人民共和国发票管理办法》关于开具和使用发票的一般要求"],
|
||||
"recommended_variants": ["invoice_before_payment", "payment_before_invoice"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored payment and invoicing alignment clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_auto_renewal_notice_v1",
|
||||
"clause_type": "auto_renewal_notice",
|
||||
"title": "自动续期与续约通知",
|
||||
"text": "如订单约定自动续期,双方应明确续期周期、续期价格、异议通知期限、停用窗口和通知方式。任一方拟不续期或调整续期价格、服务范围或计费口径的,应至少于当前期限届满前三十日发送书面通知;未约定清楚续期条件、价格机制或未完成通知的,不得据此主张当然续费、连续锁定多个周期或向对方追收未经确认的新增费用。",
|
||||
"plain_explanation": "防止自动续费条款表述含糊,导致价格和期限争议。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["续费价格未提前通知", "客户误触发多周期自动锁定"],
|
||||
"negotiation_points": ["通知提前期", "续费价格是否允许单方调整"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于意思表示和格式条款提示说明义务的一般规则"],
|
||||
"recommended_variants": ["30_day_notice", "manual_renewal_default"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored auto-renewal notice clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_breach_cure_and_termination_v1",
|
||||
"clause_type": "breach_cure_termination",
|
||||
"title": "违约补救期与解除权",
|
||||
"text": "任一方违反付款、交付、保密、数据安全、知识产权或其他主要义务的,守约方有权发出书面整改通知并给予五至十五个工作日合理补救期;违约方在补救期内未纠正、无法补救或已造成重大损害的,守约方可暂停履行、要求专项保障、解除相关订单或本协议并追究违约责任。对可能持续扩大损失的严重违约,守约方可不经补救期直接采取紧急救济或解除措施。",
|
||||
"plain_explanation": "给解除权设置可执行的补救期,同时保留对重大违约的快速处置权。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["轻微违约被直接解除", "严重违约又缺少及时止损抓手"],
|
||||
"negotiation_points": ["补救期长度", "哪些违约可直接解除"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement",
|
||||
"non_disclosure_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于违约责任、先履行抗辩和合同解除的一般规则"],
|
||||
"recommended_variants": ["cure_10_business_days", "material_breach_immediate_termination"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored breach cure and termination clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_liability_cap_carveout_v1",
|
||||
"clause_type": "liability_cap_carveout",
|
||||
"title": "责任上限例外与间接损失排除",
|
||||
"text": "除双方另有约定外,责任上限不适用于故意或重大过失、侵犯知识产权、违反保密或个人信息保护义务、拖欠到期价款、违法分包以及依法不得限制的法定责任。除前述情形外,任何一方均不对间接损失、可得利益损失、商誉损失、替代采购成本或数据机会损失承担责任,但双方已明确约定的违约金、服务抵扣、返工费用和第三方直接索赔不视为间接损失。",
|
||||
"plain_explanation": "把责任上限条款中的例外和间接损失排除写清,避免后续解释冲突。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["责任上限把故意侵权也一并豁免", "间接损失定义过宽导致直接损失难主张"],
|
||||
"negotiation_points": ["例外责任范围", "第三方索赔是否计入上限"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement",
|
||||
"non_disclosure_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于违约损失、侵权责任和格式条款效力的一般规则"],
|
||||
"recommended_variants": ["broad_carveouts", "narrow_carveouts"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored liability carveout clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_type": "confidentiality_fullstack",
|
||||
"title": "保密信息范围、例外与返还",
|
||||
"text": "保密信息包括披露时标注为保密或按其性质应合理理解为保密的技术、商务、数据、算法、报价、客户信息、日志样本、源代码及谈判信息。下列信息不属保密信息:接收方能证明其在披露前已合法持有、非因违约而公开、从有权第三方合法取得或独立开发形成的信息;接收方因法律法规、监管或司法要求必须披露时,应在法律允许范围内及时通知披露方,并仅披露必要部分。合作结束或披露方要求时,接收方应按约定返还、删除或持续受限保存保密信息及其复制件。",
|
||||
"plain_explanation": "把保密信息的范围、例外、强制披露和返还删除动作一次写全。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["保密范围过窄导致关键资料无法保护", "法定披露和返还删除义务缺失"],
|
||||
"negotiation_points": ["保密期限", "留存备份和审计副本的范围"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement",
|
||||
"non_disclosure_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国反不正当竞争法》商业秘密保护规则", "《中华人民共和国民法典》关于附随义务和信息保护的一般规则"],
|
||||
"recommended_variants": ["mutual_fullstack", "unilateral_customer_data_focus"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored full-stack confidentiality clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_dispute_resolution_operable_v1",
|
||||
"clause_type": "dispute_resolution_operable",
|
||||
"title": "争议解决条款可执行性",
|
||||
"text": "双方应在本协议中明确适用法律、争议解决机构或有管辖权法院、送达地址以及电子证据的可采规则。约定仲裁的,应写明仲裁委员会、仲裁地和仲裁规则;约定诉讼的,应确保选择的法院与争议或当事人具有实际连接点。双方确认通过约定邮箱、系统消息、电子签章平台或快递寄送的通知、日志、订单记录、对账单和电子签署文件,可作为争议解决中的证据材料。",
|
||||
"plain_explanation": "避免争议解决条款因机构不明、管辖无连接点或证据规则缺失而失效。",
|
||||
"risk_level": "medium",
|
||||
"common_risks": ["仲裁机构名称写错", "约定法院无实际连接点导致条款失效"],
|
||||
"negotiation_points": ["诉讼还是仲裁", "电子证据和送达方式是否一并确认"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement",
|
||||
"non_disclosure_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》", "《中华人民共和国民事诉讼法》", "《中华人民共和国仲裁法》"],
|
||||
"recommended_variants": ["court_with_service_address", "arbitration_with_evidence_clause"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored operable dispute resolution clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_type": "service_scope_change_order",
|
||||
"title": "服务范围确认与变更单机制",
|
||||
"text": "双方应在订单、需求说明或项目计划中明确服务边界、交付假设、客户配合义务、外部依赖和不在本次服务范围内的事项。任何新增需求、接口扩展、数据迁移、流程重构、驻场支持、性能指标提升或第三方适配,如可能影响工作量、周期、费用或责任边界,应通过书面变更单确认后执行;变更未获确认前,服务商有权按原范围继续履约并据此调整资源安排。",
|
||||
"plain_explanation": "把范围确认和变更单流程前置,避免项目执行中持续无偿扩容。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["范围未冻结导致持续加项", "客户口头变更后拒绝补价或顺延工期"],
|
||||
"negotiation_points": ["谁有权发起和批准变更", "未签变更单时是否允许暂停相关工作"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于合同内容确定、合同变更和协作履行的一般规则"],
|
||||
"recommended_variants": ["standard_change_order", "time_and_materials_scope"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored service scope and change order clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_termination_and_exit_support_v1",
|
||||
"clause_type": "termination_exit_support",
|
||||
"title": "终止、结算与退出支持",
|
||||
"text": "协议或订单到期、终止或解除后,双方应在约定期限内完成费用结算、账号停用、资料返还、权限回收和未完成事项移交。服务商应在客户付清到期应付款项的前提下,按约定提供合理的退出过渡支持、知识转移、系统交接或替代方案说明;超出基础支持范围的驻场协助、深度迁移、历史数据清洗或第三方协调服务,可另行计费。任何一方在退出阶段仍应持续履行保密、数据保护、知识产权和争议解决等存续条款。",
|
||||
"plain_explanation": "把终止后的结算、交接和持续义务写清,避免退出阶段互相卡住。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["终止后无交接安排导致业务中断", "退出支持范围不明引发额外争议"],
|
||||
"negotiation_points": ["基础退出支持是否免费", "过渡期长度和协助强度"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement"
|
||||
],
|
||||
"industry_tags": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于合同终止后结算、返还和附随义务的一般规则"],
|
||||
"recommended_variants": ["basic_exit_support", "paid_transition_assistance"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored termination and exit support clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_data_export_delete_workflow_v1",
|
||||
"clause_type": "data_export_delete_workflow",
|
||||
"title": "数据导出、删除与交接流程",
|
||||
"text": "协议终止或客户书面要求时,服务商应按照双方约定的格式、介质、接口、校验方式和时限提供数据导出;完成交接并经客户确认或过渡期届满后,服务商应删除或匿名化不再必要的客户数据和个人信息,并保留法律法规、审计或争议处理所必需的最小范围记录。双方应就导出申请、身份核验、样本确认、正式交付、删除确认和异常回退形成可执行流程,避免因口头指令、格式不一致或责任边界不清导致数据无法接收或误删。",
|
||||
"plain_explanation": "把数据导出和删除从原则性承诺落到可执行流程。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["只写可导出但没有格式和时限", "删除动作无确认链导致数据丢失争议"],
|
||||
"negotiation_points": ["导出格式和次数", "删除确认凭证和保留日志范围"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement",
|
||||
"data_processing_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》关于删除、委托处理终止和个人信息处理者义务的规则", "《中华人民共和国数据安全法》关于数据处理安全保障的一般规则"],
|
||||
"recommended_variants": ["export_then_delete", "delete_with_legal_retention"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored data export and deletion workflow clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_sla_operational_metrics_v1",
|
||||
"clause_type": "sla_operational_metrics",
|
||||
"title": "服务级别指标与支持响应",
|
||||
"text": "双方应在订单或SLA附件中明确可用性指标、监测口径、计划维护窗口、故障分级、首次响应时间、恢复目标、升级路径以及未达标时的服务补偿方式。因客户自有系统、第三方依赖、网络运营商、不可抗力、客户违规操作或双方事先确认的计划维护造成的中断,不计入服务级别违约;服务补偿原则上以服务抵扣、延长服务期或专项整改为主,除非双方另有明确约定。",
|
||||
"plain_explanation": "把SLA从口号变成可量化、可取证、可执行的运营条款。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["可用性统计口径不一致", "故障响应时限无法举证"],
|
||||
"negotiation_points": ["赔偿方式是服务抵扣还是现金", "计划维护是否计入不可用时间"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于履行标准、瑕疵补救和违约责任的一般规则"],
|
||||
"recommended_variants": ["monthly_uptime_credit", "ticket_response_only"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored SLA operational metrics clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_change_order_project_v1",
|
||||
"clause_type": "project_change_order",
|
||||
"title": "项目变更单、工期顺延与费用调整",
|
||||
"text": "项目执行过程中,任一方提出需求调整、范围扩展、验收标准提高、第三方系统切换、数据补录、现场支持增加或安全整改要求的,应提交书面变更申请。服务商应在合理期限内说明对交付物、里程碑、工期、资源和费用的影响;经双方确认的变更单自生效之日起成为原合同组成部分,未确认前相关新增工作不视为原价范围内义务,工期亦应据实顺延。",
|
||||
"plain_explanation": "针对项目型合同补足变更单、费用调整和工期顺延三件事。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["变更影响未书面确认", "客户要求先做再谈费用和工期"],
|
||||
"negotiation_points": ["变更评估时限", "紧急变更先执行后补签的条件"],
|
||||
"applicable_contract_types": [
|
||||
"software_development_agreement",
|
||||
"implementation_service_agreement",
|
||||
"saas_service_agreement",
|
||||
"ai_service_agreement"
|
||||
],
|
||||
"industry_tags": ["software", "saas", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于合同变更、价款调整和履行障碍的一般规则"],
|
||||
"recommended_variants": ["formal_change_order", "email_approval_fast_track"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored project change order clause."
|
||||
}
|
||||
},
|
||||
{
|
||||
"clause_id": "clause_cn_subcontracting_and_subprocessor_v1",
|
||||
"clause_type": "subcontracting_subprocessor",
|
||||
"title": "分包、转委托与分处理者管理",
|
||||
"text": "服务商拟将其在本协议项下的部分服务、数据处理活动或运维工作委托给分包商、关联公司或其他分处理者的,应按照订单或附件约定取得客户事先同意或适用的一般授权清单,并保证受托方承担不低于本协议的保密、数据安全、合规和服务标准义务。服务商应对其分包商或分处理者的履约结果承担连带或替代责任;受托方发生重大变更、合规事件或安全事故的,服务商应及时通知客户并采取替换、补救或停用措施。",
|
||||
"plain_explanation": "把普通分包和数据分处理统一纳入审批、通知和责任追溯框架。",
|
||||
"risk_level": "high",
|
||||
"common_risks": ["供应商暗中转包", "分处理者出事后主供应商试图免责"],
|
||||
"negotiation_points": ["是否允许一般性预授权", "重大变更通知期限和客户反对权"],
|
||||
"applicable_contract_types": [
|
||||
"saas_service_agreement",
|
||||
"software_development_agreement",
|
||||
"ai_service_agreement",
|
||||
"implementation_service_agreement",
|
||||
"data_processing_agreement"
|
||||
],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于债务履行辅助人和转委托的一般规则", "《中华人民共和国个人信息保护法》关于受托处理和再委托处理的规则"],
|
||||
"recommended_variants": ["prior_written_consent", "general_authorization_with_objection_right"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored subcontracting and subprocessor clause."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,256 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "contract_templates_cn_saas_v1",
|
||||
"domain": "templates",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Initial official template pack for SaaS, software, NDA, and AI data services with reusable clause references and questionnaire-oriented variables."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"template_id": "tmpl_cn_saas_msa_neutral_001",
|
||||
"template_name": "SaaS主服务协议基础版",
|
||||
"contract_type": "saas_service_agreement",
|
||||
"industry": "saas",
|
||||
"scenario": "标准订阅式SaaS服务,含实施上线、账号开通、SLA、数据处理附件和退出导出安排",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_definitions_order_docs_v1", "required": true},
|
||||
{"clause_id": "clause_cn_parties_and_scope_v1", "required": true, "notes": "明确主协议、订单及关联使用边界。"},
|
||||
{"clause_id": "clause_cn_service_term_and_renewal_v1", "required": true, "variant": "manual_renewal_default"},
|
||||
{"clause_id": "clause_cn_fees_and_invoice_saas_v1", "required": true},
|
||||
{"clause_id": "clause_cn_delivery_implementation_plan_v1", "required": false, "notes": "有实施或联调时启用。"},
|
||||
{"clause_id": "clause_cn_acceptance_saas_objective_v1", "required": true},
|
||||
{"clause_id": "clause_cn_sla_standard_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_processing_dpa_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_incident_notice_v1", "required": true},
|
||||
{"clause_id": "clause_cn_subprocessor_control_v1", "required": false},
|
||||
{"clause_id": "clause_cn_ip_layered_allocation_v1", "required": true},
|
||||
{"clause_id": "clause_cn_confidentiality_mutual_v1", "required": true},
|
||||
{"clause_id": "clause_cn_breach_and_indemnity_general_v1", "required": true},
|
||||
{"clause_id": "clause_cn_liability_cap_service_fees_v1", "required": true},
|
||||
{"clause_id": "clause_cn_dispute_resolution_cn_court_v1", "required": true},
|
||||
{"clause_id": "clause_cn_termination_and_data_export_v1", "required": true},
|
||||
{"clause_id": "clause_cn_third_party_services_dependency_v1", "required": false}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "customer_entity_name", "type": "string", "required": true, "description": "客户签约主体全称"},
|
||||
{"name": "service_modules", "type": "string", "required": true, "description": "购买的产品模块/账号套餐/用量口径"},
|
||||
{"name": "subscription_term_months", "type": "number", "required": true, "description": "首期订阅月数"},
|
||||
{"name": "implementation_required", "type": "boolean", "required": true, "description": "是否包含实施部署、培训或接口联调"},
|
||||
{"name": "acceptance_days", "type": "number", "required": true, "description": "交付或上线后的验收反馈天数"},
|
||||
{"name": "uptime_target", "type": "string", "required": true, "description": "SLA可用性承诺,如99.5%或99.9%"},
|
||||
{"name": "contains_personal_information", "type": "boolean", "required": true, "description": "是否处理个人信息"},
|
||||
{"name": "cross_border_transfer", "type": "boolean", "required": true, "description": "是否涉及跨境传输或境外访问"},
|
||||
{"name": "liability_cap_basis", "type": "enum", "required": true, "description": "赔偿上限基准", "enum_values": ["12_month_fees", "current_order_fees", "custom"]}
|
||||
],
|
||||
"generation_questions": [
|
||||
"客户购买的是标准订阅服务、私有化部署还是混合模式?",
|
||||
"是否需要按阶段实施、里程碑验收或接口联调清单?",
|
||||
"是否处理敏感个人信息、重要数据或客户侧限制出境的数据?",
|
||||
"客户是否要求源代码托管、数据迁移协助或退出过渡期支持?"
|
||||
],
|
||||
"review_rule_ids": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003"
|
||||
],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored formal SaaS template."
|
||||
}
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_dpa_b2b_001",
|
||||
"template_name": "B2B数据处理附件基础版",
|
||||
"contract_type": "data_processing_agreement",
|
||||
"industry": "ai_data_services",
|
||||
"scenario": "作为主服务协议附件使用,明确委托处理、数据安全、分包管理、审计协助与终止删除",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_definitions_order_docs_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_roles_and_instructions_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_categories_and_purposes_v1", "required": true},
|
||||
{"clause_id": "clause_cn_subprocessor_control_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_measures_baseline_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_incident_notice_v1", "required": true},
|
||||
{"clause_id": "clause_cn_audit_and_assistance_v1", "required": true},
|
||||
{"clause_id": "clause_cn_confidentiality_mutual_v1", "required": true},
|
||||
{"clause_id": "clause_cn_liability_cap_service_fees_v1", "required": true},
|
||||
{"clause_id": "clause_cn_return_delete_on_exit_v1", "required": true},
|
||||
{"clause_id": "clause_cn_dispute_resolution_cn_court_v1", "required": true}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "data_categories", "type": "string", "required": true, "description": "数据类别、字段范围与是否包含敏感个人信息"},
|
||||
{"name": "processing_purpose", "type": "string", "required": true, "description": "处理目的与业务功能"},
|
||||
{"name": "subprocessors_allowed", "type": "boolean", "required": true, "description": "是否允许子处理者"},
|
||||
{"name": "incident_notice_hours", "type": "number", "required": true, "description": "安全事件通知时限(小时)"},
|
||||
{"name": "return_or_delete_mode", "type": "enum", "required": true, "description": "终止后数据处置方式", "enum_values": ["return_then_delete", "delete_only", "customer_choice"]},
|
||||
{"name": "cross_border_transfer", "type": "boolean", "required": true, "description": "是否涉及跨境提供或境外访问"}
|
||||
],
|
||||
"generation_questions": [
|
||||
"哪些数据由客户控制、哪些数据由服务商独立决定处理?",
|
||||
"是否允许使用第三方云、短信、OCR、模型服务等子处理者?",
|
||||
"终止合作后,客户需要何种格式和时限的数据导出支持?",
|
||||
"是否涉及重要数据、敏感个人信息或境外访问权限?"
|
||||
],
|
||||
"review_rule_ids": [
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003"
|
||||
],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored formal DPA attachment template."
|
||||
}
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_software_dev_basic_001",
|
||||
"template_name": "软件开发合同基础版",
|
||||
"contract_type": "software_development_agreement",
|
||||
"industry": "software",
|
||||
"scenario": "定制开发、接口开发、轻量实施一体的基础软件开发合同,强调交付清单、变更控制与验收",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_definitions_order_docs_v1", "required": true},
|
||||
{"clause_id": "clause_cn_parties_and_scope_v1", "required": true},
|
||||
{"clause_id": "clause_cn_fees_and_invoice_saas_v1", "required": true, "notes": "开发费按里程碑/阶段支付时适用。"},
|
||||
{"clause_id": "clause_cn_delivery_implementation_plan_v1", "required": true},
|
||||
{"clause_id": "clause_cn_software_dev_deliverables_and_change_control_v1", "required": true},
|
||||
{"clause_id": "clause_cn_acceptance_saas_objective_v1", "required": true, "notes": "复用客观验收标准以兼容现有审查规则。"},
|
||||
{"clause_id": "clause_cn_maintenance_support_post_acceptance_v1", "required": true},
|
||||
{"clause_id": "clause_cn_ip_layered_allocation_v1", "required": true},
|
||||
{"clause_id": "clause_cn_confidentiality_mutual_v1", "required": true},
|
||||
{"clause_id": "clause_cn_breach_and_indemnity_general_v1", "required": true},
|
||||
{"clause_id": "clause_cn_liability_cap_service_fees_v1", "required": true},
|
||||
{"clause_id": "clause_cn_dispute_resolution_cn_court_v1", "required": true},
|
||||
{"clause_id": "clause_cn_third_party_services_dependency_v1", "required": false}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "project_name", "type": "string", "required": true, "description": "项目名称"},
|
||||
{"name": "delivery_mode", "type": "enum", "required": true, "description": "交付形态", "enum_values": ["source_code", "binary_only", "hosted_plus_customization"]},
|
||||
{"name": "milestone_count", "type": "number", "required": true, "description": "里程碑数量"},
|
||||
{"name": "acceptance_days", "type": "number", "required": true, "description": "每阶段验收反馈天数"},
|
||||
{"name": "warranty_months", "type": "number", "required": true, "description": "维保月数"},
|
||||
{"name": "customer_owned_custom_deliverables", "type": "boolean", "required": true, "description": "客户是否取得定制交付物所有权"}
|
||||
],
|
||||
"generation_questions": [
|
||||
"交付的是源代码、目标代码,还是基于现有平台的定制配置?",
|
||||
"是否存在第三方系统、云资源或开源组件依赖?",
|
||||
"需求变更由谁审批,是否需要单独签署变更单?",
|
||||
"客户主张的成果归属是否会触及服务商预存平台或通用能力?"
|
||||
],
|
||||
"review_rule_ids": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_saas_ip_output_003"
|
||||
],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored software development baseline template."
|
||||
}
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_nda_mutual_basic_001",
|
||||
"template_name": "保密协议基础版",
|
||||
"contract_type": "non_disclosure_agreement",
|
||||
"industry": "software",
|
||||
"scenario": "商务接洽、POC、项目评估和数据对接前的双向保密协议基础版",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_definitions_order_docs_v1", "required": true},
|
||||
{"clause_id": "clause_cn_confidentiality_mutual_v1", "required": true},
|
||||
{"clause_id": "clause_cn_breach_and_indemnity_general_v1", "required": true},
|
||||
{"clause_id": "clause_cn_liability_cap_service_fees_v1", "required": false, "notes": "如需设置责任上限时启用;对商业秘密泄露也可改为不设上限。"},
|
||||
{"clause_id": "clause_cn_dispute_resolution_cn_court_v1", "required": true}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "disclosing_scenarios", "type": "string", "required": true, "description": "信息披露场景,如商务洽谈/POC/项目评估"},
|
||||
{"name": "confidentiality_term_years", "type": "number", "required": true, "description": "一般保密期限(年)"},
|
||||
{"name": "residual_knowledge_allowed", "type": "boolean", "required": true, "description": "是否允许残余知识使用"},
|
||||
{"name": "injunctive_relief_needed", "type": "boolean", "required": true, "description": "是否强调可申请禁令或行为保全"}
|
||||
],
|
||||
"generation_questions": [
|
||||
"披露内容是否涉及源代码、模型参数、客户名单或价格政策?",
|
||||
"是否允许员工基于残余记忆形成一般经验使用?",
|
||||
"双方是否需要对样品、测试账号、演示环境也纳入保密范围?"
|
||||
],
|
||||
"review_rule_ids": [
|
||||
"rule_cn_saas_ip_output_003"
|
||||
],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored NDA baseline template."
|
||||
}
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_ai_data_service_basic_001",
|
||||
"template_name": "AI数据服务协议基础版",
|
||||
"contract_type": "ai_service_agreement",
|
||||
"industry": "ai_data_services",
|
||||
"scenario": "数据清洗、标注、抽取、评测、模型调用编排或行业知识库服务的基础协议",
|
||||
"jurisdiction": "CN",
|
||||
"version": "v1",
|
||||
"stance": "neutral",
|
||||
"clauses": [
|
||||
{"clause_id": "clause_cn_definitions_order_docs_v1", "required": true},
|
||||
{"clause_id": "clause_cn_parties_and_scope_v1", "required": true},
|
||||
{"clause_id": "clause_cn_service_term_and_renewal_v1", "required": true},
|
||||
{"clause_id": "clause_cn_fees_and_invoice_saas_v1", "required": true},
|
||||
{"clause_id": "clause_cn_delivery_implementation_plan_v1", "required": true},
|
||||
{"clause_id": "clause_cn_acceptance_saas_objective_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_processing_dpa_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_roles_and_instructions_v1", "required": true},
|
||||
{"clause_id": "clause_cn_data_categories_and_purposes_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_measures_baseline_v1", "required": true},
|
||||
{"clause_id": "clause_cn_security_incident_notice_v1", "required": true},
|
||||
{"clause_id": "clause_cn_subprocessor_control_v1", "required": true},
|
||||
{"clause_id": "clause_cn_ip_layered_allocation_v1", "required": true},
|
||||
{"clause_id": "clause_cn_confidentiality_mutual_v1", "required": true},
|
||||
{"clause_id": "clause_cn_breach_and_indemnity_general_v1", "required": true},
|
||||
{"clause_id": "clause_cn_liability_cap_service_fees_v1", "required": true},
|
||||
{"clause_id": "clause_cn_return_delete_on_exit_v1", "required": true},
|
||||
{"clause_id": "clause_cn_third_party_services_dependency_v1", "required": true},
|
||||
{"clause_id": "clause_cn_dispute_resolution_cn_court_v1", "required": true}
|
||||
],
|
||||
"variables": [
|
||||
{"name": "service_type", "type": "enum", "required": true, "description": "AI/数据服务类型", "enum_values": ["data_labeling", "data_cleaning", "knowledge_base", "model_orchestration", "evaluation_service"]},
|
||||
{"name": "training_data_included", "type": "boolean", "required": true, "description": "是否涉及训练样本或微调数据"},
|
||||
{"name": "customer_data_sensitivity", "type": "enum", "required": true, "description": "数据敏感程度", "enum_values": ["general", "personal_information", "sensitive_personal_information", "important_data"]},
|
||||
{"name": "third_party_model_dependency", "type": "boolean", "required": true, "description": "是否依赖第三方基础模型或云能力"},
|
||||
{"name": "output_ip_mode", "type": "enum", "required": true, "description": "成果使用权模式", "enum_values": ["customer_use_license", "customer_ownership_for_custom_outputs", "shared_use_with_vendor_retained_platform_ip"]},
|
||||
{"name": "incident_notice_hours", "type": "number", "required": true, "description": "安全事件通知时限(小时)"}
|
||||
],
|
||||
"generation_questions": [
|
||||
"服务结果是数据加工输出、知识库、流程编排还是模型调用能力?",
|
||||
"是否允许服务商使用匿名化统计或非可识别样本优化产品?",
|
||||
"是否存在第三方模型、OCR、云资源、短信或地图能力依赖?",
|
||||
"客户是否要求对训练数据、输出结果、提示词或标签体系主张排他权利?"
|
||||
],
|
||||
"review_rule_ids": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003"
|
||||
],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored AI data service baseline template."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,285 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "faq_cn_data_compliance_v1",
|
||||
"domain": "faq",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Publishable PRC data compliance and commercial contracting FAQ package for SaaS, software development, and AI/data service transactions."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"faq_id": "faq_cn_data_001",
|
||||
"question": "SaaS合同里只写“服务商应保障数据安全”为什么不够?",
|
||||
"short_answer": "因为这类表述只有原则,没有分工、范围、时限和补救机制,发生事故时很难据此判断谁负责、怎么配合、赔多少。",
|
||||
"long_answer": "一份可执行的数据安全条款至少应回答五件事:处理什么数据、各方是什么角色、采取哪些最低安全措施、发生事件后多久通知、合作终止后数据如何返还或删除。如果合同只有“保障数据安全”之类的笼统义务,服务商可能无法判断合规基线,客户也无法要求具体整改;一旦发生泄露、误删或接口滥用,双方会在通知时点、日志保留、第三方配合和损失承担上产生争议。对B2B SaaS而言,建议以单独的数据处理附件承载这些内容。",
|
||||
"topic_tags": ["data_security", "contract_review", "saas"],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》委托处理相关规则", "《中华人民共和国数据安全法》数据安全管理义务"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_002",
|
||||
"question": "客户要求“项目产生的所有成果、数据、代码均归甲方所有”时,SaaS服务商最该先审什么?",
|
||||
"short_answer": "先审归属对象有没有分层:客户数据、定制成果、预存平台、底层代码、模型能力、第三方组件不能一概而论。",
|
||||
"long_answer": "这类条款常把不同层级的资产打包处理,表面上简洁,实务上风险极高。SaaS服务商至少要把五类对象拆开:一是客户上传和业务运行形成的数据;二是为客户定制的报表、配置、接口或文档;三是服务商原有平台、底层代码、算法模型和通用组件;四是第三方软件或开源依赖;五是基于匿名化统计形成的运营洞察。如果不分层,客户可能主张取得服务商核心平台或模型相关权益,服务商则可能因保留条款过宽而无法满足客户的数据迁移和持续使用诉求。更稳妥的做法是:客户数据归客户,服务商预存IP归服务商,定制成果按项目性质单独约定所有权或使用许可。",
|
||||
"topic_tags": ["ip", "saas", "drafting"],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国著作权法》软件及作品权利归属基本规则", "《中华人民共和国民法典》合同解释与履行规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_003",
|
||||
"question": "为什么SaaS实施项目要单独约定验收,不适合只靠“上线即完成交付”?",
|
||||
"short_answer": "因为上线不等于功能稳定、接口可用或培训完成;没有验收结构,价款支付、维保起算和违约认定都会失去客观锚点。",
|
||||
"long_answer": "很多SaaS或软件实施争议并不是“有没有上线”,而是“上线后能不能按约使用”。如果合同只写上线即交付完成,客户容易在后续以功能不达标为由拒付,服务商则会主张系统已开通、义务已履行,双方都缺乏清晰证据。更合理的设计是将交付、试运行、正式验收拆分开,分别明确测试环境、接口联调、关键缺陷定义、整改轮次、反馈期限和逾期推定规则。这样既能防止客户无限期拖延验收,也能避免服务商在重大缺陷未修复时过早触发收款。",
|
||||
"topic_tags": ["acceptance", "payment", "implementation"],
|
||||
"industry_tags": ["saas", "software"],
|
||||
"linked_rule_ids": ["rule_cn_saas_acceptance_001"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》关于全面履行、协作履行与违约责任的一般规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_004",
|
||||
"question": "客户把含有个人信息的业务数据交给SaaS服务商时,合同中为什么要先写清双方角色?",
|
||||
"short_answer": "因为角色决定义务边界:谁决定处理目的和方式、谁负责取得授权、谁应回应个人权利请求,不能仅靠业务习惯默认为服务商全包。",
|
||||
"long_answer": "在多数企业采购场景中,客户通常决定业务目的、字段范围和使用方式,服务商主要按指示提供存储、计算、接口或运维,因此常见结构是客户作为个人信息处理规则的主导方,服务商作为受托处理方承担受托范围内义务。但如果服务商会将数据用于独立建模、画像优化、联合分析或其他超出客户指示的目的,就可能不再只是单纯受托处理。合同应写明处理目的、处理方式、字段类别、权限控制、指令变更流程及超范围处理限制,否则一旦发生投诉或检查,双方容易互相推责。",
|
||||
"topic_tags": ["personal_information", "data_processing", "role_allocation"],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》委托处理与个人信息处理者义务", "《中华人民共和国民法典》协作履行规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_005",
|
||||
"question": "AI或数据服务合同里,服务商能否直接把客户数据用于模型训练或产品优化?",
|
||||
"short_answer": "不能默认直接使用,必须先看合同授权、数据类型、是否涉及个人信息或商业秘密,以及是否采取了足够的去标识化或匿名化安排。",
|
||||
"long_answer": "“用于改进服务”不是当然合法的万能口径。若客户数据包含个人信息、受监管业务数据、源代码、模型提示词、交易数据或其他敏感商业信息,服务商若要用于训练、微调、评估或通用产品优化,至少应单独约定用途、范围、技术措施、样本保留周期、退出机制和成果边界。实务上更稳妥的写法是分层授权:默认仅为履约处理;如需改进模型或产品,应另行取得明确授权,并约定不得反向识别客户、不得暴露客户专有知识、不得使客户数据在其他客户侧可还原。",
|
||||
"topic_tags": ["ai_training", "data_use", "confidentiality"],
|
||||
"industry_tags": ["ai_data_services", "saas", "software"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002", "rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》处理目的和最小必要原则", "《中华人民共和国反不正当竞争法》商业秘密保护规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_006",
|
||||
"question": "客户要求服务商承诺“绝对不出安全事件”是否合理?",
|
||||
"short_answer": "通常不合理。更可执行的做法是约定安全基线、事件分级、通知时限、补救措施和责任划分,而不是要求结果上绝对零风险。",
|
||||
"long_answer": "网络与数据安全义务一般应以“采取与服务性质相匹配的合理、适当、持续的管理和技术措施”为核心,而不是简单承诺绝对结果。若服务商承诺“绝不泄露、绝不宕机、绝不丢失”,在复杂的云环境、第三方依赖和客户侧配置参与下,极易形成失衡责任。建议将承诺改为:建立访问控制、加密、备份、日志、漏洞修复和人员权限管理等基线;定义重大事件、一般事件及其通报时点;对因客户配置错误、弱口令、违规导入第三方数据等因素造成的风险做责任切分。",
|
||||
"topic_tags": ["data_security", "liability", "risk_allocation"],
|
||||
"industry_tags": ["saas", "ai_data_services", "software"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国数据安全法》数据安全保护义务", "《中华人民共和国网络安全法》网络运行安全一般规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_007",
|
||||
"question": "SaaS合同中的数据删除和返还条款,最低应写到什么程度?",
|
||||
"short_answer": "至少要写清返还对象、导出格式、申请窗口、交付方式、备份保留期、删除完成标准和例外留存依据。",
|
||||
"long_answer": "终止后的数据处置是高频争议点。若合同只写“合作结束后删除数据”,客户会担心无法迁移,服务商则可能认为只需停用账号。建议明确:一是客户有权导出的数据范围,包括主数据、操作日志、报表、附件和接口数据;二是导出格式、次数、费用和技术协助边界;三是服务终止后保留导出窗口;四是生产环境与备份环境的删除节奏;五是因法定义务、审计留痕或争议处理需要而例外保留的数据范围及期限。这样才能兼顾客户可迁移性和服务商合规留痕需求。",
|
||||
"topic_tags": ["data_return", "data_deletion", "exit_management"],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》删除与受托处理终止相关规则", "《中华人民共和国数据安全法》数据全生命周期管理要求"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_008",
|
||||
"question": "服务商使用云厂商、短信商、OCR服务或大模型接口时,合同里为什么要写子处理者和第三方依赖?",
|
||||
"short_answer": "因为客户实际关心的不只是主合同相对方,还包括谁会接触其数据、数据会流向哪里,以及第三方出问题时谁负责协调与赔付。",
|
||||
"long_answer": "很多数据和AI服务并非完全由主服务商自建完成,而是依赖云主机、对象存储、CDN、消息推送、语音识别、支付接口或基础模型能力。若合同不披露或不约束这些子处理者、分包商和关键第三方,客户很难评估真实风险。较稳妥的安排包括:要求服务商对关键子处理者类别进行告知;承诺其对第三方履约承担管理责任;限制第三方超范围使用客户数据;在更换关键第三方时履行通知义务;对跨境传输、日志存储地域和应急协助作专门约定。",
|
||||
"topic_tags": ["subprocessor", "vendor_management", "ai_services"],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》受托处理与再委托管理规则", "《中华人民共和国民法典》辅助履行与违约责任规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_009",
|
||||
"question": "软件定制和SaaS混合项目里,客户为什么应避免把“验收通过后再支付全部价款”写成唯一付款条件?",
|
||||
"short_answer": "因为混合项目通常包含订阅、实施、开发、接口联调和培训等不同价值节点,全部压到最终验收会放大现金流和争议风险。",
|
||||
"long_answer": "在SaaS加实施或定制开发的项目中,服务商往往在前期已投入大量配置、研发、人力和第三方资源。如果全部价款都与最终验收绑定,一旦客户内部流程拖延、需求频繁变更或接口依赖未完成,双方会陷入“服务商已投入但无法收款、客户未完全可用也不愿付款”的僵局。更常见也更稳妥的设计是:订阅费按服务期开通收取,实施费按里程碑结算,定制开发费按阶段交付和验收挂钩,尾款比例保持可控,并辅以逾期反馈视为阶段确认的规则。",
|
||||
"topic_tags": ["payment", "acceptance", "project_management"],
|
||||
"industry_tags": ["saas", "software"],
|
||||
"linked_rule_ids": ["rule_cn_saas_acceptance_001"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》有偿合同履行与价款支付规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_010",
|
||||
"question": "自动续约条款为什么经常在企业软件采购中引发争议?",
|
||||
"short_answer": "因为很多合同只写“到期自动续约”,却没写提前通知期限、续约价格机制、功能变更影响和停用后数据安排。",
|
||||
"long_answer": "自动续约本身并非当然无效,但如果条款隐藏在订单或通用条款中,且没有清楚说明续约周期、通知节点、续费价格和终止后果,极易在到期前后发生争议。对客户而言,风险在于预算未批、业务已变更却被主张继续扣费;对服务商而言,若没有明确的通知和确认证据,也难以证明客户同意续费。更可执行的做法是:写明自动续约适用前提、提前通知期限、续费价格的确定方式、客户在通知期内的退出权,以及未续约时的数据导出和账号停用安排。",
|
||||
"topic_tags": ["auto_renewal", "payment", "termination"],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》格式条款提示说明义务与合同履行规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_011",
|
||||
"question": "客户要求“开票后90天付款”或者“以客户回款为付款前提”时,服务商应重点防什么?",
|
||||
"short_answer": "重点防止把付款义务无限后移,尤其是将内部审批、最终客户回款或形式性票据瑕疵变成拒付理由。",
|
||||
"long_answer": "在企业软件交易中,开票、验收和付款经常被捆绑使用。服务商需要区分:开票是税务和结算动作,不应当然等于重新启动超长账期;客户内部审批或其下游客户未回款,通常也不应当然转嫁给服务商。较平衡的条款是明确付款起算点、发票类型与开票时间、票据瑕疵的补正机制,以及客户不得以其内部流程或第三方回款为由无期限拖延付款。若客户确实要求较长账期,服务商应同步评估价格、停服权、逾期违约金和分期交付安排。",
|
||||
"topic_tags": ["invoicing", "payment", "accounts_receivable"],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_acceptance_001"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》价款支付与违约责任规则", "《保障中小企业款项支付条例》相关支付导向规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_012",
|
||||
"question": "AI服务合同里的“输出结果知识产权归谁”为什么不能一句话解决?",
|
||||
"short_answer": "因为输出结果可能同时受输入数据来源、模型底座、人工加工程度、第三方素材限制和合同目的影响,简单“一刀切”往往不可执行。",
|
||||
"long_answer": "AI输出通常不是单一类型资产。有的只是机器生成文本草稿,有的是客户基于其专有数据和业务规则反复迭代后的专属成果,还有的会混入第三方版权素材、模板库、预训练能力或服务商原有方法论。合同至少应拆分四层:客户输入及其权利归属、服务商模型和平台能力的保留、面向客户交付的输出使用权或归属安排、以及第三方限制和侵权处理机制。对于高价值项目,建议同时写明服务商是否保留将输出用于模型再训练、案例展示或通用能力沉淀的权利。",
|
||||
"topic_tags": ["ai_output", "ip", "licensing"],
|
||||
"industry_tags": ["ai_data_services", "software", "saas"],
|
||||
"linked_rule_ids": ["rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国著作权法》作品权利归属基本规则", "《中华人民共和国民法典》合同约定优先与解释规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_013",
|
||||
"question": "客户要求源代码托管或交付Escrow时,哪些情形更值得考虑接受?",
|
||||
"short_answer": "通常在高度定制、强依赖单一供应商、客户业务连续性要求高且支付规模较大时,更适合讨论有限触发条件下的源码托管。",
|
||||
"long_answer": "源码托管并不等于客户立即取得全部底层代码。对服务商而言,风险是核心资产外泄;对客户而言,担忧是服务商停业、严重违约或长期无法维护。较平衡的安排通常包括:仅托管项目相关定制代码和必要部署文档;预存平台、通用组件和第三方受限代码不当然纳入;只有在服务商破产、停止维护、重大违约且在合理期限内未补救等触发条件出现时,客户才可取得受限使用权。这样既照顾业务连续性,也避免客户借托管实质性取得服务商核心平台。",
|
||||
"topic_tags": ["source_code", "business_continuity", "ip"],
|
||||
"industry_tags": ["software", "saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国著作权法》软件权利归属规则", "《中华人民共和国民法典》附条件权利安排与违约补救规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_014",
|
||||
"question": "争议解决条款里,为什么企业软件合同不宜只写“协商不成提交有管辖权法院”?",
|
||||
"short_answer": "因为这类表述看似完整,实务上却可能导致管辖地不明确、证据保全不便、技术争议处理周期长。",
|
||||
"long_answer": "SaaS、软件开发和数据服务争议往往涉及电子证据、日志、接口调用记录、版本迭代文档和跨地区履行事实。若合同没有明确争议解决地和适用程序,一旦发生停服、源码交付、数据返还或费用结算争议,诉讼前的证据固定和禁令需求会很麻烦。实务上应根据交易规模和执行需求选择仲裁或诉讼,并尽量明确仲裁机构或管辖法院所在地。同时可补充紧急救济、保密义务持续适用、电子证据效力和服务不中断的临时安排。",
|
||||
"topic_tags": ["dispute_resolution", "evidence", "contract_drafting"],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_acceptance_001", "rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国民事诉讼法》管辖与电子数据证据规则", "《中华人民共和国仲裁法》仲裁约定一般规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_015",
|
||||
"question": "违约责任条款里把服务商责任上限写成“已收取费用总额”是否总是合理?",
|
||||
"short_answer": "不总是合理,要看违约类型、数据风险级别、项目金额结构以及是否对故意、重大过失、保密和知识产权侵权作了例外。",
|
||||
"long_answer": "责任上限的核心不是越高越好或越低越好,而是是否与风险结构匹配。对于一般性的延迟交付、轻微SLA不达标或可修复缺陷,设定与近12个月已付费用挂钩的责任上限较常见;但若涉及故意违法、重大过失、恶意泄密、未经授权使用客户数据、知识产权侵权或人身财产损害,通常不宜被同一上限完全覆盖。客户若坚持高风险例外,服务商则应同步限定损失类型、因果关系和减损义务,避免出现远超交易对价的不可控暴露。",
|
||||
"topic_tags": ["liability_cap", "breach", "risk_allocation"],
|
||||
"industry_tags": ["saas", "software", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002", "rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国民法典》违约责任与损失赔偿规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_016",
|
||||
"question": "开源组件、第三方模型或数据集被嵌入交付物时,合同里应如何处理知识产权和合规风险?",
|
||||
"short_answer": "应明确第三方成分清单、适用许可、使用限制、替换机制和侵权应对,而不是笼统承诺“全部成果完全无权利瑕疵”。",
|
||||
"long_answer": "在现代软件和AI项目中,完全不依赖第三方资源并不现实。问题不在于是否使用,而在于是否透明和可控。合同至少应覆盖:交付物中是否包含开源组件、商用SDK、预训练模型、外部数据集或素材库;这些要素分别适用什么许可;客户是否需要额外遵守署名、开源披露或不得再分发等条件;若关键依赖许可变化、下架或产生侵权争议,服务商是否负责替换、绕行或提供替代方案。这样既能保护客户的持续使用权,也能避免服务商承担无法实现的绝对担保。",
|
||||
"topic_tags": ["open_source", "third_party_ip", "ai_models"],
|
||||
"industry_tags": ["software", "ai_data_services", "saas"],
|
||||
"linked_rule_ids": ["rule_cn_saas_ip_output_003"],
|
||||
"linked_law_refs": ["《中华人民共和国著作权法》软件和作品权利规则", "《中华人民共和国民法典》瑕疵担保与违约责任规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_017",
|
||||
"question": "跨境访问或境外云资源参与服务时,为什么不能只在合同里写“数据存储在国内”?",
|
||||
"short_answer": "因为是否发生跨境流动,不只看主库物理位置,还要看远程访问、备份、运维支持、日志同步和第三方接口调用路径。",
|
||||
"long_answer": "很多合同把“服务器在国内”当成全部合规答案,但实务上数据流动链路更复杂。若境外团队可远程访问生产数据、日志会同步到境外监控系统、备份容灾在境外、或AI推理请求被发送到境外模型接口,都可能触发额外的合规评估和客户关注。合同应至少披露数据存储地域、跨境访问场景、远程运维权限、子处理者所在地区及替代方案,并约定未经客户同意不得擅自改变关键数据路径。对高敏感行业客户,还应支持本地化部署、专有云或跨境功能关闭选项。",
|
||||
"topic_tags": ["cross_border_data", "cloud", "data_localization"],
|
||||
"industry_tags": ["saas", "ai_data_services"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》个人信息跨境提供规则", "《中华人民共和国数据安全法》重要数据安全管理要求"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
},
|
||||
{
|
||||
"faq_id": "faq_cn_data_018",
|
||||
"question": "客户发现服务商疑似超范围处理数据时,合同上最有用的救济机制是什么?",
|
||||
"short_answer": "最有用的通常不是事后空泛索赔,而是能立即启动的暂停处理、审计配合、证据保全、整改时限和数据隔离机制。",
|
||||
"long_answer": "超范围处理的风险在于损害会持续扩大,如果合同只保留事后追责,客户往往很难及时止损。较实用的条款组合包括:客户有权发出书面整改通知并要求服务商在限定时间内说明处理依据;在重大疑点下可暂停特定接口、导出或训练活动;服务商应保留关键日志并配合独立审计或双方认可的第三方核查;若确认构成超范围处理,应执行删除、隔离、返还、补充通知和内部纠偏。对服务商而言,也应要求审计范围合理、不得接触其他客户信息,并保护其商业秘密和系统安全。",
|
||||
"topic_tags": ["audit_rights", "data_governance", "breach_response"],
|
||||
"industry_tags": ["saas", "ai_data_services", "software"],
|
||||
"linked_rule_ids": ["rule_cn_saas_data_scope_002", "rule_cn_saas_acceptance_001"],
|
||||
"linked_law_refs": ["《中华人民共和国个人信息保护法》受托处理监督与违法处理责任规则", "《中华人民共和国民法典》违约补救与协作履行规则"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored FAQ package."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,129 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "industry_ai_data_services_cn_v1",
|
||||
"domain": "industry_pack",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "hybrid_compilation",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Draft AI/data services industry pack linking current data compliance, contract review, and template assets."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"pack_id": "industry_pack_cn_ai_data_services_001",
|
||||
"pack_name": "AI/数据服务行业法务包",
|
||||
"industry": "ai_data_services",
|
||||
"summary": "覆盖数据清洗、标注、抽取、评测、知识库编排和模型服务场景,重点控制委托处理、数据用途、输出归属和退出删除风险。",
|
||||
"common_contract_types": [
|
||||
"AI服务协议",
|
||||
"数据处理附件",
|
||||
"保密协议",
|
||||
"实施服务协议"
|
||||
],
|
||||
"regulatory_focus": [
|
||||
"个人信息委托处理与指令边界",
|
||||
"训练、评测和样本复用授权",
|
||||
"分处理者和基础模型供应商管理",
|
||||
"安全事件通知、审计协助和留痕",
|
||||
"导出、删除、匿名化和跨境安排"
|
||||
],
|
||||
"common_disputes": [
|
||||
"服务商超出约定用途使用客户数据",
|
||||
"模型输出知识产权和许可范围不清",
|
||||
"分处理者未披露或云资源链条失控",
|
||||
"安全事件通知迟延或处置留痕不足",
|
||||
"合作终止后数据未及时删除或交接不完整"
|
||||
],
|
||||
"must_review_clause_ids": [
|
||||
"clause_cn_data_processing_dpa_v1",
|
||||
"clause_cn_data_roles_and_instructions_v1",
|
||||
"clause_cn_data_categories_and_purposes_v1",
|
||||
"clause_cn_security_measures_baseline_v1",
|
||||
"clause_cn_security_incident_notice_v1",
|
||||
"clause_cn_subcontracting_and_subprocessor_v1",
|
||||
"clause_cn_data_export_delete_workflow_v1",
|
||||
"clause_cn_liability_cap_carveout_v1"
|
||||
],
|
||||
"high_risk_expressions": [
|
||||
"服务商可自行决定任何数据用途",
|
||||
"模型输出默认完全归服务商所有且不可撤回",
|
||||
"任何再委托无需通知客户",
|
||||
"合作结束后数据是否删除由服务商自行决定"
|
||||
],
|
||||
"glossary_terms": [
|
||||
"委托处理",
|
||||
"处理指令",
|
||||
"分处理者",
|
||||
"训练样本",
|
||||
"删除确认"
|
||||
],
|
||||
"required_attachment_checklist": [
|
||||
"数据处理附件",
|
||||
"数据字段/样本清单",
|
||||
"安全措施基线清单",
|
||||
"分处理者名录",
|
||||
"安全事件响应流程",
|
||||
"导出删除交接单"
|
||||
],
|
||||
"source_registry_ids": [
|
||||
"src_cn_cac",
|
||||
"src_cn_npc_lawdb",
|
||||
"src_internal_authored"
|
||||
],
|
||||
"rule_ids": [
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003",
|
||||
"rule_cn_payment_invoice_005",
|
||||
"rule_cn_auto_renewal_006",
|
||||
"rule_cn_liability_cap_008",
|
||||
"rule_cn_confidentiality_009",
|
||||
"rule_cn_service_scope_011",
|
||||
"rule_cn_termination_exit_012",
|
||||
"rule_cn_data_export_delete_013",
|
||||
"rule_cn_sla_support_014",
|
||||
"rule_cn_subcontracting_016"
|
||||
],
|
||||
"clause_ids": [
|
||||
"clause_cn_parties_and_scope_v1",
|
||||
"clause_cn_service_term_and_renewal_v1",
|
||||
"clause_cn_fees_and_invoice_saas_v1",
|
||||
"clause_cn_data_processing_dpa_v1",
|
||||
"clause_cn_data_roles_and_instructions_v1",
|
||||
"clause_cn_data_categories_and_purposes_v1",
|
||||
"clause_cn_security_measures_baseline_v1",
|
||||
"clause_cn_security_incident_notice_v1",
|
||||
"clause_cn_audit_and_assistance_v1",
|
||||
"clause_cn_subprocessor_control_v1",
|
||||
"clause_cn_subcontracting_and_subprocessor_v1",
|
||||
"clause_cn_ip_layered_allocation_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_data_export_delete_workflow_v1",
|
||||
"clause_cn_termination_and_exit_support_v1",
|
||||
"clause_cn_third_party_services_dependency_v1",
|
||||
"clause_cn_dispute_resolution_operable_v1"
|
||||
],
|
||||
"template_ids": [
|
||||
"tmpl_cn_ai_data_service_basic_001",
|
||||
"tmpl_cn_dpa_b2b_001",
|
||||
"tmpl_cn_nda_mutual_basic_001"
|
||||
],
|
||||
"faq_ids": [
|
||||
"faq_cn_data_004",
|
||||
"faq_cn_data_005",
|
||||
"faq_cn_data_006",
|
||||
"faq_cn_data_007",
|
||||
"faq_cn_data_008",
|
||||
"faq_cn_data_012",
|
||||
"faq_cn_data_017",
|
||||
"faq_cn_data_018"
|
||||
],
|
||||
"draft_gaps": [
|
||||
"尚缺AI输出侵权索赔的专门FAQ",
|
||||
"尚缺行业化的跨境调用和模型供应商尽调清单"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,118 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "industry_ecommerce_operations_cn_v1",
|
||||
"domain": "industry_pack",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "hybrid_compilation",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Draft ecommerce/operations industry pack using current general contract assets as the initial legal bundle."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"pack_id": "industry_pack_cn_ecommerce_operations_001",
|
||||
"pack_name": "电商/代运营行业法务包",
|
||||
"industry": "ecommerce_operations",
|
||||
"summary": "覆盖店铺代运营、广告投放、活动策划、内容分发和平台对接场景,现阶段以通用服务条款和FAQ拼装首版草案。",
|
||||
"common_contract_types": [
|
||||
"电商代运营服务协议",
|
||||
"营销推广与广告投放协议",
|
||||
"平台店铺托管协议",
|
||||
"保密协议"
|
||||
],
|
||||
"regulatory_focus": [
|
||||
"宣传用语、促销和平台运营规则合规",
|
||||
"店铺账号、素材和客户数据的控制权分配",
|
||||
"推广费、返点和代采资源结算",
|
||||
"客服、售后和投诉协同责任边界",
|
||||
"第三方投放渠道和外包团队管理"
|
||||
],
|
||||
"common_disputes": [
|
||||
"GMV或ROI未达预期引发违约争议",
|
||||
"店铺账号和素材交接不完整",
|
||||
"平台处罚责任由谁承担不明确",
|
||||
"推广费用、返佣和代采成本对账争议",
|
||||
"终止后客户数据和运营权限回收不彻底"
|
||||
],
|
||||
"must_review_clause_ids": [
|
||||
"clause_cn_counterparty_authority_rep_v1",
|
||||
"clause_cn_payment_invoice_alignment_v1",
|
||||
"clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_breach_cure_and_termination_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_dispute_resolution_operable_v1",
|
||||
"clause_cn_termination_and_exit_support_v1"
|
||||
],
|
||||
"high_risk_expressions": [
|
||||
"保证店铺销量、排名或投放效果",
|
||||
"平台处罚和违规责任全部由服务商承担",
|
||||
"客户随时新增活动需求且费用不变",
|
||||
"店铺账号、粉丝和素材默认归服务商使用"
|
||||
],
|
||||
"glossary_terms": [
|
||||
"平台处罚",
|
||||
"代采资源",
|
||||
"投放账号权限",
|
||||
"售后协同",
|
||||
"结案交接"
|
||||
],
|
||||
"required_attachment_checklist": [
|
||||
"服务范围及KPI清单",
|
||||
"店铺/账号权限交接清单",
|
||||
"投放预算与对账规则",
|
||||
"素材和知识产权授权清单",
|
||||
"客服售后协同SOP",
|
||||
"终止交接和数据导出清单"
|
||||
],
|
||||
"source_registry_ids": [
|
||||
"src_cn_samr",
|
||||
"src_cn_local_market_regulators",
|
||||
"src_internal_authored"
|
||||
],
|
||||
"rule_ids": [
|
||||
"rule_cn_contract_authority_004",
|
||||
"rule_cn_payment_invoice_005",
|
||||
"rule_cn_auto_renewal_006",
|
||||
"rule_cn_breach_liability_007",
|
||||
"rule_cn_liability_cap_008",
|
||||
"rule_cn_confidentiality_009",
|
||||
"rule_cn_dispute_resolution_010",
|
||||
"rule_cn_service_scope_011",
|
||||
"rule_cn_termination_exit_012",
|
||||
"rule_cn_subcontracting_016"
|
||||
],
|
||||
"clause_ids": [
|
||||
"clause_cn_counterparty_authority_rep_v1",
|
||||
"clause_cn_payment_invoice_alignment_v1",
|
||||
"clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_breach_cure_and_termination_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_dispute_resolution_operable_v1",
|
||||
"clause_cn_termination_and_exit_support_v1",
|
||||
"clause_cn_third_party_services_dependency_v1",
|
||||
"clause_cn_subcontracting_and_subprocessor_v1"
|
||||
],
|
||||
"template_ids": [
|
||||
"tmpl_cn_nda_mutual_basic_001",
|
||||
"tmpl_cn_ai_data_service_basic_001",
|
||||
"tmpl_cn_software_dev_basic_001"
|
||||
],
|
||||
"faq_ids": [
|
||||
"faq_cn_data_003",
|
||||
"faq_cn_data_010",
|
||||
"faq_cn_data_011",
|
||||
"faq_cn_data_014",
|
||||
"faq_cn_data_015"
|
||||
],
|
||||
"draft_gaps": [
|
||||
"尚缺电商代运营专属模板",
|
||||
"尚缺广告宣传和平台处罚的行业专属审查规则",
|
||||
"尚缺电商营销FAQ专包"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,142 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "industry_pack_cn_ai_data_services_v1",
|
||||
"domain": "industry_pack",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"industry": "ai_data_services",
|
||||
"notes": "面向中国AI服务、数据处理、知识库、标注清洗和模型编排场景的行业法务组合包草案。"
|
||||
},
|
||||
"items": {
|
||||
"positioning": {
|
||||
"industry_name": "AI/数据服务",
|
||||
"target_scenarios": [
|
||||
"数据清洗、标注、抽取和评测服务",
|
||||
"企业知识库与RAG知识工程服务",
|
||||
"模型调用编排、Agent工作流或AI平台服务",
|
||||
"客户数据驱动的AI定制项目"
|
||||
],
|
||||
"core_risk_topics": [
|
||||
"客户数据用途越界与训练授权不清",
|
||||
"个人信息、重要数据和安全事件责任边界模糊",
|
||||
"第三方模型、OCR、云服务依赖未充分披露",
|
||||
"输出结果权利、平台能力保留和案例展示边界不清",
|
||||
"终止后的数据返还、删除证明和过渡协助不足"
|
||||
]
|
||||
},
|
||||
"law_sources": [
|
||||
{
|
||||
"source_registry_id": "src_cn_npc_lawdb",
|
||||
"focus": "个人信息保护法、数据安全法、民法典等基础法源",
|
||||
"law_refs": [
|
||||
"《中华人民共和国个人信息保护法》关于处理目的、委托处理、删除和再委托的规则",
|
||||
"《中华人民共和国数据安全法》关于分类分级、安全管理和全过程治理的一般要求",
|
||||
"《中华人民共和国民法典》关于合同履行、违约责任和协作义务的一般规则"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_cn_cac",
|
||||
"focus": "数据出境、算法、个人信息与平台治理相关监管口径",
|
||||
"law_refs": [
|
||||
"网信领域关于数据治理、算法与个人信息处理的规则、办法和公开指引"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_cn_miit",
|
||||
"focus": "信息服务、平台能力和软件服务交付的行业监管材料",
|
||||
"law_refs": [
|
||||
"软件与信息服务相关通知、标准和行业实践材料"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_internal_authored",
|
||||
"focus": "平台自研AI/数据服务合同条款和审查规则",
|
||||
"law_refs": [
|
||||
"平台自研法务内容资产"
|
||||
]
|
||||
}
|
||||
],
|
||||
"recommended_templates": [
|
||||
{
|
||||
"template_id": "tmpl_cn_ai_data_service_basic_001",
|
||||
"usage": "AI数据服务主协议模板"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_dpa_b2b_001",
|
||||
"usage": "承接委托处理、再委托和删除返还责任的数据处理附件"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_saas_msa_neutral_001",
|
||||
"usage": "AI平台订阅、知识库SaaS或标准化服务场景主协议"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_nda_mutual_basic_001",
|
||||
"usage": "模型评测、样本测试和方案交流前的保密协议"
|
||||
}
|
||||
],
|
||||
"recommended_rules": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003",
|
||||
"rule_cn_contract_authority_004",
|
||||
"rule_cn_liability_cap_008",
|
||||
"rule_cn_confidentiality_009",
|
||||
"rule_cn_service_scope_011",
|
||||
"rule_cn_termination_exit_012",
|
||||
"rule_cn_data_export_delete_013",
|
||||
"rule_cn_subcontracting_016"
|
||||
],
|
||||
"recommended_clauses": [
|
||||
"clause_cn_counterparty_authority_rep_v1",
|
||||
"clause_cn_data_processing_dpa_v1",
|
||||
"clause_cn_data_roles_and_instructions_v1",
|
||||
"clause_cn_data_categories_and_purposes_v1",
|
||||
"clause_cn_security_incident_notice_v1",
|
||||
"clause_cn_subcontracting_and_subprocessor_v1",
|
||||
"clause_cn_ip_layered_allocation_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_termination_and_exit_support_v1",
|
||||
"clause_cn_data_export_delete_workflow_v1"
|
||||
],
|
||||
"faq_ids": [
|
||||
"faq_cn_data_001",
|
||||
"faq_cn_data_004",
|
||||
"faq_cn_data_005",
|
||||
"faq_cn_data_006",
|
||||
"faq_cn_data_007",
|
||||
"faq_cn_data_008",
|
||||
"faq_cn_data_012",
|
||||
"faq_cn_data_014"
|
||||
],
|
||||
"playbooks": [
|
||||
{
|
||||
"theme": "客户数据能否用于训练或产品优化",
|
||||
"template_ids": ["tmpl_cn_ai_data_service_basic_001", "tmpl_cn_dpa_b2b_001"],
|
||||
"rule_ids": ["rule_cn_saas_data_scope_002", "rule_cn_saas_ip_output_003"],
|
||||
"clause_ids": ["clause_cn_data_roles_and_instructions_v1", "clause_cn_ip_layered_allocation_v1"]
|
||||
},
|
||||
{
|
||||
"theme": "第三方大模型、OCR和云服务依赖管理",
|
||||
"template_ids": ["tmpl_cn_ai_data_service_basic_001", "tmpl_cn_saas_msa_neutral_001"],
|
||||
"rule_ids": ["rule_cn_subcontracting_016", "rule_cn_saas_data_scope_002"],
|
||||
"clause_ids": ["clause_cn_subcontracting_and_subprocessor_v1", "clause_cn_security_incident_notice_v1"]
|
||||
},
|
||||
{
|
||||
"theme": "项目结束后的数据返还、删除证明与过渡支持",
|
||||
"template_ids": ["tmpl_cn_ai_data_service_basic_001", "tmpl_cn_dpa_b2b_001"],
|
||||
"rule_ids": ["rule_cn_termination_exit_012", "rule_cn_data_export_delete_013"],
|
||||
"clause_ids": ["clause_cn_termination_and_exit_support_v1", "clause_cn_data_export_delete_workflow_v1"]
|
||||
}
|
||||
],
|
||||
"known_gaps": [
|
||||
"尚缺AI训练授权专用附件、模型输出侵权应对专用条款集和跨境数据场景专属模板",
|
||||
"缺少面向数据标注、众包采集、模型测评等细分业态的垂直FAQ",
|
||||
"缺少结合监管处罚与裁判摘要的高风险案例卡片"
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,131 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "industry_pack_cn_ecommerce_operations_v1",
|
||||
"domain": "industry_pack",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"industry": "ecommerce_operations",
|
||||
"notes": "面向中国电商代运营、平台店铺服务、直播推广和营销协作场景的过渡版行业法务组合包草案。当前以通用企业商事模板和规则为骨架。"
|
||||
},
|
||||
"items": {
|
||||
"positioning": {
|
||||
"industry_name": "电商/代运营",
|
||||
"target_scenarios": [
|
||||
"店铺代运营与月度服务费+提成合作",
|
||||
"直播推广、内容运营和广告投放协作",
|
||||
"平台招商、渠道联营与品牌授权配套合作",
|
||||
"客户资料、用户线索和经营数据共享场景"
|
||||
],
|
||||
"core_risk_topics": [
|
||||
"服务范围、KPI口径和客户配合义务不清",
|
||||
"营销合规、宣传用语和平台规则变动责任不明",
|
||||
"广告素材、店铺数据、客户名单和投放账户权限边界不清",
|
||||
"佣金结算、开票、退款和活动损失分担争议",
|
||||
"合作终止后账号交接、数据导出和素材返还安排不足"
|
||||
]
|
||||
},
|
||||
"law_sources": [
|
||||
{
|
||||
"source_registry_id": "src_cn_npc_lawdb",
|
||||
"focus": "民法典、电子商务法等电商合作基础法源",
|
||||
"law_refs": [
|
||||
"《中华人民共和国民法典》关于服务合同、委托协作、违约责任的一般规则",
|
||||
"《中华人民共和国电子商务法》关于平台经营、信息披露、消费者保护的基础规则"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_cn_samr",
|
||||
"focus": "广告、反不正当竞争、消费者权益和格式条款监管口径",
|
||||
"law_refs": [
|
||||
"市场监管领域关于广告宣传、促销活动、消费者权益和不正当竞争的规则与公开指引"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_cn_local_market_regulators",
|
||||
"focus": "直播电商、地方执法口径和营销活动合规提醒",
|
||||
"law_refs": [
|
||||
"地方市场监管部门关于直播电商、促销和平台经营的执法提示与公开材料"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_internal_authored",
|
||||
"focus": "平台现有通用商业合同模板与规则的电商过渡编排",
|
||||
"law_refs": [
|
||||
"平台自研法务内容资产"
|
||||
]
|
||||
}
|
||||
],
|
||||
"recommended_templates": [
|
||||
{
|
||||
"template_id": "tmpl_cn_software_dev_basic_001",
|
||||
"usage": "作为项目制代运营/活动交付过渡模板,承载范围清单、阶段交付和变更控制"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_saas_msa_neutral_001",
|
||||
"usage": "作为店铺工具、运营后台、会员系统或营销SaaS配套服务协议模板"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_nda_mutual_basic_001",
|
||||
"usage": "品牌资料、店铺数据、价格政策和渠道资源合作前保密协议"
|
||||
}
|
||||
],
|
||||
"recommended_rules": [
|
||||
"rule_cn_contract_authority_004",
|
||||
"rule_cn_payment_invoice_005",
|
||||
"rule_cn_breach_liability_007",
|
||||
"rule_cn_confidentiality_009",
|
||||
"rule_cn_dispute_resolution_010",
|
||||
"rule_cn_service_scope_011",
|
||||
"rule_cn_termination_exit_012",
|
||||
"rule_cn_change_order_015"
|
||||
],
|
||||
"recommended_clauses": [
|
||||
"clause_cn_counterparty_authority_rep_v1",
|
||||
"clause_cn_payment_invoice_alignment_v1",
|
||||
"clause_cn_breach_cure_and_termination_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_dispute_resolution_operable_v1",
|
||||
"clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_cn_change_order_project_v1",
|
||||
"clause_cn_termination_and_exit_support_v1"
|
||||
],
|
||||
"faq_ids": [
|
||||
"faq_cn_data_009",
|
||||
"faq_cn_data_011",
|
||||
"faq_cn_data_014",
|
||||
"faq_cn_data_015",
|
||||
"faq_cn_data_016",
|
||||
"faq_cn_data_017",
|
||||
"faq_cn_data_018"
|
||||
],
|
||||
"playbooks": [
|
||||
{
|
||||
"theme": "代运营合作只写“提升销量”而未定义工作边界",
|
||||
"template_ids": ["tmpl_cn_software_dev_basic_001"],
|
||||
"rule_ids": ["rule_cn_service_scope_011", "rule_cn_change_order_015"],
|
||||
"clause_ids": ["clause_cn_service_scope_and_change_order_v1", "clause_cn_change_order_project_v1"]
|
||||
},
|
||||
{
|
||||
"theme": "佣金结算、返点、活动退款和开票周期争议",
|
||||
"template_ids": ["tmpl_cn_software_dev_basic_001", "tmpl_cn_saas_msa_neutral_001"],
|
||||
"rule_ids": ["rule_cn_payment_invoice_005", "rule_cn_breach_liability_007"],
|
||||
"clause_ids": ["clause_cn_payment_invoice_alignment_v1", "clause_cn_breach_cure_and_termination_v1"]
|
||||
},
|
||||
{
|
||||
"theme": "合作终止后的店铺后台、素材、数据和账号交接",
|
||||
"template_ids": ["tmpl_cn_software_dev_basic_001", "tmpl_cn_nda_mutual_basic_001"],
|
||||
"rule_ids": ["rule_cn_termination_exit_012", "rule_cn_confidentiality_009"],
|
||||
"clause_ids": ["clause_cn_termination_and_exit_support_v1", "clause_cn_confidentiality_fullstack_v1"]
|
||||
}
|
||||
],
|
||||
"known_gaps": [
|
||||
"当前缺少电商代运营专属主模板、直播推广专属模板和品牌授权配套模板",
|
||||
"FAQ仍以通用商事/数据问答为主,尚缺广告法、直播话术、平台处罚和消费者投诉专项FAQ",
|
||||
"尚缺与电子商务法、广告法、反不正当竞争法深度绑定的专属审查规则包"
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,143 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "industry_pack_cn_saas_software_v1",
|
||||
"domain": "industry_pack",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"industry": "saas_software",
|
||||
"notes": "面向中国SaaS订阅、软件实施、定制开发与配套NDA场景的行业法务组合包草案。"
|
||||
},
|
||||
"items": {
|
||||
"positioning": {
|
||||
"industry_name": "SaaS/软件",
|
||||
"target_scenarios": [
|
||||
"标准SaaS订阅采购",
|
||||
"SaaS+实施上线一体化项目",
|
||||
"定制开发与接口集成项目",
|
||||
"售前POC、试用与保密接洽"
|
||||
],
|
||||
"core_risk_topics": [
|
||||
"验收标准主观化或缺失",
|
||||
"服务范围蔓延与变更失控",
|
||||
"平台预存IP与项目成果归属混同",
|
||||
"自动续约、开票付款与责任上限失衡",
|
||||
"退出迁移、数据导出和持续支持安排不足"
|
||||
]
|
||||
},
|
||||
"law_sources": [
|
||||
{
|
||||
"source_registry_id": "src_cn_npc_lawdb",
|
||||
"focus": "民法典、著作权法等合同与知识产权基础法源",
|
||||
"law_refs": [
|
||||
"《中华人民共和国民法典》合同编关于履行、变更、解除、违约责任的一般规则",
|
||||
"《中华人民共和国著作权法》软件及作品权利归属基本规则"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_cn_miit",
|
||||
"focus": "软件、平台服务、工业互联网及信息化项目监管口径",
|
||||
"law_refs": [
|
||||
"工信领域软件与信息服务相关规范性文件、通知和行业指引"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_cn_cac",
|
||||
"focus": "SaaS处理业务数据和个人信息时的数据合规边界",
|
||||
"law_refs": [
|
||||
"数据处理、网络与个人信息保护相关监管规则和公开指引"
|
||||
]
|
||||
},
|
||||
{
|
||||
"source_registry_id": "src_internal_authored",
|
||||
"focus": "平台条款、规则、模板与FAQ的结构化编排",
|
||||
"law_refs": [
|
||||
"平台自研法务内容资产"
|
||||
]
|
||||
}
|
||||
],
|
||||
"recommended_templates": [
|
||||
{
|
||||
"template_id": "tmpl_cn_saas_msa_neutral_001",
|
||||
"usage": "标准订阅式SaaS主服务协议主模板"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_software_dev_basic_001",
|
||||
"usage": "定制开发、二开、接口交付项目主模板"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_nda_mutual_basic_001",
|
||||
"usage": "售前评估、POC、演示与需求对接前的保密协议"
|
||||
},
|
||||
{
|
||||
"template_id": "tmpl_cn_dpa_b2b_001",
|
||||
"usage": "涉及客户数据、日志、个人信息时的数据处理附件"
|
||||
}
|
||||
],
|
||||
"recommended_rules": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_saas_data_scope_002",
|
||||
"rule_cn_saas_ip_output_003",
|
||||
"rule_cn_payment_invoice_005",
|
||||
"rule_cn_auto_renewal_006",
|
||||
"rule_cn_liability_cap_008",
|
||||
"rule_cn_service_scope_011",
|
||||
"rule_cn_termination_exit_012",
|
||||
"rule_cn_data_export_delete_013",
|
||||
"rule_cn_sla_support_014",
|
||||
"rule_cn_change_order_015"
|
||||
],
|
||||
"recommended_clauses": [
|
||||
"clause_cn_acceptance_saas_objective_v1",
|
||||
"clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_cn_change_order_project_v1",
|
||||
"clause_cn_sla_operational_metrics_v1",
|
||||
"clause_cn_payment_invoice_alignment_v1",
|
||||
"clause_cn_auto_renewal_notice_v1",
|
||||
"clause_cn_ip_layered_allocation_v1",
|
||||
"clause_cn_termination_and_exit_support_v1",
|
||||
"clause_cn_data_export_delete_workflow_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_dispute_resolution_operable_v1"
|
||||
],
|
||||
"faq_ids": [
|
||||
"faq_cn_data_002",
|
||||
"faq_cn_data_003",
|
||||
"faq_cn_data_007",
|
||||
"faq_cn_data_009",
|
||||
"faq_cn_data_010",
|
||||
"faq_cn_data_011",
|
||||
"faq_cn_data_013",
|
||||
"faq_cn_data_014"
|
||||
],
|
||||
"playbooks": [
|
||||
{
|
||||
"theme": "客户坚持甲方主观满意验收",
|
||||
"template_ids": ["tmpl_cn_saas_msa_neutral_001", "tmpl_cn_software_dev_basic_001"],
|
||||
"rule_ids": ["rule_cn_saas_acceptance_001", "rule_cn_change_order_015"],
|
||||
"clause_ids": ["clause_cn_acceptance_saas_objective_v1", "clause_cn_change_order_project_v1"]
|
||||
},
|
||||
{
|
||||
"theme": "客户要求所有成果和底层平台归甲方",
|
||||
"template_ids": ["tmpl_cn_saas_msa_neutral_001", "tmpl_cn_software_dev_basic_001"],
|
||||
"rule_ids": ["rule_cn_saas_ip_output_003"],
|
||||
"clause_ids": ["clause_cn_ip_layered_allocation_v1", "clause_cn_confidentiality_fullstack_v1"]
|
||||
},
|
||||
{
|
||||
"theme": "到期退出、导出数据与过渡支持谈判",
|
||||
"template_ids": ["tmpl_cn_saas_msa_neutral_001", "tmpl_cn_dpa_b2b_001"],
|
||||
"rule_ids": ["rule_cn_termination_exit_012", "rule_cn_data_export_delete_013"],
|
||||
"clause_ids": ["clause_cn_termination_and_exit_support_v1", "clause_cn_data_export_delete_workflow_v1"]
|
||||
}
|
||||
],
|
||||
"known_gaps": [
|
||||
"尚缺更细的私有化部署、源码托管、渠道代理、实施驻场等专属模板",
|
||||
"缺少软件采购/项目交付类行业化FAQ子包",
|
||||
"缺少与裁判观点绑定的案例化审查说明"
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,128 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "industry_saas_software_cn_v1",
|
||||
"domain": "industry_pack",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "hybrid_compilation",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "draft",
|
||||
"notes": "Draft SaaS/software industry pack linking currently available sources, rules, clauses, templates, and FAQ assets."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"pack_id": "industry_pack_cn_saas_software_001",
|
||||
"pack_name": "SaaS/软件行业法务包",
|
||||
"industry": "saas_software",
|
||||
"summary": "覆盖标准订阅SaaS、实施上线、轻量定制开发与售后维保场景,优先解决范围、验收、SLA、变更、数据与退出风险。",
|
||||
"common_contract_types": [
|
||||
"SaaS主服务协议",
|
||||
"软件开发合同",
|
||||
"实施/上线服务协议",
|
||||
"保密协议"
|
||||
],
|
||||
"regulatory_focus": [
|
||||
"服务范围和订单文件层级",
|
||||
"上线验收、版本迭代和SLA可执行性",
|
||||
"数据处理与安全事件通知",
|
||||
"知识产权分层归属与第三方依赖",
|
||||
"终止后的导出、交接和持续义务"
|
||||
],
|
||||
"common_disputes": [
|
||||
"需求边界不清导致持续加项",
|
||||
"验收标准主观化导致回款拖延",
|
||||
"SLA承诺无法量化或无法举证",
|
||||
"项目终止后数据和账号难以交接",
|
||||
"第三方云资源或接口故障责任归属不清"
|
||||
],
|
||||
"must_review_clause_ids": [
|
||||
"clause_cn_parties_and_scope_v1",
|
||||
"clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_cn_acceptance_saas_objective_v1",
|
||||
"clause_cn_sla_operational_metrics_v1",
|
||||
"clause_cn_security_incident_notice_v1",
|
||||
"clause_cn_ip_layered_allocation_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_termination_and_exit_support_v1"
|
||||
],
|
||||
"high_risk_expressions": [
|
||||
"以客户满意为唯一验收标准",
|
||||
"服务商无条件满足后续新增需求",
|
||||
"任何中断均按月费全额赔偿",
|
||||
"客户可随时要求永久免费迁移支持"
|
||||
],
|
||||
"glossary_terms": [
|
||||
"订单文件优先级",
|
||||
"需求冻结",
|
||||
"上线窗口",
|
||||
"可用性口径",
|
||||
"服务抵扣"
|
||||
],
|
||||
"required_attachment_checklist": [
|
||||
"订单/报价单",
|
||||
"实施计划或项目排期",
|
||||
"SLA附件",
|
||||
"数据处理附件",
|
||||
"验收标准或验收单",
|
||||
"退出交接清单"
|
||||
],
|
||||
"source_registry_ids": [
|
||||
"src_cn_miit",
|
||||
"src_cn_cac",
|
||||
"src_internal_authored"
|
||||
],
|
||||
"rule_ids": [
|
||||
"rule_cn_saas_acceptance_001",
|
||||
"rule_cn_payment_invoice_005",
|
||||
"rule_cn_auto_renewal_006",
|
||||
"rule_cn_breach_liability_007",
|
||||
"rule_cn_liability_cap_008",
|
||||
"rule_cn_service_scope_011",
|
||||
"rule_cn_termination_exit_012",
|
||||
"rule_cn_sla_support_014",
|
||||
"rule_cn_change_order_015",
|
||||
"rule_cn_subcontracting_016"
|
||||
],
|
||||
"clause_ids": [
|
||||
"clause_cn_definitions_order_docs_v1",
|
||||
"clause_cn_parties_and_scope_v1",
|
||||
"clause_cn_service_term_and_renewal_v1",
|
||||
"clause_cn_fees_and_invoice_saas_v1",
|
||||
"clause_cn_payment_invoice_alignment_v1",
|
||||
"clause_cn_delivery_implementation_plan_v1",
|
||||
"clause_cn_acceptance_saas_objective_v1",
|
||||
"clause_cn_sla_standard_v1",
|
||||
"clause_cn_sla_operational_metrics_v1",
|
||||
"clause_cn_service_scope_and_change_order_v1",
|
||||
"clause_cn_software_dev_deliverables_and_change_control_v1",
|
||||
"clause_cn_change_order_project_v1",
|
||||
"clause_cn_maintenance_support_post_acceptance_v1",
|
||||
"clause_cn_security_incident_notice_v1",
|
||||
"clause_cn_confidentiality_fullstack_v1",
|
||||
"clause_cn_ip_layered_allocation_v1",
|
||||
"clause_cn_liability_cap_carveout_v1",
|
||||
"clause_cn_termination_and_exit_support_v1",
|
||||
"clause_cn_third_party_services_dependency_v1",
|
||||
"clause_cn_dispute_resolution_operable_v1"
|
||||
],
|
||||
"template_ids": [
|
||||
"tmpl_cn_saas_msa_neutral_001",
|
||||
"tmpl_cn_software_dev_basic_001",
|
||||
"tmpl_cn_nda_mutual_basic_001"
|
||||
],
|
||||
"faq_ids": [
|
||||
"faq_cn_data_003",
|
||||
"faq_cn_data_009",
|
||||
"faq_cn_data_010",
|
||||
"faq_cn_data_011",
|
||||
"faq_cn_data_014",
|
||||
"faq_cn_data_015"
|
||||
],
|
||||
"draft_gaps": [
|
||||
"尚缺独立的软件运维服务模板",
|
||||
"尚缺行业化价格调整和续费FAQ"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,449 @@
|
||||
{
|
||||
"version": 1,
|
||||
"metadata": {
|
||||
"package_name": "review_rules_cn_contract_v1",
|
||||
"domain": "rules",
|
||||
"jurisdiction": "CN",
|
||||
"content_version": "v1",
|
||||
"source_type": "internal_authored",
|
||||
"maintainer": "qishu",
|
||||
"review_status": "approved",
|
||||
"created_at": "2026-05-04T07:17:07Z",
|
||||
"updated_at": "2026-05-04T07:17:07Z",
|
||||
"notes": "PRC commercial contract review rule pack v1 for enterprise transactions, with emphasis on SaaS, software development, implementation, and AI/data service scenarios."
|
||||
},
|
||||
"items": [
|
||||
{
|
||||
"rule_id": "rule_cn_saas_acceptance_001",
|
||||
"rule_name": "SaaS验收标准缺失或仅以甲方主观满意为准",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "implementation_service_agreement"],
|
||||
"clause_scope": ["acceptance", "delivery", "service_level"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["验收合格", "甲方满意", "上线即视为验收", "无异议视为验收"],
|
||||
"risk_description": "未约定可操作的验收口径、测试周期、缺陷分级和整改次数时,容易导致交付争议长期悬而未决;若仅以单方主观满意为标准,服务方难以证明已完成主要义务。",
|
||||
"review_question": "是否已经明确交付物清单、验收环境、测试方法、缺陷等级、整改期限,以及逾期不验收时的推定机制?",
|
||||
"suggested_fix": "将验收拆分为交付确认、试运行、正式验收三个节点;明确关键指标、书面异议期限、整改轮次和逾期未反馈视为阶段性通过的规则。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于全面履行、协作履行与违约责任的一般规则",
|
||||
"reason": "验收安排直接影响是否完成履行、是否存在违约以及损失认定。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:软件开发/信息化项目因验收标准不明引发价款争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_acceptance_saas_objective_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored review seed based on common commercial practice."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_saas_data_scope_002",
|
||||
"rule_name": "数据处理边界、角色分工与安全义务不清",
|
||||
"contract_scope": ["saas_service_agreement", "data_processing_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["data_processing", "data_security", "privacy"],
|
||||
"industry_scope": ["saas", "ai_data_services"],
|
||||
"severity": "critical",
|
||||
"trigger_pattern": ["数据安全", "个人信息", "委托处理", "接口数据", "训练数据"],
|
||||
"risk_description": "合同未区分控制者/处理者、委托处理范围、保存期限、删除返还义务及安全事件通知机制时,双方会在合规责任、客户索赔和监管应对上出现重大不确定性。",
|
||||
"review_question": "是否明确了数据类型、处理目的、处理方式、最小必要范围、子处理者限制、安全措施、泄露通知和终止后的删除/返还流程?",
|
||||
"suggested_fix": "新增专门的数据处理附件,逐项写明数据分类、处理角色、跨境限制、审计配合、事件通知时限、子处理者准入及终止后的数据处置义务。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国个人信息保护法》关于委托处理、处理规则透明化与处理者义务的规定",
|
||||
"reason": "涉及个人信息处理角色和委托链条时,合同需要支撑法定义务落地。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国数据安全法》关于数据安全管理义务的一般要求",
|
||||
"reason": "数据分类、保护措施和事件处置需要形成合同化约束。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:平台服务商与企业客户因数据导出、删除及泄露通知责任争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_data_processing_dpa_v1", "clause_cn_security_incident_notice_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored review seed informed by PRC data compliance practice."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_saas_ip_output_003",
|
||||
"rule_name": "平台预存知识产权与项目产出归属混同",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["intellectual_property", "deliverables", "license"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["知识产权归甲方所有", "平台", "底层代码", "模型", "接口", "成果归属"],
|
||||
"risk_description": "若将底层平台、预存代码、通用工具与定制交付成果一并约定为客户所有,可能导致服务方核心资产流失;若完全不区分客户专属成果,也会引发客户对使用权与迁移权的重大顾虑。",
|
||||
"review_question": "是否区分预存IP、第三方组件、通用能力、客户数据、定制成果及其对应的所有权、许可范围和退出迁移安排?",
|
||||
"suggested_fix": "采用分层归属结构:预存平台和通用能力归服务方,客户数据归客户,定制交付成果按约定归属或许可,并补充必要的内部使用、展示、接口调用及迁移协助条款。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于意思自治与合同解释的一般规则",
|
||||
"reason": "知识产权和成果归属需要通过明确约定避免重大解释争议。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国著作权法》关于作品和软件权利归属的基本规则",
|
||||
"reason": "代码、文档、模型相关成果的权利界定需要兼容著作权法框架。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:软件定制项目中底层代码与二次开发成果归属争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_ip_layered_allocation_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Platform-authored review seed for software and AI delivery contracts."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_contract_authority_004",
|
||||
"rule_name": "主体资格、经营范围或签约权限未核验",
|
||||
"contract_scope": ["general_commercial_contract", "saas_service_agreement", "software_development_agreement", "procurement_agreement"],
|
||||
"clause_scope": ["parties", "signing_authority", "representations_and_warranties"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "critical",
|
||||
"trigger_pattern": ["授权代表", "签署", "营业执照", "法定代表人", "受托签约"],
|
||||
"risk_description": "未核验合同相对方存续状态、经营资质、受限情形或签约代表权限时,可能出现合同效力争议、履约主体不明确、付款对象错配以及后续追责困难。",
|
||||
"review_question": "是否已核验相对方名称与统一社会信用代码、存续状态、必要资质许可,以及签字人是否为法定代表人或持有有效授权文件?",
|
||||
"suggested_fix": "在签约前完成主体尽调并留存营业执照、授权委托书、董事会或内部审批文件;合同中补充主体陈述保证、资质持续有效义务及权限瑕疵的赔偿责任。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》关于民事主体、代理与合同效力的一般规则",
|
||||
"reason": "主体资格和代理权限直接影响合同成立、生效及责任承担。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国公司法》关于法定代表人、公司对外行为和内部授权治理的基本规则",
|
||||
"reason": "公司签约权限通常需要与公司治理和授权安排相匹配。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:因越权签约或主体不真实导致合同效力与付款责任争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_counterparty_authority_rep_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal commercial contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_payment_invoice_005",
|
||||
"rule_name": "付款条件、对账口径与发票义务不匹配",
|
||||
"contract_scope": ["general_commercial_contract", "saas_service_agreement", "software_development_agreement", "service_agreement"],
|
||||
"clause_scope": ["payment", "invoice", "acceptance"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["付款", "开票", "发票", "对账", "付款条件"],
|
||||
"risk_description": "若价税口径、付款节点、验收/对账前提、发票类型和开具时点不一致,容易引发拖延付款、拒收发票、税务成本转嫁及逾期违约金争议。",
|
||||
"review_question": "是否明确含税/不含税价格、付款前置条件、对账确认机制、发票类型税率、开票时点,以及发票瑕疵是否影响付款义务?",
|
||||
"suggested_fix": "将付款节点与可验证里程碑绑定,明确对账异议期、电子/专票要求、开票信息变更流程,并约定除重大税务违法外不得以轻微开票瑕疵拒绝支付已到期无争议价款。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于价款支付、同时履行抗辩与违约责任的一般规则",
|
||||
"reason": "付款条件和配合义务的表述决定是否构成到期债务及抗辩。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国发票管理办法》及相关税务管理规则",
|
||||
"reason": "发票种类、开具义务和税务合规直接影响交易执行与成本承担。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:因开票与付款节点脱节导致服务费争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_payment_invoice_alignment_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal commercial contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_auto_renewal_006",
|
||||
"rule_name": "自动续约触发条件、通知方式或调价机制不清",
|
||||
"contract_scope": ["saas_service_agreement", "maintenance_service_agreement", "framework_service_agreement"],
|
||||
"clause_scope": ["term", "renewal", "pricing"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services", "general_commercial"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["自动续期", "自动续约", "到期顺延", "续费"],
|
||||
"risk_description": "自动续约条款未明确通知路径、提前终止窗口、续期价格和服务范围调整规则时,容易产生被动续费、预算超支或履约基础变化后的争议。",
|
||||
"review_question": "是否明确自动续约的适用前提、通知期限与送达方式、客户拒绝续约窗口,以及续期价格、指标、服务内容是否可调整?",
|
||||
"suggested_fix": "将自动续约限定为书面提醒后生效,明确至少一轮到期前通知、客户可在约定窗口内拒绝续约,并写明续期价格按原价、预先约定公式或双方另行确认。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于意思表示、格式条款提示说明及合同解释的一般规则",
|
||||
"reason": "自动续约涉及持续交易下的重要权利义务变动,应确保意思表示清晰可证明。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:企业软件订阅因自动续费提示不足引发价款争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_auto_renewal_notice_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal SaaS contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_breach_liability_007",
|
||||
"rule_name": "违约情形、补救期限与救济路径约定失衡或缺失",
|
||||
"contract_scope": ["general_commercial_contract", "saas_service_agreement", "software_development_agreement", "service_agreement"],
|
||||
"clause_scope": ["breach", "remedy", "termination"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["违约责任", "补救期限", "立即解除", "违约金"],
|
||||
"risk_description": "如仅对一方设置严格违约责任,或未区分一般违约、重大违约与可补救违约,容易导致小瑕疵被直接放大为解除或索赔依据,增加交易不稳定性。",
|
||||
"review_question": "是否明确主要违约类型、通知与补救期、重大违约的认定口径、继续履行与解除的适用顺序,以及违约金与实际损失之间的衔接?",
|
||||
"suggested_fix": "按违约等级分层设计:一般违约先通知并给予合理补救期,重大违约方可触发暂停服务、解除合同或索赔;对违约金过高或过低情形保留依法调整空间。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于违约责任、继续履行、补救措施、解除权和违约金调整的规定",
|
||||
"reason": "违约条款直接影响救济顺序、损失分配和争议裁量空间。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:持续服务合同因轻微违约被解除引发损失争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_breach_cure_and_termination_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal commercial contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_liability_cap_008",
|
||||
"rule_name": "责任上限缺失、过低或例外范围不清",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "general_commercial_contract", "ai_service_agreement"],
|
||||
"clause_scope": ["limitation_of_liability", "indemnity", "breach"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "critical",
|
||||
"trigger_pattern": ["责任上限", "赔偿上限", "全部损失", "无限责任"],
|
||||
"risk_description": "没有责任上限或上限与交易规模明显失衡时,服务方可能承担不可测的连带商业风险;而上限过低且无例外,会使客户在数据泄露、侵权或故意违约场景下难以获得实质救济。",
|
||||
"review_question": "是否约定总体责任上限的计算基数、适用期间、可累计方式,以及对故意、重大过失、保密/数据安全/知识产权侵权等情形是否设置合理例外?",
|
||||
"suggested_fix": "以近12个月已支付费用、相关订单总价或明确倍数作为一般责任上限,并列明不受限或提高上限的例外事项;同时排除间接损失时应保留可预见直接损失与合理维权费用。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于违约损失赔偿、可预见规则和格式条款公平性的基本规则",
|
||||
"reason": "责任限制安排需兼顾意思自治、风险可控与显失公平审查。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:SaaS合同责任上限与数据泄露损失范围争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_liability_cap_carveout_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal SaaS contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_confidentiality_009",
|
||||
"rule_name": "保密信息范围、例外、期限或披露流程不完整",
|
||||
"contract_scope": ["nda", "general_commercial_contract", "saas_service_agreement", "software_development_agreement"],
|
||||
"clause_scope": ["confidentiality", "data_security", "publicity"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["保密", "机密信息", "披露", "宣传"],
|
||||
"risk_description": "若保密信息定义过窄或没有法定披露、已公开、独立开发等例外,执行时难以落地;若未限制对外宣传、客户名称使用和内部知悉范围,也容易引发商业信誉或数据扩散风险。",
|
||||
"review_question": "是否明确保密信息定义、合理例外、内部最小必要知悉、法定披露通知、保密期限,以及客户名称、Logo、案例宣传的使用条件?",
|
||||
"suggested_fix": "采用“列举+兜底”定义,补充法定披露提前通知、员工与分包商同等约束、宣传需另行书面同意、以及返还或销毁证明义务。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于附随义务、诚实信用与违约责任的一般规则",
|
||||
"reason": "保密义务属于交易合作中的重要附随义务。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国反不正当竞争法》关于商业秘密保护的基本规则",
|
||||
"reason": "涉及技术信息和经营信息时,合同约束有助于商业秘密保护与举证。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:项目合作中客户信息对外宣传引发违约争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_confidentiality_fullstack_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal commercial contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_dispute_resolution_010",
|
||||
"rule_name": "争议解决条款的管辖、仲裁机构或送达机制不确定",
|
||||
"contract_scope": ["general_commercial_contract", "saas_service_agreement", "software_development_agreement", "procurement_agreement"],
|
||||
"clause_scope": ["dispute_resolution", "governing_law", "notice"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "medium",
|
||||
"trigger_pattern": ["争议解决", "仲裁", "管辖法院", "送达地址"],
|
||||
"risk_description": "若仲裁机构名称错误、约定法院无实际连接点,或送达地址与电子通知机制缺失,争议发生后可能出现管辖无效、程序拖延和证据送达受阻。",
|
||||
"review_question": "是否明确适用法律、有效的仲裁机构或有管辖连接点的法院,并约定书面与电子送达地址、变更通知义务及通知视为送达规则?",
|
||||
"suggested_fix": "统一争议解决路径,避免“仲裁/诉讼并列但不清”表述;补充电子邮件、系统消息、快递地址的多轨送达条款,并要求地址变更未通知的一方承担不利后果。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于协议解释与诚实信用的一般规则",
|
||||
"reason": "争议解决条款需要具有可执行性并能支持后续程序。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国仲裁法》《中华人民共和国民事诉讼法》关于仲裁协议和管辖约定的基本规则",
|
||||
"reason": "无效仲裁约定或不当管辖约定会直接影响争议处理效率。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:仲裁机构名称错误导致仲裁条款效力争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_dispute_resolution_operable_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal commercial contract review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_service_scope_011",
|
||||
"rule_name": "服务范围、交付边界与客户配合义务界定不清",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "implementation_service_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["services", "deliverables", "customer_dependencies"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "critical",
|
||||
"trigger_pattern": ["服务内容", "工作范围", "配合义务", "接口", "里程碑"],
|
||||
"risk_description": "若合同只描述总体目标而未细化服务清单、排除事项、客户前置条件和第三方依赖,项目实施中极易发生范围蔓延、追加收费争议和延期责任倒置。",
|
||||
"review_question": "是否明确基线服务清单、非包含项、客户需提供的资源与决策时点、第三方系统依赖、变更管理流程以及超范围工作的收费规则?",
|
||||
"suggested_fix": "以附件方式列示范围说明书、角色分工矩阵和里程碑计划,并设置需求变更单、客户逾期配合顺延、第三方限制免责及超范围服务单独报价机制。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于标的、履行方式、协作履行与违约责任的一般规则",
|
||||
"reason": "服务边界和配合义务是判断是否违约及是否应顺延的重要基础。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:实施项目因需求边界不清导致延期与价款争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_service_scope_and_change_order_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal SaaS and implementation review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_termination_exit_012",
|
||||
"rule_name": "终止事由、终止后结算与退出协助安排缺失",
|
||||
"contract_scope": ["saas_service_agreement", "software_development_agreement", "general_commercial_contract", "ai_service_agreement"],
|
||||
"clause_scope": ["termination", "exit", "handover"],
|
||||
"industry_scope": ["general_commercial", "saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["解除", "终止", "退出", "交接"],
|
||||
"risk_description": "合同未区分到期终止、便利解除、重大违约解除和法定解除,且未约定终止后的费用结算、账号关闭、资料交接和过渡支持时,双方容易在退出阶段发生集中冲突。",
|
||||
"review_question": "是否明确各类终止路径、提前通知期、已履行部分结算、预付款退还规则、过渡服务期限,以及交接材料和账号处置方式?",
|
||||
"suggested_fix": "建立终止与退出章节,分别约定到期不续、便利解除、违约解除、合规停服的适用条件,并补充未完成工时结算、账号冻结、交接清单和有偿过渡支持。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于解除、终止后果、恢复原状与损失赔偿的规定",
|
||||
"reason": "终止机制和后果直接影响交易退出成本与争议处理。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:云服务终止后账号关闭与预付款退还争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_termination_and_exit_support_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal contract exit review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_data_export_delete_013",
|
||||
"rule_name": "数据导出、迁移协助与删除证明义务不明确",
|
||||
"contract_scope": ["saas_service_agreement", "data_processing_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["data_export", "data_retention", "termination"],
|
||||
"industry_scope": ["saas", "ai_data_services"],
|
||||
"severity": "critical",
|
||||
"trigger_pattern": ["数据导出", "数据迁移", "删除", "返还数据"],
|
||||
"risk_description": "缺少导出格式、接口权限、迁移时限、删除例外和删除证明约定时,客户可能陷入供应商锁定;服务方也可能在备份保留、监管留存与删除请求之间承担不确定责任。",
|
||||
"review_question": "是否明确导出数据范围、格式、频次、费用、协助边界、删除时限、备份保留例外及删除完成证明方式?",
|
||||
"suggested_fix": "约定标准化导出格式和下载窗口,区分在线导出、API导出和人工迁移协助;终止后在法定留存和安全备份例外下完成删除,并向客户出具删除/匿名化确认。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国个人信息保护法》关于委托处理终止、删除和个人信息处理义务的规定",
|
||||
"reason": "个人信息和业务数据退出时需要有明确的处置路径。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国数据安全法》关于数据处理全过程安全管理的一般要求",
|
||||
"reason": "导出、迁移和删除均涉及数据安全和责任留痕。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:SaaS客户退出时数据无法完整导出引发服务争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_data_export_delete_workflow_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal data lifecycle review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_sla_support_014",
|
||||
"rule_name": "服务可用性、故障响应和服务补偿机制不可执行",
|
||||
"contract_scope": ["saas_service_agreement", "maintenance_service_agreement", "hosting_service_agreement"],
|
||||
"clause_scope": ["service_level", "support", "credits"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["SLA", "可用性", "响应时间", "服务补偿"],
|
||||
"risk_description": "如只笼统承诺高可用而未界定统计口径、维护窗口、故障等级、排除情形和补偿上限,SLA将难以执行,也容易与违约赔偿、责任上限条款发生冲突。",
|
||||
"review_question": "是否明确可用性计算方法、监测来源、计划维护通知、事件等级、响应恢复时限、服务积分/赔偿的申请条件及与其他救济的关系?",
|
||||
"suggested_fix": "将SLA做成附件,写明月度可用性公式、计划维护排除、客户原因和第三方网络排除项、故障升级路径,以及服务积分是否为唯一救济的适用范围。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于履行标准、违约责任与损失赔偿的一般规则",
|
||||
"reason": "服务等级指标是判断履行是否符合约定的重要标准。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:云平台可用性承诺与服务补偿争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_sla_operational_metrics_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal SaaS service level review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_change_order_015",
|
||||
"rule_name": "需求变更、版本迭代与追加费用机制缺失",
|
||||
"contract_scope": ["software_development_agreement", "implementation_service_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["change_management", "pricing", "delivery"],
|
||||
"industry_scope": ["software", "saas", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["需求变更", "版本迭代", "追加费用", "变更单"],
|
||||
"risk_description": "项目类合同未设置变更流程时,口头需求和即时沟通常被视为默认承诺,导致工期、费用和验收标准不断漂移,最终难以区分原合同范围与新增工作。",
|
||||
"review_question": "是否约定变更提出、影响评估、审批权限、生效形式、工期顺延、费用调整和紧急变更的补办流程?",
|
||||
"suggested_fix": "要求任何影响范围、排期、接口、资源或价格的事项均通过书面变更单确认;紧急变更可先执行后补签,但应在短期内完成影响追认。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于合同变更、履行协作与证据留存的一般规则",
|
||||
"reason": "变更管理是认定新增义务和价款调整的核心依据。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:软件定制项目因口头追加需求引发结算争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_change_order_project_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal project change review rule."
|
||||
}
|
||||
},
|
||||
{
|
||||
"rule_id": "rule_cn_subcontracting_016",
|
||||
"rule_name": "分包、转委托或子处理安排未经控制",
|
||||
"contract_scope": ["saas_service_agreement", "data_processing_agreement", "implementation_service_agreement", "ai_service_agreement"],
|
||||
"clause_scope": ["subcontracting", "subprocessor", "data_security"],
|
||||
"industry_scope": ["saas", "software", "ai_data_services"],
|
||||
"severity": "high",
|
||||
"trigger_pattern": ["分包", "转委托", "子处理者", "第三方服务商"],
|
||||
"risk_description": "允许服务方自由分包或接入子处理者而不设准入标准、责任穿透和通知机制时,客户可能丧失对核心交付和数据链路的控制;服务方也可能因上游失误承担不可控违约风险。",
|
||||
"review_question": "是否明确哪些事项可分包、哪些需事先同意、子处理者的安全与保密要求、替换通知义务以及服务方对分包结果承担何种责任?",
|
||||
"suggested_fix": "对核心开发、运维、数据处理等敏感事项设置事先书面同意或白名单机制,并要求分包合同传导保密、安全、审计与删除义务,且服务方对分包商行为承担连带或完全责任。",
|
||||
"legal_basis": [
|
||||
{
|
||||
"law_ref": "《中华人民共和国民法典》合同编关于债务履行辅助人与违约责任的一般规则",
|
||||
"reason": "分包不当然免除原合同义务,责任分配需在合同中明确。"
|
||||
},
|
||||
{
|
||||
"law_ref": "《中华人民共和国个人信息保护法》关于受托处理和再委托的规定",
|
||||
"reason": "涉及个人信息时,子处理链条必须具备可控性和透明度。"
|
||||
}
|
||||
],
|
||||
"case_refs": ["待补充:外包实施商擅自转委托导致项目与数据事故争议案例"],
|
||||
"fallback_clause_ids": ["clause_cn_subcontracting_and_subprocessor_v1"],
|
||||
"source": {
|
||||
"registry_id": "src_internal_authored",
|
||||
"source_type": "internal_authored",
|
||||
"license_note": "Internal subcontracting review rule."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in New Issue
Block a user