Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/architecture/rfcs/agent-session-execution-modes-v0.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
the session-ownership decision already described for the Desktop frontend.
Session-ownership and host-admission decisions require maintainer acceptance.
- **Created:** 2026-09-15
- **Last normative revision:** 2026-10-27
- **Last normative revision:** 2026-10-29
- **Implementation baseline:** `6c3da75ca`
- **Related contracts:** [Desktop execution frontends](desktop-execution-frontends-v0.md),
[Single-owner local daemon](single-owner-local-daemon-v0.md),
Expand Down Expand Up @@ -245,6 +245,15 @@ results and controller recovery must retain the original request/attempt and
settlement binding. Until that profile qualifies, existing bindings retain their
current behavior; no implicit conversion or host promotion follows.

For C6/C8's [human interaction during execution](controller-executor-unified-contract-v0.md#human-interaction-during-execution),
keep the controller's conversation queue available while the single admitted
executor works. Questions, proactive reports and previews reuse current session,
audience and delivery bindings; they do not admit another business attempt.
Feedback retains its ordered request revision and actual consumption/adoption
readback across stop, restart and late results. A host unable to support this
concurrency or fencing must expose that limit; existing serialized Chat or a
successful bounded runtime invocation does not qualify the two-session journey.

### Reusable Agent operations and continuation ownership

The existing frontend Goal Chat is the baseline conversational coordinator. The
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
- **作者 / 负责人:** 由维护者指示整理的契约。它把桌面端提案中已有的会话归属决策
抽取并规范化。会话归属与宿主接入决策需要维护者接受。
- **创建日期:** 2026-09-15
- **最近规范性修订:** 2026-10-27
- **最近规范性修订:** 2026-10-29
- **实现基线:** `6c3da75ca`
- **相关契约:** [桌面执行前端](desktop-execution-frontends-v0.zh-CN.md)、
[单属主本地守护进程](single-owner-local-daemon-v0.md)、
Expand Down Expand Up @@ -196,6 +196,13 @@ claim 与完成回执,以及"只有经过验证的回写才推进工作"这一
角色变化、Stop、迟到结果及 controller 恢复须保留原 request/attempt 和结算绑定。
该 profile 合格前,已有绑定行为不变;不隐式转换或提升 host。

对于 C6/C8 的[执行期间人机交互](controller-executor-unified-contract-v0.zh-CN.md#human-interaction-during-execution),
唯一已准入 executor 工作时,controller 的对话队列仍须可用。询问、主动汇报和预览
复用当前会话、受众及投递绑定,不准入另一个业务 attempt。反馈在 Stop、重启和迟到
结果后仍保留有序 request revision 及真实消费/采用 readback。Host 无法支持这种并发
或 fencing 时须明示限制;已有串行 Chat 或一次有界 runtime 调用成功,不能证明双会话
旅程合格。

### 可复用的 Agent 操作与续跑归属

现有前端 Goal 对话是会话型 coordinator 的基线入口。所有者也可以把 peer
Expand Down
13 changes: 12 additions & 1 deletion docs/architecture/rfcs/capable-manager-semantic-handoff-v0.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
- **Supersedes / closes:** [Personal Follow-through independent proposal](personal-follow-through-v0.md)
- **Delivery maturity:** Partial; private runtime profile, team-plan confirmation and Todo materialization shipped; complete M1–M4 remain unqualified.
- **Authors / owners:** LoopX maintainers; manager engineering owner
- **Created / last normative revision:** 2026-09-13 / 2026-10-28
- **Created / last normative revision:** 2026-09-13 / 2026-10-29
- **Implementation baseline:** `7eb4b7bb1661bd5eff63a8725a33169792d5964b`
- **Language mirror:** [中文版](capable-manager-semantic-handoff-v0.zh-CN.md)
- **Related contracts:** [Effect interpreter](agent-loop-effect-interpreter-v0.md), [Manager continuity](../../reference/protocols/manager-evidence-and-continuity-v0.md), [Goal Vision/Replan](../../reference/protocols/goal-vision-replan-contract-v0.md), [Desktop frontends](desktop-execution-frontends-v0.md), [Shared authority](shared-goal-authority-state-provider-v0.md), [Shared Goal alignment/amendment](shared-goal-alignment-and-governed-amendment-v0.md), [TS migration](typescript-control-plane-migration-v0.md)
Expand Down Expand Up @@ -196,6 +196,17 @@ packet view. Runtime-owned routing/revision/attempt metadata reuses these reques
records; it is not another authority or handoff ledger. This does not restrict
independent peer Agents, which retain their own scoped Core relationships.

That profile's C6/C8 [human interaction journey](controller-executor-unified-contract-v0.md#human-interaction-during-execution)
extends semantic return beyond the final answer: converse while work runs,
proactively report meaningful evidence-backed changes and use task-appropriate
rich presentations to help the user judge and correct the work. Reuse existing
request/revision, artifact, audience and delivery owners; preserve quiet and
deduplicated reporting, accessible text and source/version readback. Receipt,
handling and actual feedback adoption remain separate: subsequent work and
artifacts must show adopted revisions, including after reconnect or late results.
No new manager ledger, sending authority or C1 prerequisite follows. Current
progress/steering primitives do not by themselves qualify that concurrent journey.

Prefer one cohesive replacement to compatibility wrappers that preserve duplicate decisions. Inventory every existing producer/reader, migrate with lossless mappings, switch one writer and delete the replaced rules. Reusing contracts and data is required; reusing every current class, JSON directory and prompt is not.

The lead Agent owns task decomposition, investigation, delegation, revision and
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
- **替代 / 关闭:** [个人事项持续跟进独立提案](personal-follow-through-v0.zh-CN.md)
- **交付成熟度:** Partial;私人运行 profile、团队计划确认与 Todo 物化已交付,完整 M1–M4 未验收。
- **作者 / 责任人:** LoopX 维护者、管家工程负责人
- **创建 / 最近规范修订:** 2026-09-13 / 2026-10-28
- **创建 / 最近规范修订:** 2026-09-13 / 2026-10-29
- **实现基线:** `7eb4b7bb1661bd5eff63a8725a33169792d5964b`
- **语言镜像:** [English](capable-manager-semantic-handoff-v0.md)
- **相关契约:** [Effect interpreter](agent-loop-effect-interpreter-v0.zh-CN.md)、[管家连续性](../../reference/protocols/manager-evidence-and-continuity-v0.md)、[Goal Vision/Replan](../../reference/protocols/goal-vision-replan-contract-v0.md)、[桌面入口](desktop-execution-frontends-v0.zh-CN.md)、[共享权威](shared-goal-authority-state-provider-v0.zh-CN.md)、[共享目标对齐/修订](shared-goal-alignment-and-governed-amendment-v0.zh-CN.md)、[TS 迁移](typescript-control-plane-migration-v0.zh-CN.md)
Expand Down Expand Up @@ -162,6 +162,13 @@ flowchart LR
记录,不形成另一套权限或交接账本。独立 peer Agent 仍保留各自受限的 Core 关系,
不受这个同 Agent 内部角色划分限制。

该 profile 的 C6/C8 [人机交互旅程](controller-executor-unified-contract-v0.zh-CN.md#human-interaction-during-execution)
把语义返回延伸到最终答案之前:执行中可交流,主动报告有证据的实质变化,按任务选择
丰富展现以帮助用户判断和纠偏。复用既有 request/revision、产物、受众和投递 owner,
保留安静与去重汇报、可访问文本和来源/版本 readback。收到、处理与反馈实际采用分别
记录;重连或迟到结果之后,后续工作和产物仍须证明已采用修订。不新增管家账本、发送
权限或 C1 前置;现有 progress/steering 原语不能单独证明这条并发旅程合格。

优先一次内聚替换,不用兼容包装长期保留两套判断。盘点所有 producer/reader,无损迁移、切换单 writer、删除被替代规则。必须复用有效契约和数据,不必复用每个类、JSON 目录和 prompt。

主 Agent 负责拆解、调查、委派、修订和综合;host 服务执行已准入动作并恢复其回执,
Expand Down
Loading
Loading