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
8 changes: 8 additions & 0 deletions docs/architecture/rfcs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -254,6 +254,14 @@ Paired diffs do not certify translation accuracy.
governed commit policy/verifier, lease-impact handling and Stage 3+
qualification remain unshipped. Manager handoff consumes these boundaries;
it does not provide another amendment writer.
- [Goal contract evolution and bounded working context v0](goal-contract-evolution-v0.md)
([中文版](goal-contract-evolution-v0.zh-CN.md))
- **Delivery on `main`:** Proposal only; existing objective revision and additive
outcome maintenance remain the implemented boundary.
- **Current boundary:** One authorized change set for objective and requirements,
retained version history, scoped peer adoption and bounded indexed context.
R4/R5 own migration; real model recognition, packaged recovery, shared-store
concurrency and outcome/cost qualification remain open.
- [Persistent Goal outcome refinement v0](goal-outcome-refinement-v0.md)
([中文版](goal-outcome-refinement-v0.zh-CN.md))
- **Current boundary:** Supporting outcomes preserve cumulative requirements
Expand Down
3 changes: 2 additions & 1 deletion docs/architecture/rfcs/STATUS.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ appendix may keep dated history, but no dated log heading may precede it.

[中文版](STATUS.zh-CN.md) is the semantic mirror of this file.

## Accepted (50)
## Accepted (51)

| RFC | Header status | Supersedes / closes | Ledger |
| --- | --- | --- | --- |
Expand All @@ -38,6 +38,7 @@ appendix may keep dated history, but no dated log heading may precede it.
| [RFC: Frontier Science Research Program v0](frontier-science-research-program-v0.md) | Accepted | none | — |
| [RFC: Goal Artifact Lifecycle Projection (milestone / guard / next-transition) v0](goal-artifact-lifecycle-projection-v0.md) | Accepted | none | — |
| [RFC: Goal Channel Collaboration v0](goal-channel-collaboration-v0.md) | Accepted | none | — |
| [RFC: Goal contract evolution and bounded working context (v0)](goal-contract-evolution-v0.md) | Accepted | none | — |
| [RFC: Goal Direction Baseline (v0)](goal-direction-baseline-v0.md) | Accepted | none | — |
| [Design follow-up: Goal continuity across restart and replacement](goal-immutability-coherence-defense-v0.md) | Accepted | none | — |
| [Goal Instance Identity and Orphan Recovery (v0)](goal-instance-identity-and-orphan-recovery-v0.md) | Accepted | none | — |
Expand Down
3 changes: 2 additions & 1 deletion docs/architecture/rfcs/STATUS.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@

[English](STATUS.md) 与本文互为语义镜像。

## 已接受 (50)
## 已接受 (51)

| RFC | 头部状态 | 替代 / 关闭 | Ledger |
| --- | --- | --- | --- |
Expand All @@ -35,6 +35,7 @@
| [RFC:前沿科学研究计划 v0](frontier-science-research-program-v0.zh-CN.md) | 已接受 | 无 | — |
| [RFC:Goal Artifact 生命周期投影(milestone / guard / next-transition)v0](goal-artifact-lifecycle-projection-v0.zh-CN.md) | 已接受 | 无 | — |
| [RFC: Goal Channel 协作模型 v0](goal-channel-collaboration-v0.zh-CN.md) | 已接受 | 无 | — |
| [RFC:Goal 契约演化与有界工作上下文(v0)](goal-contract-evolution-v0.zh-CN.md) | 已接受 | 无 | — |
| [RFC:Goal Direction Baseline(目标方向基线)v0](goal-direction-baseline-v0.zh-CN.md) | 已接受 | 无 | — |
| [后续设计:重启与实例替换中的 Goal 连续性](goal-immutability-coherence-defense-v0.zh-CN.md) | 已接受 | none | — |
| [Goal 实例身份与孤儿状态恢复(v0)](goal-instance-identity-and-orphan-recovery-v0.zh-CN.md) | 已接受 | 无 | — |
Expand Down
385 changes: 385 additions & 0 deletions docs/architecture/rfcs/goal-contract-evolution-v0.md

Large diffs are not rendered by default.

295 changes: 295 additions & 0 deletions docs/architecture/rfcs/goal-contract-evolution-v0.zh-CN.md

Large diffs are not rendered by default.

11 changes: 11 additions & 0 deletions docs/architecture/rfcs/goal-outcome-refinement-v0.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,17 @@ An outcome is useful when it has a separately recognizable result and criteria,
especially across multiple turns, tasks or repeated user corrections. Do not
promote every message, housekeeping action or intermediate step.

## Evolution beyond additive refinement

[Goal contract evolution](goal-contract-evolution-v0.md) defines the next R4/R5
proposal: unify operating-objective and requirement changes, retain exact prior
versions, separate applicability from satisfaction, and provide bounded working
context over scalable canonical records. It also qualifies whether a model
recognizes a natural correction and adopts it in subsequent work. This extends
the existing acceptance/amendment owners; it does not replace today's additive
operation, capacity limits or full-context obligations before migration qualifies.
Vision remains a route checkpoint, never fallback acceptance after a failed save.

## Ordinary user messages

<a id="current-operating-objective"></a>
Expand Down
8 changes: 8 additions & 0 deletions docs/architecture/rfcs/goal-outcome-refinement-v0.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,14 @@
重要性本身不要求另开运行实例。跨轮次、任务或反复纠正、且有独立结果与条件的
工作适合登记成果;普通消息、维护动作和中间步骤不应全部升级为成果。

## 从只增细化走向演化

[Goal 契约演化](goal-contract-evolution-v0.zh-CN.md)定义下一步 R4/R5 提案:统一
当前目标与要求变更,保留精确旧版本,区分适用性与满足情况,在可扩展 canonical
记录之上提供有界工作上下文。同时验证模型能否从自然纠正识别变化并落实到后续
工作。它扩展既有验收/修订 owner;迁移合格前不替换当前只增操作、容量上限或
完整上下文义务。Vision 仍是路线检查点,保存失败后不能成为备用验收。

## 普通用户消息

<a id="current-operating-objective"></a>
Expand Down
2 changes: 2 additions & 0 deletions docs/architecture/rfcs/loopx-overall-roadmap-v0.md
Original file line number Diff line number Diff line change
Expand Up @@ -620,6 +620,7 @@ subsystem was not performed. Section 8 records the focused audit.
| [Semantic Vocabulary Convergence and Commit-Time Drift Checks (v0)](semantic-vocabulary-convergence-v0.md) | S2 | Accepted; registry/inventory/drift and subsequent typed slices exist | P1: converge by semantic role and active producer/consumer; no name-based enum merging; review schema changes separately |
| [LoopX Shared Control-Plane Authority and Pluggable State Providers (v0)](shared-goal-authority-state-provider-v0.md) | S2/S3/S7 | Accepted; stores, local transactions and service-admission foundations exist | P1→P2: R5 local D1–D3, R6 authenticated hosts; real backend/soak/recovery before promotion |
| [Shared Goal Alignment and Governed Amendment Protocol (v0)](shared-goal-alignment-and-governed-amendment-v0.md) | S3 | Accepted; Stage 1/2 and bounded local root/template commit; generic adoption incomplete | P1: #3836 governed acceptance amendments and peer adoption; R4 CAS/lease impact, conflicts and lost-response receipts |
| [Goal contract evolution and bounded working context v0](goal-contract-evolution-v0.md) | S3/S5/S6/S7 | Proposal; objective revision and additive outcomes remain separate on main | R4/R5 M1: full-Goal correction with exact retention, bounded complete reads and packaged recovery; M2 unified changes/peer adoption; S11 and R6/R7 qualify behavior, shared authority and complete cost |
| [Goal Direction Baseline (v0)](goal-direction-baseline-v0.md) | S3/S6 | Accepted; material read-model proposal | P1: #2831 direction-material revision to acceptance basis linkage; same-Agent/current-revision fixtures |
| [Goal Artifact Lifecycle Projection (milestone / guard / next-transition) v0](goal-artifact-lifecycle-projection-v0.md) | S3/S5 | Accepted; read-model proposal | P1: derive milestone/guard/next transition from typed facts; no process engine |
| [Capable Agent Manager and Semantic Work Handoff (v0)](capable-manager-semantic-handoff-v0.md) | S1/S3 | Accepted; shared request assessment/Core-link context and scoped worker linking qualified; M1–M4 not fully qualified | P0→P1: owner → steward → managed Agent authority inheritance, receiver-owned planning, actual work and original-route return in R1/R2 real teams and R3; continuation matrix and A1–A20. An authorized steward group retains its owner's managed read/effect scope; do not reduce it merely because the entrypoint is external |
Expand Down Expand Up @@ -1214,6 +1215,7 @@ original-route completion. Those remain the same R3 acceptance gates above.
- **Work versus obligations:** follow [alignment RFC §3.7](shared-goal-alignment-and-governed-amendment-v0.md#37-current-work-and-goal-requirements). Keep stable criterion identity and coverage across replan, compaction, restart and Agent handoff; allow only authorized, recorded amendments to change the commitment. Reuse the existing Goal acceptance and Todo owners through R5. Validate evidence content, scope and freshness before global closeout; a local `no_followup` is insufficient. This remains open beyond the shared Goal/current-work read prerequisite; S11 owns qualification of actual model adoption.
- **Outcome continuity slice:** [default refinement and review](goal-outcome-refinement-v0.md) retains original intent and cumulative requirements, reuses inline work context and batches changed evidence into normal writeback. Existing replan receives uncovered requirements; local reviews never change root stop/budget authority. The rebased foundation composes acceptance/ACK compatibility with configured checks, cumulative outcomes and uncovered-outcome replanning. External-worker attempt deduplication and Explore method selection retain their separate owners. Additive File/SQLite and packaged UI qualification is separate from S11 model adoption and matched EdgeBench benefit; no experiment is launched here.
- **Stale operating objective:** [owner revision and peer adoption](goal-outcome-refinement-v0.md#current-operating-objective) adds an Agent-prepared, owner-applied revision through existing Goal update and acceptance transport. Canonical context supersedes stale source display; peers reconcile independently before new execution while in-flight recovery remains available. Original commitments and protected amendment authority remain intact. Scripted CLI/native tools and real-store qualification do not establish model recognition or installed/live collaboration.
- **Unified contract evolution:** [Goal contract evolution](goal-contract-evolution-v0.md) unifies operating-objective and requirement changes through existing R4 authority, with exact history, governed replacement/withdrawal, affected-peer adoption and R5 indexed storage. M1 must let a full Goal retain a new correction through CLI/native tools and packaged App recovery; M2 qualifies coupled changes and peer return; S11 measures natural-trigger recognition and subsequent outcomes. This is a proposal, not a cap increase, a new authority or a claim that tools are used merely because they exist.
- **Owner:** alignment RFC Stage 3–5 and TS Goal/work-graph owners.
- **First correction:** `intent_basis` remains the existing source-facts digest. Preserve compatible readers; introducing a real intent revision requires versioning and producer/reader inventory. Renaming cannot give historical receipts stronger semantics.
- **Order:** establish root intent/permissions/acceptance/stop authority, then one intent-preserving work-graph commit class. Ordinary Todo edits retain existing owners; do not require amendment for every add. Changes to shared commitments consume scoped policy, required verifier, exact CAS and lease-impact disposition.
Expand Down
2 changes: 2 additions & 0 deletions docs/architecture/rfcs/loopx-overall-roadmap-v0.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -467,6 +467,7 @@ Muse 设计页在浏览器超时,其文章通过网页检索读取。本次调
| [Semantic Vocabulary Convergence and Commit-Time Drift Checks (v0)](semantic-vocabulary-convergence-v0.zh-CN.md) | S2 | 已接受;registry/inventory/drift 与后续 typed 切片存在 | P1:按语义角色收敛 vocabulary;盘点真实 producer/consumer;不凭枚举同名合并,schema 改动单独审阅 |
| [LoopX Shared Control-Plane Authority and Pluggable State Providers (v0)](shared-goal-authority-state-provider-v0.zh-CN.md) | S2/S3/S7 | 已接受;store、局部事务和 service admission 基础已存在 | P1→P2:R5 本地 D1–D3;R6 认证跨 host;真实 backend/soak/恢复资格后才晋升 |
| [Shared Goal Alignment and Governed Amendment Protocol (v0)](shared-goal-alignment-and-governed-amendment-v0.zh-CN.md) | S3 | 已接受;Stage 1/2 与有界本地 root/template commit,通用采纳未闭合 | P1:R4 一个 work-graph amendment class;CAS/lease impact、冲突及丢响应回执 |
| [Goal 契约演化与有界工作上下文 v0](goal-contract-evolution-v0.zh-CN.md) | S3/S5/S6/S7 | 提案;main 的目标修订与只增成果仍分离 | R4/R5 M1:已满 Goal 接收纠正、精确保留、有界完整读取及打包恢复;M2 统一变更/peer 采用;S11、R6/R7 验行为、共享权威及完整成本 |
| [Goal Direction Baseline (v0)](goal-direction-baseline-v0.zh-CN.md) | S3/S6 | 已接受;只读设计 | P1:合成 fixture 验同 Agent/current revision 的材料阅读;不写 Vision、不自动建 Todo |
| [Goal Artifact Lifecycle Projection (milestone / guard / next-transition) v0](goal-artifact-lifecycle-projection-v0.zh-CN.md) | S3/S5 | 已接受;只读设计 | P1:从现有 typed facts 显示 milestone/guard/next transition;不加流程引擎 |
| [Capable Agent Manager and Semantic Work Handoff (v0)](capable-manager-semantic-handoff-v0.zh-CN.md) | S1/S3 | 已接受;共享请求评估/Core 链接上下文与沙盒关联工作已验证,M1–M4 未完整验收 | P0→P1:R1/R2 真实团队及 R3 验证接收方采用、实际工作与原路回传;接续矩阵及 A1–A20 |
Expand Down Expand Up @@ -845,6 +846,7 @@ Lark 传输 owner,本切片不再重复修改它。
- **当前工作与完整义务:** 遵循 [alignment RFC §3.7](shared-goal-alignment-and-governed-amendment-v0.zh-CN.md#37-当前工作与-goal-要求)。跨重规划、压缩、重启和 Agent 交接保留 criterion 身份与覆盖关系;只有授权且留痕的 amendment 可改变承诺。经 R5 复用既有 Goal acceptance 与 Todo owner。全局收口前验证证据内容、范围和时效,局部 `no_followup` 不足以结清目标。共享 Goal/当前任务读取前置之外的部分仍未完成;模型实际采用的资格归 S11。
- **成果连续性切片:** [默认细化与自查](goal-outcome-refinement-v0.zh-CN.md) 保留原始意图和累计要求,复用内联工作上下文,把有变化的证据合并进正常写回。未覆盖要求进入现有 replan,局部自查不改变根目标停止/预算权威。Rebase 后的基础组合验收/ACK 兼容、已配置检查、累计成果与未覆盖成果重规划;外部 worker 尝试去重及 Explore 方法选择仍由各自 owner 负责。只增式 File/SQLite 与打包 UI 验证,同 S11 模型采用及匹配 EdgeBench 收益分开记录;这里不发起实验。
- **执行目标过期:** [owner 修订与逐 Agent 采用](goal-outcome-refinement-v0.zh-CN.md#current-operating-objective) 复用 Goal update 和验收传输,由 Agent 准备、owner 应用。Canonical 上下文优先于旧文件展示;各 Agent 在新执行前独立对齐,在途恢复保留。原始承诺及受保护修改权限不变。脚本 CLI/原生工具和真实存储验证不代表模型识别能力、已安装宿主或线上协作已验收。
- **统一契约演化:** [Goal 契约演化](goal-contract-evolution-v0.zh-CN.md)在既有 R4 权威下统一当前目标与要求变更,保留精确历史、受治理替换/撤回、受影响 peer 采用,并衔接 R5 索引存储。M1 须让已满 Goal 通过 CLI/原生工具和打包 App 恢复路径保留新纠正;M2 验证关联变更及 peer 返回;S11 测自然触发识别和后续成果。它是提案,不提高上限、不增权威,也不因工具存在就声称模型会用。
- **Owner:** alignment RFC Stage 3–5;TS Goal/work-graph owner。
- **先收口:** `intent_basis` 仅是现有 source-facts digest;保留兼容 reader,真正引入 intent revision 时单独版本化并盘点 producer/reader。不得改名后假装历史回执拥有新语义。
- **交付次序:** 明确 root intent/permissions/acceptance/stop 的 authority;先做保持 intent 的一个 work-graph commit class。普通 Todo 编辑仍走现有 owner,不能给每次 add 强加 amendment 流程。跨共享承诺修改才消费有范围 policy、必要的 verifier、精确 CAS 与 lease-impact disposition。
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -366,6 +366,15 @@ general supersession, global closeout, cross-Agent reassignment and S11 model/
benchmark adoption remain open. This is a disclosed default guidance change,
not qualification of the complete R4 contract.

The [Goal contract evolution proposal](goal-contract-evolution-v0.md) composes
operating-objective revision and supporting requirement evolution under these
same owners. A source-bound change set retains original intent and version
history, validates each effect's authority, publishes coupled changes atomically,
and identifies affected peers without a unanimous barrier. Record storage and
bounded decision context follow that semantic boundary. Current local template
commit remains narrower; this proposal neither enables general supersession nor
proves model use. Its E1–E9 and M1–M3 refine R4/R5's existing acceptance work.

### 3.8 Invalid evidence and affected consumers

Recovery and work switching must preserve the different observations defined
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -305,6 +305,12 @@ R1/R4/R5 与 S11,本 RFC 不隐式开启新的 acceptance policy。下一完
一般替代、全局收口、跨 Agent 转交及 S11 模型/benchmark 采用仍未完成。这是
明确披露的默认指导变化,不代表完整 R4 合同已取得资格。

[Goal 契约演化提案](goal-contract-evolution-v0.zh-CN.md)在这些既有 owner 下组合
当前目标修订与支撑要求演化。绑定来源的变更集保留原始意图和版本历史,逐效果
检查权限,原子发布相互关联的变化,并识别受影响 peer,不等待全员屏障。记录
存储及有界决策上下文服从该语义边界。当前本机模板提交仍较窄;本提案不启用
通用替代,也不证明模型使用。其 E1–E9、M1–M3 细化既有 R4/R5 验收工作。

### 3.8 失效证据与受影响消费者

恢复和工作切换须保留 §3.7 中不同观察的含义。当前 `work_context.complete` 表示
Expand Down
Loading