20260617:目前有914 页
This commit is contained in:
58
concepts/lifecycle-aware-harness.md
Normal file
58
concepts/lifecycle-aware-harness.md
Normal file
@@ -0,0 +1,58 @@
|
||||
---
|
||||
title: "Lifecycle-Aware Harness(生命周期感知 Harness)"
|
||||
created: 2026-06-11
|
||||
updated: 2026-06-11
|
||||
type: concept
|
||||
tags: [agent, harness, lifecycle, architecture]
|
||||
sources: [raw/papers/xu-life-harness-runtime-adaptation-2026.md]
|
||||
confidence: high
|
||||
---
|
||||
|
||||
# Lifecycle-Aware Harness
|
||||
|
||||
> Life-Harness 的核心架构理念:将 Agent 交互分解为生命周期阶段,每阶段部署专门的接口干预——而非将 Harness 视为单一整体进行优化。
|
||||
|
||||
## 生命周期分解
|
||||
|
||||
传统 Harness 优化(如 Meta-Harness、AHE)将 Harness 视为**自由形式的代码制品**进行搜索或持续编辑。Lifecycle-Aware Harness 则将交互分解为四个明确的阶段:
|
||||
|
||||
```
|
||||
交互前 → 任务条件化时 → 动作执行前 → 执行后
|
||||
❶ ❷ ❸ ❹
|
||||
契约层 技能层 实现层 调控层
|
||||
```
|
||||
|
||||
每层有明确的职责边界:
|
||||
- ❶ 契约层:输出增强后的环境可见契约 C′
|
||||
- ❷ 技能层:从技能记忆库检索相关技能并注入 Prompt
|
||||
- ❸ 实现层:在提交环境前验证动作、阻断无效调用
|
||||
- ❹ 调控层:监控轨迹动态、检测退化、触发恢复
|
||||
|
||||
## 为什么生命周期分解重要
|
||||
|
||||
失败模式与交互阶段高度绑定:
|
||||
- 契约问题 → 在交互开始前就应该解决
|
||||
- 格式问题 → 在动作提交前就应该阻断
|
||||
- 退化问题 → 只有在执行后轨迹中才可检测
|
||||
|
||||
将 Harness 分解为生命周期层意味着:
|
||||
- **精准干预**:每层只处理自己阶段的问题,不干扰其他阶段
|
||||
- **可组合**:各层可独立优化和评估
|
||||
- **可审计**:每层干预的触发条件明确,效果可追踪
|
||||
|
||||
## 与整体式 Harness 优化的对比
|
||||
|
||||
| 维度 | 整体式(Meta-Harness) | 生命周期式(Life-Harness) |
|
||||
|------|----------------------|--------------------------|
|
||||
| 抽象层次 | 自由形式代码 | 结构化接口层 |
|
||||
| 干预粒度 | 全局搜索/编辑 | 阶段特定的固定干预 |
|
||||
| 可解释性 | 低(代码作为整体优化) | 高(每层理由明确) |
|
||||
| 确定领域适用性 | 有限 | 强(利用环境确定性) |
|
||||
|
||||
## 参考
|
||||
- [[xu-life-harness|Life-Harness 论文]]
|
||||
- [[runtime-harness-adaptation|Runtime Harness Adaptation]]
|
||||
- [[environment-contract-layer|环境契约层]]
|
||||
- [[procedural-skill-layer|程序技能层]]
|
||||
- [[action-realization-layer|动作实现层]]
|
||||
- [[trajectory-regulation-layer|轨迹调控层]]
|
||||
Reference in New Issue
Block a user