204 lines
5.9 KiB
Markdown
204 lines
5.9 KiB
Markdown
|
# 2026-04-03 工作日志
|
|||
|
|
|
|||
|
|
## 今日开发计划
|
|||
|
|
|
|||
|
|
### 今日目标
|
|||
|
|
|
|||
|
|
- ~~分析 `demo/` 下三个 agent 项目与 Jarvis 当前 agents 的差异~~
|
|||
|
|
- ~~明确 Jarvis 2.0 升级方向~~
|
|||
|
|
- ~~建立 development-doc 文档结构~~
|
|||
|
|
- ~~形成分阶段 plan 文档~~
|
|||
|
|
- ~~形成 2 天融合改造计划~~
|
|||
|
|
|
|||
|
|
### 今日计划拆分
|
|||
|
|
|
|||
|
|
1. ~~分析 demo 项目能力与设计重点~~
|
|||
|
|
2. ~~评估 Jarvis 当前 agents 的优势与短板~~
|
|||
|
|
3. ~~输出 Jarvis 2.0 总体升级思路~~
|
|||
|
|
4. ~~建立 `development-doc/plan` 与 `development-doc/daily`~~
|
|||
|
|
5. ~~将 plan 拆成 phase 文档~~
|
|||
|
|
6. ~~输出 2 天融合改造计划~~
|
|||
|
|
|
|||
|
|
### Day 1 工作内容
|
|||
|
|
|
|||
|
|
#### Day 1 目标
|
|||
|
|
|
|||
|
|
- ~~完成 demo 项目分析~~
|
|||
|
|
- ~~完成 Jarvis 当前能力差距判断~~
|
|||
|
|
- ~~完成 `development-doc/` 目录搭建~~
|
|||
|
|
- ~~完成 phase 文档拆分~~
|
|||
|
|
- ~~完成 2 天融合计划初稿~~
|
|||
|
|
|
|||
|
|
#### Day 1 分步骤执行
|
|||
|
|
|
|||
|
|
1. ~~分析 `demo/swarm-ide-chore-specs-mvp`~~
|
|||
|
|
2. ~~分析 `demo/claude-code-cli-master`~~
|
|||
|
|
3. ~~分析 `demo/claw-code-main`~~
|
|||
|
|
4. ~~梳理 Jarvis 当前 agents 架构优势与短板~~
|
|||
|
|
5. ~~输出 `plan/README.md` 与 phase 文档~~
|
|||
|
|
6. ~~输出 `2026-04-03-jarvis-agents-2-day-integration-plan.md`~~
|
|||
|
|
7. ~~建立并整理 `daily/` 日志结构~~
|
|||
|
|
|
|||
|
|
#### Day 1 完成标准
|
|||
|
|
|
|||
|
|
- ~~文档结构齐全~~
|
|||
|
|
- ~~分阶段计划可读~~
|
|||
|
|
- ~~两天改造路线明确~~
|
|||
|
|
- ~~daily 可持续维护~~
|
|||
|
|
|
|||
|
|
> Day 2 内容已拆分到 `daily/2026-04-04.md`
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 今日实际完成
|
|||
|
|
|
|||
|
|
1. 分析了以下 demo 项目：
|
|||
|
|
- `demo/swarm-ide-chore-specs-mvp`
|
|||
|
|
- `demo/claude-code-cli-master`
|
|||
|
|
- `demo/claw-code-main`
|
|||
|
|
|
|||
|
|
2. 梳理了 Jarvis 当前 agent 架构的优势与短板：
|
|||
|
|
- 当前强项：分层路由、业务导向、continuity、fallback、测试基础
|
|||
|
|
- 当前短板：动态协作不足、缺少 verifier、缺少 task/runtime、可观察性不足
|
|||
|
|
|
|||
|
|
3. 输出并整理了 Jarvis 规划文档结构：
|
|||
|
|
- `development-doc/README.md`
|
|||
|
|
- `development-doc/plan/README.md`
|
|||
|
|
- `development-doc/plan/phase-0-current-state-and-target.md`
|
|||
|
|
- `development-doc/plan/phase-1-safe-foundation.md`
|
|||
|
|
- `development-doc/plan/phase-2-controlled-collaboration.md`
|
|||
|
|
- `development-doc/plan/phase-3-dynamic-collaboration.md`
|
|||
|
|
- `development-doc/plan/phase-4-visibility-and-isolation.md`
|
|||
|
|
- `development-doc/plan/2026-04-03-jarvis-agents-2-day-integration-plan.md`
|
|||
|
|
|
|||
|
|
4. 建立并整理了 daily 目录：
|
|||
|
|
- `development-doc/daily/2026-04-03.md`
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 当前进度
|
|||
|
|
|
|||
|
|
### 文档规划进度
|
|||
|
|
|
|||
|
|
- demo 分析：已完成
|
|||
|
|
- 总体升级方向：已完成
|
|||
|
|
- plan 目录搭建：已完成
|
|||
|
|
- 分阶段 plan：已完成
|
|||
|
|
- 2 天融合计划：已完成
|
|||
|
|
- daily 规范：已完成
|
|||
|
|
- Day 3 清单与验收文档：已更新
|
|||
|
|
- Day 4 清单：已更新
|
|||
|
|
|
|||
|
|
### 代码改造进度
|
|||
|
|
|
|||
|
|
- 已完成 Day 1 / Day 2 底座与协作闭环
|
|||
|
|
- 已完成 Day 3 最小受限动态协作 runtime
|
|||
|
|
- 已补齐 registry spawn policy、graph spawn guardrail、message trace、interrupt / recovery 最小闭环
|
|||
|
|
- Phase 1-3 核心功能已基本落地
|
|||
|
|
- Day 4 聚焦 Phase 4 可视化与隔离执行能力
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 今日修改的模块 / 文件
|
|||
|
|
|
|||
|
|
### 新增 / 更新的开发文档
|
|||
|
|
|
|||
|
|
- `development-doc/README.md`
|
|||
|
|
- `development-doc/plan/README.md`
|
|||
|
|
- `development-doc/plan/phase-0-current-state-and-target.md`
|
|||
|
|
- `development-doc/plan/phase-1-safe-foundation.md`
|
|||
|
|
- `development-doc/plan/phase-2-controlled-collaboration.md`
|
|||
|
|
- `development-doc/plan/phase-3-dynamic-collaboration.md`
|
|||
|
|
- `development-doc/plan/phase-4-visibility-and-isolation.md`
|
|||
|
|
- `development-doc/plan/2026-04-03-jarvis-agents-2-day-integration-plan.md`
|
|||
|
|
- `development-doc/daily/2026-04-03.md`
|
|||
|
|
|
|||
|
|
### 本轮补充分析与改造涉及的代码文件
|
|||
|
|
|
|||
|
|
- `backend/app/agents/state.py`
|
|||
|
|
- `backend/app/agents/graph.py`
|
|||
|
|
- `backend/app/agents/prompts.py`
|
|||
|
|
- `backend/app/agents/registry/models.py`
|
|||
|
|
- `backend/app/agents/registry/builtins.py`
|
|||
|
|
- `backend/app/agents/registry/indexes.py`
|
|||
|
|
- `backend/app/agents/tools/__init__.py`
|
|||
|
|
- `backend/tests/backend/app/agents/test_graph.py`
|
|||
|
|
- `backend/tests/backend/app/agents/test_registry.py`
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 今日结论
|
|||
|
|
|
|||
|
|
### 从 demo 项目吸收的核心方向
|
|||
|
|
|
|||
|
|
- 从 Swarm-IDE 学：动态通信原语、可观察性、协作拓扑
|
|||
|
|
- 从 Claude Code CLI 学：coordinator / task / verifier 的平台化编排
|
|||
|
|
- 从 Claw Code 学：runtime 分层、工具注册表、权限模型
|
|||
|
|
|
|||
|
|
### Jarvis 总体升级方向
|
|||
|
|
|
|||
|
|
Jarvis 不应直接变成完全自由的 swarm，而应升级为：
|
|||
|
|
|
|||
|
|
- 受控的动态协作运行时
|
|||
|
|
|
|||
|
|
原则：
|
|||
|
|
|
|||
|
|
- 简单请求继续走当前稳定路径
|
|||
|
|
- 复杂请求才进入协作模式
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 当前阻塞点
|
|||
|
|
|
|||
|
|
- 暂无明显代码层阻塞
|
|||
|
|
- 当前主要待办是完成定向回归测试并收尾验收
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 风险与临时决策
|
|||
|
|
|
|||
|
|
### 当前风险
|
|||
|
|
|
|||
|
|
- 不要一开始就引入无限动态 agent
|
|||
|
|
- 不要直接替换现有 graph 主路径
|
|||
|
|
- 应优先保持 reminder/task/search 等现有业务稳定
|
|||
|
|
- 新能力必须配套测试和约束策略
|
|||
|
|
|
|||
|
|
### 当前决策
|
|||
|
|
|
|||
|
|
1. 采用受限动态协作，而不是自由 swarm
|
|||
|
|
2. 通过 registry 固化 spawn role policy，再由 graph 在运行时执行权限校验
|
|||
|
|
3. interrupt / recovery 先落最小闭环，优先保证 direct 主路径稳定
|
|||
|
|
4. daily 后续必须作为开发过程中的持续更新日志使用
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 验证 / 测试情况
|
|||
|
|
|
|||
|
|
- 已补充 Day 3 相关 runtime / registry / graph 回归测试
|
|||
|
|
- 已更新 Day 3 执行清单与 daily 状态
|
|||
|
|
- 正在执行定向 pytest 验证，重点覆盖 `test_graph.py` 与 `test_registry.py`
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 下一步计划
|
|||
|
|
|
|||
|
|
1. 完成 Day 3 定向回归测试
|
|||
|
|
2. 若有失败，修正 runtime / test 偏差
|
|||
|
|
3. 统一整理 Day 3 最终验收结论
|
|||
|
|
4. 启动 Day 4：Phase 4 可视化 API 实现
|
|||
|
|
5. 设计隔离执行最小方案
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 每日维护要求
|
|||
|
|
|
|||
|
|
后续正式进入改造阶段后，本文件需要持续更新：
|
|||
|
|
|
|||
|
|
1. 开始开发前更新“今日开发计划”
|
|||
|
|
2. 完成一个阶段性步骤后更新“当前进度”
|
|||
|
|
3. 变更方案时更新“风险与临时决策”
|
|||
|
|
4. 出现问题时更新“当前阻塞点”
|
|||
|
|
5. 每次完成验证后更新“验证 / 测试情况”
|
|||
|
|
6. 一天结束前补齐“已完成 / 未完成 / 下一步计划”
|