loopx-project · huangruiteng · Sep 20, 2026 · Sep 19, 2026 · Sep 19, 2026
@@ -287,6 +287,15 @@ changes.
     Lark operation cards. Direct Goal workspace navigation and Overview compose
     bounded graph/acceptance readback, source navigation and snapshot export. General cross-channel disclosure,
     living documents and governed amendment/settlement review remain open.
+- [Live Team Workspace v0](live-team-workspace-v0.md)
+  ([中文版](live-team-workspace-v0.zh-CN.md))
+  - **RFC status:** Draft presentation slice under intelligent presentation.
+  - **Delivery on `main`:** Design proposal only; no live team-stream qualification.
+  - **Current boundary:** A command surface plus spatial research studio, evidence
+    handoff motion, conclusion revision and replay. L1 requires one real
+    objection→revision→acceptance→adoption journey with evidence and intervention/stop
+    feedback in packaged UI; L2 requires original-coordinator two-cycle acceptance;
+    L3 qualifies semantic zoom and display scale. No new scheduler or authority.
 - [Human Attention Wishlist v0](human-attention-wishlist-v0.md)
   ([中文版](human-attention-wishlist-v0.zh-CN.md))
   - **RFC status:** Draft, under maintainer review.

@@ -673,6 +673,18 @@ canonical facts, authority, evidence status, or whether an effect committed.
 Adaptive policies must be inspectable and resettable. Their outputs carry
 reason codes and preserve a deterministic fallback.
 
+### 8.7 Live team workspace
+
+[Live Team Workspace v0](live-team-workspace-v0.md) specifies the S5/R2 research
+journey: a command surface and spatial studio share typed facts with the list,
+semantic zoom and historical replay. Purposeful motion is a product objective;
+registration, execution, return, independent acceptance and requester adoption
+remain distinct. Preserve source/revision lineage and uncertainty; never infer
+activity from decorative motion or confidence from agreement counts. This is a
+Draft presentation slice, not a shipped team stream or new scheduling authority.
+Its L1–L3 plan and V1–V7 acceptance extend this RFC's Stage 3 presentation journey;
+they do not close cross-channel or governed settlement acceptance here.
+
 ## 9. Coverage across the long-horizon lifecycle
 
 | Phase | Intelligent surface responsibility |

@@ -551,6 +551,15 @@ type PresentationArtifactPlan = {
 
 Adaptive policy 必须 inspectable、resettable，其输出携带 reason codes，并始终保留 deterministic fallback。
 
+### 8.7 团队实时工作区
+
+[团队实时工作区 v0](live-team-workspace-v0.zh-CN.md) 描述 S5/R2 投研旅程：
+指挥台与空间工作室同列表、语义缩放和历史回放共用 typed 事实。有目的的动态
+是产品目标；注册、执行、返回、独立验收与请求方采用保持分离。保留来源 / 版本
+谱系和不确定性，不能由装饰动态推断活动或由共识人数推断置信度。这是 Draft
+展示切片，不是已交付的团队流，也不新增调度权限。其 L1–L3 计划与 V1–V7 验收
+展开本 RFC Stage 3 的展示旅程，不关闭本文跨渠道或受治理 settlement 验收。
+
 ## 9. 覆盖长程工作的完整生命周期
 
 | 阶段 | 智能化界面的职责 |

@@ -39,7 +39,7 @@ P0 blocks correctness or continuity in the current user journey. P1 enables repe
 | **S2 Typed kernel and durable authority · P0/P1** | Effect/Todo/quota/recovery owners, TS migration and store candidates exist; writer cutover/provider promotion remain incomplete | Migrate one real transaction/recovery lifecycle at a time, with semantic counterexamples before cutover/deletion. R1 correctness precedes migration volume. Require real backend, concurrency/fence, ambiguous commit, retention/export recovery, bridge costs and D1–D3 evidence |
 | **S3 Goal planning and multi-Agent collaboration · P0/P1** | Vision/replan, peer frontiers, claim/lease, directory, manager_context and explicit continuation exist; general handoff/shared amendment remain incomplete | R2 proves peer dependency; R3 closes parallel joins, pipelines, help/review, continuation and automatic return; R4 delivers one intent-preserving amendment class. Cover cycles, invalidated inputs, rejection/deferral, lease transfer, competing bases and aggregate acceptance |
 | **S4 Runtime/host/daemon · P0/P1** | Attached/managed, Turn, broker, runtime connectors and Desktop repairs exist; registration does not establish executable capacity | Qualify multi-Turn supervision for one real supported combination; restart/cancel/drain/stop retain work and fence old executors. Then expand host parity, unique service-profile ownership, clean installation and upgrades; show unsupported adapter capabilities |
-| **S5 Frontend, Lark and human interaction · P0/P1** | Local chat, settings, proposals and partial Goal Channel verticals exist; shared audience/session/work readback needs qualification | One journey spans settings, work graph, handoff, blockers, cost, corrections, artifacts and return. Shared typed projections; reconnect/repeated-click/stale/original-route cases. Then intelligent review, keyboard accessibility, bilingual terminology, actionable errors and offline degradation; interrupt only for actual decisions |
+| **S5 Frontend, Lark and human interaction · P0/P1** | Local chat, settings, proposals and partial Goal Channel verticals exist; shared audience/session/work readback needs qualification | One journey spans settings, work graph, handoff, blockers, cost, corrections, artifacts and return. Shared typed projections; reconnect/repeated-click/stale/original-route cases. [Live team workspace](live-team-workspace-v0.md) makes exchange, revision and original-coordinator continuation visible. Then intelligent review, keyboard accessibility, bilingual terminology, actionable errors and offline degradation; interrupt only for actual decisions |
 | **S6 Materials, evidence, memory and learning · P1** | Authority registry, material lifecycle/frontier, decision context, reward memory and turn recall exist; direction baseline and parts of attribution remain proposed | Connect material revision→same-Agent read→decision reference→artifact/outcome. Expose expiry/revocation/source loss and forgetting policy. Handoff preserves decision-relevant summaries and authorized artifacts; qualify OpenViking/Obelisk as optional providers. Prove causal utility with controls, not relevance alone |
 | **S7 Budget, scheduling and fleet scale · P0 observation/P1–P2 expansion** | Quota/scheduler and partial usage aggregates exist; full provider cost, distributed reservations and hundred-Agent concurrency need evidence | Separate configured budget, admission, consumption and estimates; unknown is not zero and replay cannot double-charge. R7 pagination/bounded summaries, provider/host limits, fairness, backpressure, event wake and isolation; report registration/activity/throughput and cost per accepted outcome separately |
 | **S8 Capabilities, extensions and domain integration · P1/P2** | Capability catalog, extension lifecycle, hooks, engineering/research/content/office capabilities and computer-use contracts exist | First exercise the shared control plane with existing issue-fix/PR-review and material/research callers. Every provider has readiness/version/permissions/default-off/uninstall/rollback/isolation and real-entry evidence. New domain effects start with one simulated operation, not a marketplace or workflow DSL |
@@ -295,6 +295,20 @@ This qualifies a local execution-facts readback, not the full R2 ladder: assignm
 receipt integration, provisioning, remote probes, two-cycle continuation and Lark
 qualification remain open under their existing owners.
 
+**Live team experience is a core S5 outcome.** The [Live Team Workspace
+RFC](live-team-workspace-v0.md) joins a precise command surface with a spatial
+research studio: visible artifact exchange, sourced disagreement, conclusion
+revision, replay and semantic zoom. It is a presentation slice of existing
+owners, not a second orchestrator. The next complete frontend slice connects
+one real objection→revision→independent acceptance→requester adoption episode
+to the packaged workspace, with inspectable evidence, intervention/stop feedback,
+independent CLI readback and honest degraded states.
+Then qualify the original research coordinator through the same two real cycles
+required above. Existing runtime admission/provider repairs retain their owner;
+a synthetic scene is not readiness evidence. Expand display load 10→30→100 only
+under frozen rendering/attention budgets, separately from live R7 concurrency.
+Current status is design proposal; no G1 or default-screen promotion.
+
 ### R3: Semantic Requests and Automatic Return
 
 - **Owner:** manager RFC M2/M3; migrate existing `manager_context` request/tracking/return into one typed collaboration transaction, incorporating the #4094 adapter.

@@ -39,7 +39,7 @@ LoopX 的目标是让人用本地前端或 Lark 提出、修订和验收复杂
 | **S2 typed 内核与 durable authority · P0/P1** | Effect/Todo/quota/recovery owner、TS 事务迁移与 store 候选已存在；writer 和 provider 晋升仍未全闭合 | 每次迁移一个真实事务/恢复生命周期，先语义反例再切换/删除旧 owner；R1 正确性先于迁移数量。真实 backend、并发/fence、ambiguous commit、保留/导出恢复、bridge 成本及 D1–D3 资格 |
 | **S3 目标规划与 multi-Agent 协作 · P0/P1** | Vision/replan、peer frontier、claim/lease、directory、manager_context 和显式接续有基础；通用 handoff/共享修订未闭环 | R2 必须证明 peer 依赖；R3 完成并行汇合、流水线、求助/复核、接续、自动回报；R4 做一个保持 intent 的 amendment class。检查依赖环、输入失效、拒绝/延期、lease 转移、同基线竞争及 aggregate acceptance |
 | **S4 runtime/host/daemon · P0/P1** | attached/managed、Turn、broker、runtime connector 和 Desktop 修复存在；“registered”不等于可执行 | 选择一个真实合格组合完成多 Turn supervision；restart/cancel/drain/stop 不丢工作且旧 executor 被 fence。之后扩 host parity、service-profile 唯一 owner、干净安装与版本升级；按 adapter 能力显示不支持项 |
-| **S5 前端、Lark 与人机交互 · P0/P1** | 本地对话、settings、proposal 和部分 Goal Channel vertical 已有；统一受众/会话/工作回读仍需资格 | 用一个团队旅程贯穿设置、工作图、handoff、阻塞、成本、修订、产物和回报；共享 typed projection，验证重连/重复点击/stale/原路反馈。再做 intelligent review、无障碍键盘流程、中英术语、错误可恢复和离线降级；只在真实决策处打断人 |
+| **S5 前端、Lark 与人机交互 · P0/P1** | 本地对话、settings、proposal 和部分 Goal Channel vertical 已有；统一受众/会话/工作回读仍需资格 | 用一个团队旅程贯穿设置、工作图、handoff、阻塞、成本、修订、产物和回报；共享 typed projection，验证重连/重复点击/stale/原路反馈。再做 intelligent review、无障碍键盘流程、中英术语、错误可恢复和离线降级；只在真实决策处打断人；[团队实时工作区](live-team-workspace-v0.zh-CN.md)让交换、修订与原协调员继续推进可见 |
 | **S6 材料、证据、记忆与学习 · P1** | authority registry、material lifecycle/frontier、decision context、reward memory、turn recall 已有；方向基线和部分归因仍是提案 | 先打通“材料 revision→同 Agent 阅读→决策引用→产物/结果”；失效、撤销、来源消失与遗忘策略可回读。handoff 保存影响决策的摘要与授权 artifact；OpenViking/Obelisk 按可选 provider 资格化。utility 的因果收益另以对照证明，不把相关性当提升 |
 | **S7 预算、调度与 fleet 规模 · P0 观测/P1–P2 扩展** | quota/scheduler 与部分 usage aggregate 存在；全 provider 成本、分布式资源预留及百 Agent 并发尚需证据 | 先区分配置预算、准入、消耗与估算；未知成本不记零、重复事件不双记。R7 分页/有界摘要、provider/host 限流、公平性、背压、事件唤醒与失败隔离；分别报告注册数/活跃数/吞吐量和每个验收成果成本 |
 | **S8 能力、扩展与领域集成 · P1/P2** | 已有 capability catalog、extension 生命周期、hook、工程/研究/content/office 能力及 computer-use 合同 | 优先用现有 issue-fix/PR-review 和材料/研究 caller 检验共享控制面；每个 provider 带 readiness、版本、权限、默认关闭、卸载/回滚、失败隔离与真实入口证据。新 domain effect 从模拟单操作闭环开始，不先建市场或通用工作流 DSL |
@@ -272,6 +272,15 @@ executor/profile 检查启动条件。任务准入、当前 pinned 验收绑定
 检查，不新增状态账本，也不启动执行。这只验收本地执行事实的读回；计划分配回执
 整合、通用创建、远端探针、两轮持续协作及 Lark 等价仍由原 owner 继续推进。
 
+**团队现场是 S5 核心产品目标。** [团队实时工作区 RFC](live-team-workspace-v0.zh-CN.md)
+融合精确指挥台与空间研究工作室：展示产物交换、有来源的分歧、结论修订、回放与
+语义缩放。它复用既有 owner，不建立第二套编排。下一完整前端切片在打包工作区
+呈现一次真实异议→修订→独立验收→请求方采用，提供可检查证据、干预 / 停止
+反馈、独立 CLI 回读与真实降级状态；随后按上述标准验收原投研 coordinator 的两轮真实协作。既有 runtime
+准入 / provider 修复保留原 owner；合成场景不能充当 readiness 证据。展示负载
+10→30→100 在测前冻结渲染 / 注意力预算，和 R7 实际并发分开资格化。当前为设计
+提案，不晋升 G1 或默认首屏。
+
 ### R3：语义请求与自动回报
 
 - **Owner：** 管家 RFC M2/M3；从已有 `manager_context` request/tracking/return 迁移到单一 typed collaboration 事务，纳入 #4094 adapter。