docs(rfcs): align autonomous managed teams and continuation ownership

[huangruiteng]

Goal And Delivered Outcome

• Goal/source and gap: related to [Roadmap]: LoopX overall delivery program / LoopX 整体路线与交付总跟踪 #4574, especially R2/R3/R6. Existing RFCs distinguish execution modes but need a common contract for an attached or managed lead to coordinate local/cloud workers, including workers that delegate further.
• Before → after: the design now assigns Agent creation/reuse, session lifecycle, continuation, communication and work acceptance to their existing owners. It separates inbox/queue/steer, requires one continuation owner per binding, and makes autonomous hierarchical adoption part of acceptance. The host transports decisions and enforces boundaries; it does not prescribe business phases.
• Intended base: main. This is a design alignment, not implementation or closure of the umbrella issue.

Scope And Continuation

• Updates eight RFC topics across 14 English/Chinese files: overall roadmap, session execution, frontend ingress, semantic handoff, shared authority, harness selection, IM collaboration and local daemon.
• First qualify local/cloud workers against one governed Turn contract. Keep native Goal and same-session drivers as separate profiles; preserve existing defaults and the public LoopX Ark goal_once contract. A cloud governed-Turn adapter remains an unqualified opt-in proposal. No new Ark API guarantee is asserted.
• Require three-level collaboration, two input revisions, Agent-originated replanning, intermediate adoption, independent rejection, bounded shared resources, cancellation and late-result handling. A single local authority with remote execution can advance R2/R3; it does not satisfy distributed G3/R6 or waive D1–D3.
• Complete within the requested RFC scope. Runtime/provider/product qualification remains with the existing R2/R3/R6 work; no parallel task ledger or new milestone is introduced. Keeping this documentation slice separate makes the design reviewable without changing live behavior.
• Future-facing pass: canonicalize operation/continuation rules in the session RFC and delivery rules in the frontend RFC, with links from other owners. No runtime refactor is appropriate to this scope.

Validation

• Tested revision: affd7dd3efcf2c98a526c8d54fa58c6f6cfcbe98
• Run state: finished
• Input classes: public_fixture — checked-in documentation and public source contracts.

Check kind	Result	Public-safe evidence / limitation
static	passed	git diff --check origin/main...HEAD; exactly the 14 intended RFC Markdown paths.
static	passed	loopx check --scan-path … over every changed file: public-boundary scan clean, zero errors. The checker separately reported two unrelated local-state warnings. Added lines were also checked for credential/private-reference patterns.
static	passed	uv run --extra test python examples/docs-governance-smoke.py.
real_entrypoint	passed	uv run --extra test --with-requirements docs/requirements-docs.txt mkdocs build --strict; all 21 new relative links and rendered section anchors resolve. Stable explicit anchors fix the new Chinese cross-links on both rendering paths.
manual	passed	English/Chinese consistency, ownership/default semantics, public Ark host source, current roadmap and main-branch integration reviewed.
integration	not_run	No runtime code, schema, settings or provider behavior changed. Newly specified autonomous-team scenarios remain unqualified.

• Coverage and gaps: document structure, build, new navigation and source boundaries are covered. A broader anchor-log assertion encountered existing site diagnostics; the affected references were verified present in the base revision. The site still emits informational diagnostics for 23 existing anchor references, with none from the new links. No runtime acceptance gate is claimed passed by this PR.

Frontend / Visual Evidence

• UI impact: none — RFC body content and section links only; no frontend code, documentation chrome, first viewport, primary navigation or configuration editor changes.
• Before/after and states/viewports: N/A.
• Source data: none.

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface (README, protocols, dashboard)

Technical Direction

• [Roadmap]: LoopX overall delivery program / LoopX 整体路线与交付总跟踪 #4574 R2/R3/R6; handoff A6/A8/A13; shared-authority qualification gates preserved.

Shared-authority RFC fixture impact

• Design-only clarification; no storage/schema, fixture semantics, provider routing or compatibility projection changes. Provider conformance and legacy/file/PostgreSQL rehearsal are not applicable; no provider promotion or qualification progress is claimed.

Boundary Checklist

• The diff and PR contain no private state, credentials, raw traces, internal links or local machine paths.
• No maintainer-owned benchmark work is duplicated.
• The change remains scoped to the requested RFC alignment.
• UI impact is marked none with a verified reason.
• Every commit includes a DCO Signed-off-by trailer.

[huangruiteng]

Approval conclusion (author-owned PR; GitHub blocks formal self-approval)

动机

这组 RFC 要解决的问题是：#4574（尤其 R2/R3/R6）已经区分了执行模式，但没有一个共同契约说明一个 attached/managed lead 如何协调本地与云端 worker——包括会继续向下委派的 worker。风险很具体：没有"谁是下一次执行机会的 owner"这条轴，就可能把一个自我续跑的 provider 原生 Goal 包在一串外部驱动的 Turn 里，既能重复驱动又能重复计账。

这是一次纯文档对齐（8 对中英镜像，+415/−23，没有碰任何代码、配置或 workflow），并且通篇在说"复用既有的 owner"，而不是提出新机制。

改动思路

• 把三个身份显式分开：注册的 Agent、它当前的 host session/执行代、以及每个工作请求/尝试；并写清"创建 Agent 不等于启动进程，附加 session 不等于认领工作，返回产物不等于被验收"。
• 用一张"操作族 → 复用的既有 owner → 必须观测到什么"的表，给 discover/create/reuse、attach/start/resume/stop、send/receive/return、claim/validate/settle 各指定 owner；明确这是语义操作族，不是新的通用 adapter API。
• 新增续跑归属这条轴（LoopX Turn / 原生 Goal runtime / 同会话 host driver），并禁止"把自我续跑的 Goal 反复包进外部 Turn"；切换 owner 必须停新准入、清点在途工具与不确定副作用、隔离旧执行者、读回新绑定。
• 在 manager handoff RFC 里补"层级委派与自主推进"：lineage 不是 grant、每跳仍在授权与预算内、取消只影响自有后代、等待子节点时要释放执行槽位；并把验收链写成 child artifact → receiver 验证/采纳 → parent 集成 → 原始请求方。

具体改动

关键代码/文档讲解

• agent-session-execution-modes-v0.md(+zh)：新增 ### Reusable Agent operations and continuation ownership；把"经常被混淆的五个轴"改为六个轴，新增 Continuation owner (proposed) 行。
• capable-manager-semantic-handoff-v0.md(+zh)：新增 #### Hierarchical delegation and autonomous progress，并把 A6/A8/A13 的验证要求扩成"三级合成旅程 + 两次输入修订"。
• desktop-execution-frontends / harness-selection / roadmap / openviking-collaboration / shared-goal-authority / single-owner-daemon：各自补一句边界归属，指向上面两处 owner。

我实跑与核对的内容（merged head affd7dd3）

python examples/docs-governance-smoke.py        → docs-governance-smoke ok
python examples/docs-asset-integrity-smoke.py   → ok (6 assets verified, all PNG hashes distinct)
六轴表镜像对齐                                  → EN 6 行 / zh 6 行，属主一致
相对链接锚点扫描（docs/，merged head vs merge-base） → 见下

链接锚点扫描：我把 docs/ 下所有相对 Markdown 链接解析到目标文件，用 GitHub 的锚点生成规则（小写、去标点、空格转 -）核对。结果：merge-base 上有 3 处无法解析（均为既存的 testing-and-quality.md 跨文件锚点），merged head 上有 8 处——新增的 5 处全部来自这次 PR 的中文镜像（详见风险）。

对主干的风险

一条 P2（非阻塞，且只影响中文镜像的导航）：新增的 5 条中文链接指向英文锚点，而这些锚点在中文文件里不可能存在。

具体是：

3 × ](agent-session-execution-modes-v0.zh-CN.md#reusable-agent-operations-and-continuation-ownership)
2 × ](desktop-execution-frontends-v0.zh-CN.md#agent-scoped-bot-ingress-modes)

中文镜像的标题是翻译过的：### 可复用的 Agent 操作与续跑归属、## Agent 级 Bot 入口模式，GitHub 只会生成 #可复用的-agent-操作与续跑归属 / #agent-级-bot-入口模式。英文侧同样的链接是有效的（英文文件里确实有这两个标题），所以这不是"链接写错"，而是"镜像里沿用了英文 fragment"。仓库其余中文链接用的是中文锚点（例如 #57-会话与产品连续性），所以这 5 条也与本地惯例不一致。修法很轻：改这 5 个 fragment，或给中文标题补上英文锚点；英文侧不需要动。代码/契约/默认行为都不受影响，因此不阻塞。

其余核对结果：六轴表在两种语言里都是 6 行且属主一致；新增文字没有与它引用的既有契约冲突；文中对未来工作的描述都显式标为 proposed / 未 qualify（例如"首个混合 managed cohort 需先把云适配器按同一 governed Turn 契约验证"），没有把它读成已交付能力。

我的整体评价

这是"补的是归属而不是功能"的文档改动，方向我认可：把三个身份拆开、给每个操作族指定既有 owner、并把"续跑归属"独立成轴，正好堵住"自我续跑 Goal 被反复包进外部 Turn"这条最容易犯、也最容易在账面上的错误。文字克制（明确说不新增 flag、不迁移默认、不要 manager-only 服务），镜像也保持了结构对齐。

唯一的缺陷在中文镜像的 5 条新链接上：它们指向只在英文文件里存在的锚点，读者点过去会落在文件顶部而不是对应小节。这条不影响任何运行行为，但正好落在这类"中英对照"文档最容易失守的地方，所以记成 P2 并给出最小修法。

English verdict: APPROVE (author-owned PR; published as a COMMENTED review because GitHub blocks formal self-approval) - head affd7dd is a documentation-only alignment across eight RFC pairs (+415/-23, no code or workflow file touched) that separates the registered Agent, its host session/execution generation and each work request, assigns each operation family to an existing owner, adds continuation ownership as a sixth axis with an explicit prohibition on wrapping a self-continuing native Goal in repeated externally driven Turns, and adds a hierarchical-delegation contract where lineage is not a grant and a host cannot certify its own completion; I verified it by running docs-governance-smoke and docs-asset-integrity-smoke (both ok at the merged head), confirming both mirrors carry the same six-row table and sections with consistent owners, and resolving every relative markdown link in docs/ at the merged head against the merge-base; the one P2 non-blocking finding is that five links this PR adds inside the Chinese mirrors reuse English fragments (#reusable-agent-operations-and-continuation-ownership three times, #agent-scoped-bot-ingress-modes twice) that cannot exist in the translated files whose headings are Chinese, so those zh cross-references land at the top of the target document instead of the named section - the English side resolves and the repository's other zh links use Chinese anchors, so the minimal repair is to repoint those five fragments or add matching anchors, which does not block this merge.