42 lines
1.7 KiB
Markdown
42 lines
1.7 KiB
Markdown
---
|
||
title: "Model Proposes, Harness Executes"
|
||
created: 2026-06-29
|
||
updated: 2026-06-29
|
||
type: concept
|
||
tags: [harness-engineering, safety, principle, agent]
|
||
sources: [[prompt-to-loop-engineering-2026]]
|
||
confidence: high
|
||
---
|
||
|
||
# Model Proposes, Harness Executes
|
||
|
||
> [[harness-engineering|Harness Engineering]] 八条非妥协原则之首：模型仅负责**提议**，Harness 才拥有**最终执行权**。
|
||
|
||
## 八条非妥协原则
|
||
|
||
1. **Model proposes — Harness executes**：模型提议，Harness 执行
|
||
2. **Every call returns a result**：即使超时或拒绝，也必须结构化回传
|
||
3. **Risk changes the process**：按风险动态匹配只读/草稿/外部写入三档权限
|
||
4. **Draft 与 Commit 分离**：危险操作必须由人类显式确认
|
||
5. **Context is assembled, not dumped**：上下文分层装配，不能直接倾倒
|
||
6. **Long tasks have budgets**：从步数、时间、Token、成本四维卡死预算
|
||
7. **Skills & Connectors 渐进式披露**：先暴露名称，按需加载细节
|
||
8. **Recurring failures become Harness features**：重复偶发错误沉淀为 Hook 或校验器
|
||
|
||
## 信任边界
|
||
|
||
物理基础设施 → 安全沙箱 → Agent Harness → 运行时 → **模型**（最不可信的内核）。
|
||
|
||
模型执行的每个高风险动作必须经过外围 Harness 规则的解析与沙箱隔离。
|
||
|
||
## 反面案例
|
||
|
||
2026 年 DataTalks.Club 事故：Claude Code 执行 `terraform destroy`，因 Harness 缺位（无二次确认、无基础设施红线、无 Human-in-the-Loop），生产数据库、集群及备份被物理抹除。
|
||
|
||
## 相关概念
|
||
|
||
- [[harness-engineering|Harness Engineering]]
|
||
- [[skill-issue-framework|Skill Issue 框架]]
|
||
- [[human-in-the-loop|Human-in-the-Loop]]
|
||
- [[circuit-breaker-pattern|熔断器]]
|