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
1 change: 0 additions & 1 deletion .github/CODEOWNERS
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,6 @@
/tests/ @huangruiteng @songoow @loopx-agent
/scripts/ @huangruiteng @songoow @loopx-agent
/demo/ @huangruiteng @songoow @loopx-agent
/deprecate/ @huangruiteng @songoow @loopx-agent

# --- Subsystem routes --------------------------------------------------------

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/full-public-smokes.yml
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ jobs:
retention-days: 7

smoke-fleet-health:
if: always()
if: always() && github.repository == 'loopx-project/loopx'
needs: full-public-smokes
runs-on: ubuntu-latest
timeout-minutes: 10
Expand Down
1 change: 0 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@
.venv/
.idea
node_modules/
apps/dashboard/public/*.local.json
apps/presentation/dashboard/public/*.local.json
__pycache__/
*.pyc
Expand Down
7 changes: 4 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,8 @@ LoopX needs two runtimes:

- **Python 3.11+.** `uv` installs a compatible one for you.
- **Node.js 22.22.3 or newer**, with Node.js 24 LTS recommended. `pyproject.toml`
declares no Python dependencies, but the TypeScript control plane runs on the
declares no cross-platform Python dependencies (only `tzdata; sys_platform == 'win32'`),
but the TypeScript control plane runs on the
system Node.js, both for `loopx` itself and for the test suite. `pip` and `uv`
cannot install Node.js for you.

Expand Down Expand Up @@ -193,7 +194,7 @@ touch, mention it in the PR instead of fixing it there.
| `ci-maintenance.yml` | opened, reopened, edited, updated or closed PR (`pull_request_target`, trusted base code only) | no | inspects potential stale PR comparisons without mutating the head or target; cancels obsolete Python qualification runs after rechecking the PR and source branch |
| `dependency-review.yml` | every PR | no | dependency changes introduced by the PR |
| `postgresql-integration.yml` | control-plane or npm lockfile paths | no | PostgreSQL authority store and service on a temporary instance |
| `package-smoke.yml` | extension package paths | no | extension packages install, entrypoints, and example schemas |
| `package-smoke.yml` | `loopx-core` and extension package paths | no | `loopx-core` and extension packages install, entrypoints, and example schemas |
| `release-artifacts.yml` | `loopx/`, packaging, and lockfile paths | no | release identity and a release build from this source |
| `runtime-snapshots.yml` | runtime artifact, installer, and updater paths | no | qualified, revision-addressed runtime archives and the main channel pointer |
| `ark-turn.yml` | Turn driver and collaboration paths | no | optional Ark Turn package, stdio MCP, and DSH parity |
Expand All @@ -203,7 +204,7 @@ touch, mention it in the PR instead of fixing it there.
| `frontstage-pages.yml` | README, dashboard, and chat bundle paths | no | public Pages build |
| `desktop-release-artifacts.yml` | desktop app and dashboard paths | no | macOS and Windows desktop builds |
| `desktop-updater.yml` | desktop app paths | no | desktop app build and updater feed |
| `full-public-smokes.yml` | no (push to `main`, schedule) | no | every public smoke, in shards |
| `full-public-smokes.yml` | no (manual, schedule) | no | every public smoke, in shards |
| `sonarcloud.yml` | no (called by Python Tests) | no | SonarCloud analysis of that run's coverage |
| `stale.yml` | no (schedule) | no | stale-issue reminders (never closes issues) |
| `update-notes.yml` | no (schedule) | no | biweekly update notes |
Expand Down
1 change: 1 addition & 0 deletions apps/presentation/dashboard/vite.config.ts
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ export default defineConfig({
"/ssh-hosts": chatProxy,
"/api/chat": chatProxy,
"/api/actions": chatProxy,
"/api/goals": chatProxy,
"/api/ssh-source": chatProxy,
},
},
Expand Down
2 changes: 1 addition & 1 deletion docs/book/chapters/00-reading-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -233,7 +233,7 @@ CLI/App convergence 与 Stage 4 distribution cleanup 仍是后续方向。
| 主题 | `v0.5.4` 已发布事实 | 深入入口 |
| --- | --- | --- |
| Control Plane | Turn/Host Todo settlement、quota commit、task-lease lifecycle、Vision refresh 与 scheduler heartbeat 等完整事务已迁入 typed TypeScript owner;Python facade 仍承担迁移期边界 | [迁移 RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/) |
| Operator surface | Personal Workspace 已提供 Goal、Task、Chat 和 read-only status source 入口;界面不是新的事实源 | [Dashboard README](https://github.com/huangruiteng/loopx/blob/v0.5.4/apps/presentation/dashboard/README.md) |
| Operator surface | Personal Workspace 已提供 Goal、Task、Chat 和 read-only status source 入口;界面不是新的事实源 | [Dashboard README](https://github.com/loopx-project/loopx/blob/v0.5.4/apps/presentation/dashboard/README.md) |
| Host runtime | Codex、Claude Code、OpenCode、Pi、KunlunCode、DeepSeek Harness 与 custom runner 具有不同 activation/stop contract | [Runtime Connector Catalog](/loopx/docs/integrations/runtime-connector-catalog/) |
| Capability / Provider | Capability 由 package-owned catalog entry、真实 command 和 durable validation 共同定义;Provider/Extension 不继承 Kernel authority | [Capability Catalog](/loopx/docs/capabilities/) |
| Shared authority | file、NoKV 与 PostgreSQL provider 仍是 staged candidate;安装 Provider 不会改变默认本地 authority | [Shared Authority RFC](/loopx/docs/architecture/rfcs/shared-goal-authority-state-provider-v0/) |
Expand Down
4 changes: 2 additions & 2 deletions docs/book/chapters/02-session-goal-loopx.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ same time and cost budget
记录 completion、独立 verifier、错误写入、人工介入、stop-policy、wall time 和 cost。没有 matched
baseline 或独立 verifier 时,可以记录使用体验,不能声称产品能力提升。

[Benchmark 研究 RFC](https://github.com/huangruiteng/loopx/blob/main/docs/architecture/rfcs/long-horizon-harness-benchmark-research-program-v0.md)
[Benchmark 研究 RFC](https://github.com/loopx-project/loopx/blob/main/docs/architecture/rfcs/long-horizon-harness-benchmark-research-program-v0.md)
定义当前研究边界。Benchmark-native 研究必须明确 arm semantics、authority boundary 与独立
verifier,才能作为产品研究证据。

Expand Down Expand Up @@ -274,7 +274,7 @@ environment read 与 replan,不需要新 Host 继承旧 transcript。
### Host 兼容矩阵

LoopX 保留同一 control-plane contract,但不同 Host 的启动和唤醒机制并不相同。当前公开
[Runtime Connector Catalog](https://github.com/huangruiteng/loopx/blob/main/docs/integrations/runtime-connector-catalog.md)
[Runtime Connector Catalog](https://github.com/loopx-project/loopx/blob/main/docs/integrations/runtime-connector-catalog.md)
与各 Host adapter 文档给出的主要路径是:

| Host surface | 驱动 | 关键限制 |
Expand Down
22 changes: 11 additions & 11 deletions docs/book/chapters/core-state-machines.md
Original file line number Diff line number Diff line change
Expand Up @@ -231,11 +231,11 @@ flowchart TD
- settlement 再以 `goal_id + agent_id + turn_instance_id` 绑定 writeback、spend 与 scheduler receipt。

对应的源码锚点分别是
[`completion_transaction.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/todos/completion_transaction.py)、
[`local_state_write_correctness.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/runtime/local_state_write_correctness.py)、
[`authority_store.ts`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/coordination/authority_store.ts)、
[`coordination/authority_core.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/coordination/authority_core.py)
和 [`settlement.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/turn_driver/settlement.py)。
[`completion_transaction.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/todos/completion_transaction.py)、
[`local_state_write_correctness.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/runtime/local_state_write_correctness.py)、
[`authority_store.ts`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/coordination/authority_store.ts)、
[`coordination/authority_core.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/coordination/authority_core.py)
和 [`settlement.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/turn_driver/settlement.py)。

所以正确流程是“读 basis -> 提案 -> 验证/guard -> guarded commit -> 事件或 receipt -> 回读”,而不是
Agent 直接覆盖一份看似完整的状态。
Expand Down Expand Up @@ -300,7 +300,7 @@ transition 仍由 write API、validation 和 receipt 完成。箭头表示事实

### Todo lifecycle:只有四个持久 status

[`loopx/control_plane/todos/contract.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/todos/contract.py)
[`loopx/control_plane/todos/contract.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/todos/contract.py)
定义 Todo 的持久状态:

```text
Expand Down Expand Up @@ -370,7 +370,7 @@ flowchart LR

### Handoff:clear 不等于路线完整

[`handoff_gate.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/todos/handoff_gate.py)
[`handoff_gate.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/todos/handoff_gate.py)
从 Todo relation 派生六种 handoff state:

| 派生状态 | 含义 | 下一步 |
Expand All @@ -389,7 +389,7 @@ flowchart LR

### Quota runtime:先判定行为,再考虑 spend

[`loopx/control_plane/quota/states.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/quota/states.py)
[`loopx/control_plane/quota/states.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/quota/states.py)
固定了 quota runtime state 的判定优先级:

```text
Expand Down Expand Up @@ -424,7 +424,7 @@ guard、capability gate、selected Todo、execution obligation 和 scheduler hin

### Settlement:成功必须按事务顺序落地

[`turn_transaction_contract.json`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/turn_transaction_contract.json)
[`turn_transaction_contract.json`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/turn_transaction_contract.json)
定义完整 Turn 的阶段:

```text
Expand Down Expand Up @@ -525,7 +525,7 @@ effect;外部结果必须先成为 typed observation,才能进入 Monitor
- 到达 expiry 或 stop condition:完成 Monitor,并连接 successor 或 `no_followup`。

对于已经显式提升到 shared authority 的 Goal,
[`todo_monitor_poll.ts`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/coordination/todo_monitor_poll.ts)
[`todo_monitor_poll.ts`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/coordination/todo_monitor_poll.ts)
会在同一个 canonical revision、同一次 CAS 和同一 durable operation receipt 中提交**无 lease 的
observation 与它请求的独立 successor**。事务先校验 actor 注册、claim/binding/exclusion、Monitor
仍处于 active 状态,以及 material-change generation 确实前进;任何校验失败都不会写入任一半。
Expand Down Expand Up @@ -643,7 +643,7 @@ flowchart TD

### Terminal 是严格合取,不是“队列看起来空了”

[`loopx/control_plane/goals/goal_frontier/terminal.py`](https://github.com/huangruiteng/loopx/blob/main/loopx/control_plane/goals/goal_frontier/terminal.py)
[`loopx/control_plane/goals/goal_frontier/terminal.py`](https://github.com/loopx-project/loopx/blob/main/loopx/control_plane/goals/goal_frontier/terminal.py)
中的 `goal_frontier_is_terminal_no_followup` 不接受一个手写的 terminal flag。它要求 Todo source
完整且闭合,并且 advancement、monitor、successor、handoff、replan、acceptance、autonomy blocker
等 frontier 均无未解决项;同时还需要结构化的 `no_followup` intent。
Expand Down
8 changes: 4 additions & 4 deletions docs/book/chapters/source-change-control-plane-rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,8 +64,8 @@ problem
一个本来可以一行的修复带上一份长期兼容承诺。

本章案例属于第一类。现有
[`decision_scope_v0`](https://github.com/huangruiteng/loopx/blob/main/docs/reference/protocols/decision-scope-v0.md)
已经规定 Gate 是 scoped authority;[State Machines](https://github.com/huangruiteng/loopx/blob/main/docs/product/core-control-plane/state-machine.md)
[`decision_scope_v0`](https://github.com/loopx-project/loopx/blob/main/docs/reference/protocols/decision-scope-v0.md)
已经规定 Gate 是 scoped authority;[State Machines](https://github.com/loopx-project/loopx/blob/main/docs/product/core-control-plane/state-machine.md)
也把 ambiguous scope 导向 repair。

如果实现把它变成全局 wait,应该修实现,无需新增一个"允许全局猜测"的兼容字段。
Expand Down Expand Up @@ -413,7 +413,7 @@ invariant、画完协议链,通常要几个小时。换到的东西是:这
一个真正的 additive protocol change 可以合理地跨十几个文件;一个 implementation repair 通常
不应该。

**边界一:full validation 跑不起全套,这是设计如此。** 本仓库的 [PR 基线](https://github.com/huangruiteng/loopx/blob/main/docs/development/testing-and-quality.md) 包含 lint、type、
**边界一:full validation 跑不起全套,这是设计如此。** 本仓库的 [PR 基线](https://github.com/loopx-project/loopx/blob/main/docs/development/testing-and-quality.md) 包含 lint、type、
output budget smoke、`pytest` 分层、`loopx canary premerge --from-git-diff` 和 public/private
scan;真实路径验证(例如 PostgreSQL integration)需要一个一次性隔离实例。开发阶段应当从最
聚焦的那条命令开始,无需等最宽矩阵。完整公开 smoke fleet 的职责是宽覆盖与健康观察,不是
Expand Down Expand Up @@ -443,7 +443,7 @@ diff 和描述来发现,这也是为什么下一章把 PR 描述本身当成
推导出来。

**在 Python facade 里重建 TypeScript 侧规则。** 这是本章开头提到的第二个错误。可以通过
`loopx canary premerge --from-git-diff` 发现两侧漂移,也可以用 [TypeScript Control-Plane Migration RFC](https://github.com/huangruiteng/loopx/blob/main/docs/architecture/rfcs/typescript-control-plane-migration-v0.md)
`loopx canary premerge --from-git-diff` 发现两侧漂移,也可以用 [TypeScript Control-Plane Migration RFC](https://github.com/loopx-project/loopx/blob/main/docs/architecture/rfcs/typescript-control-plane-migration-v0.md)
判断一处逻辑归谁:它是否已经是一个 domain-owned decision 或 effect receipt。如果答案是肯定的,
改动应落在 TypeScript 侧,Python 侧只做适配或兼容投影。

Expand Down
Loading
Loading