Skip to content
Open
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
118 changes: 0 additions & 118 deletions .github/workflows/postgresql-integration.yml

This file was deleted.

1 change: 0 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,6 @@ touch, mention it in the PR instead of fixing it there.
| `dco.yml` | every PR | yes (`Sign-off`) | `Signed-off-by` on contribution commits; verified GitHub-generated two-parent merges are exempt |
| `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` | `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 |
Expand Down
2 changes: 1 addition & 1 deletion README.ja.md
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ LoopX はそのオープンでハーネス非依存のコントロールレイ
| 規模 | LoopX の動かし方 | 権限、連携、ガバナンスの姿勢 |
| --- | --- | --- |
| **個人開発者とローカルエージェント** | 外部インフラなしで `python3 -m pip install --upgrade loopx`。既存の CLI/デスクトップのランタイムを接続します | ハードリースを備えた正規のローカル **SQLite** ストア(既存の File セットアップも利用可)。アイドル時のトークン消費ゼロで、再起動やコンパクションを乗り越えます |
| **エンジニアリングチームとエンタープライズへの道筋** | 対等なワーカーが todo を claim し、Desktop Workspace、GitHub、Lark を通じて共有ゴール上でレビュー済みの成果物を返します([3 エージェントのデモ](examples/collaboration-delivery/README.md)) | ワーカーのオーナーシップと人間の承認ゲートを維持します。段階的な **PostgreSQL** リモート権限([プロバイダー](loopx/control_plane/coordination/postgresql_authority_store.ts))や、計画中の組織ガバナンス(RBAC、SSO、クォータ、署名付き監査)へと拡張できます。詳しくは[導入と SaaS のロードマップ](docs/product/roadmaps/saas-opportunity-assessment.md)をご覧ください |
| **エンジニアリングチームとエンタープライズへの道筋** | 対等なワーカーが todo を claim し、Desktop Workspace、GitHub、Lark を通じて共有ゴール上でレビュー済みの成果物を返します([3 エージェントのデモ](examples/collaboration-delivery/README.md)) | ワーカーのオーナーシップと人間の承認ゲートを維持します。ローカルの **File**/**SQLite** 権限およびアウトバウンド HTTPS **RemoteAuthority** クライアント契約([ワイヤー契約](loopx/control_plane/coordination/remote_authority_contract.ts))は `loopx` 内で Apache-2.0 のまま維持され、サーバーサイドの PostgreSQL 権限、分散コーディネーション、マルチテナント組織ガバナンス(RBAC、SSO、クォータ、署名付き監査)は `loopx-project/loopx-cloud` に配置されます。詳しくは[ライセンス境界](docs/project/licensing.md#open-core-and-commercial-boundaries)と[導入と SaaS のロードマップ](docs/product/roadmaps/saas-opportunity-assessment.md)をご覧ください |

## LoopX の動作を見る

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ operate 24/7 with explicit durability and human gates:
| Scale | How LoopX runs | Authority, collaboration & governance posture |
| --- | --- | --- |
| **Solo developer & local agent** | `python3 -m pip install --upgrade loopx` with zero external infrastructure; connect your existing CLI/Desktop runtime | Canonical local **SQLite** store with hard leases (plus existing File setups), surviving restarts and compaction at zero idle tokens |
| **Engineering team & enterprise path** | Peer workers claim todos and return reviewed artifacts on shared Goals via Desktop Workspace, GitHub, and Lark ([three-agent demo](examples/collaboration-delivery/README.md)) | Preserves worker ownership and human approval gates; extends to staged **PostgreSQL** remote authority ([provider](loopx/control_plane/coordination/postgresql_authority_store.ts)) and planned org governance—RBAC, SSO, quotas, signed audit—in the [adoption & SaaS roadmap](docs/product/roadmaps/saas-opportunity-assessment.md) |
| **Engineering team & enterprise path** | Peer workers claim todos and return reviewed artifacts on shared Goals via Desktop Workspace, GitHub, and Lark ([three-agent demo](examples/collaboration-delivery/README.md)) | Preserves worker ownership and human approval gates; keeps local **File**/**SQLite** authority and the outbound HTTPS **RemoteAuthority** client contract ([wire contract](loopx/control_plane/coordination/remote_authority_contract.ts)) Apache-2.0 in `loopx`, while server-side PostgreSQL authority, distributed coordination, and multi-tenant org governance—RBAC, SSO, quotas, signed audit—live in `loopx-project/loopx-cloud` ([licensing boundary](docs/project/licensing.md#open-core-and-commercial-boundaries), [adoption & SaaS roadmap](docs/product/roadmaps/saas-opportunity-assessment.md)) |

## See LoopX in Action

Expand Down
2 changes: 1 addition & 1 deletion README.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -152,7 +152,7 @@ LoopX 把这套**开源、Harness 中立**的控制面直接做成可运行基
| 使用形态 | LoopX 运行方式 | 权威存储、协作与治理形态 |
| --- | --- | --- |
| **个人开发者 & 本地 Agent** | `python3 -m pip install --upgrade loopx` 零外部依赖直接运行,接入已有 CLI / 桌面端 | 默认本地权威 **SQLite** + hard lease(兼顾既有 File 配置),跨重启、跨压缩保留现场且闲置零 Token |
| **工程团队 & 组织级扩展** | 多 Agent 认领 Todo、基于同一 Goal 经工作区 / GitHub / 飞书协同交付与互审([三 Agent 协作示例](examples/collaboration-delivery/README.md)) | 保留各自责任边界与人工审批门;支持向预置的 **PostgreSQL** 远程共享权威([源码实现](loopx/control_plane/coordination/postgresql_authority_store.ts))以及[组织治理路线图](docs/product/roadmaps/saas-opportunity-assessment.zh-CN.md)中的 RBAC、SSO 与审计能力平滑演进 |
| **工程团队 & 组织级扩展** | 多 Agent 认领 Todo、基于同一 Goal 经工作区 / GitHub / 飞书协同交付与互审([三 Agent 协作示例](examples/collaboration-delivery/README.md)) | 保留各自责任边界与人工审批门;本地 **File**/**SQLite** 权威及出站 HTTPS **RemoteAuthority** 客户端契约([协议契约](loopx/control_plane/coordination/remote_authority_contract.ts))在 `loopx` 中保持 Apache-2.0 开源,服务端 PostgreSQL 权威、分布式协调与多租户组织治理(RBAC、SSO、配额与签名审计)承载于 `loopx-project/loopx-cloud`(见[许可证边界](docs/project/licensing.md#open-core-and-commercial-boundaries)与[组织治理路线图](docs/product/roadmaps/saas-opportunity-assessment.zh-CN.md)) |

## 看看 LoopX 如何工作

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -347,7 +347,8 @@ now rejects unsupported providers before storage or writer-fence effects;
[CLI controls](../../../tests/control_plane/test_canonical_authority_fixture.py)
verify actual File/SQLite readback and preserve state on rejection. Previously,
a PostgreSQL label silently initialized File authority. The existing
[PostgreSQL remote task candidate](../../reference/remote-authority-task-service-v0.md)
[outbound `RemoteAuthority` client contract](../../../loopx/control_plane/coordination/remote_authority_contract.ts)
(and the [`v2.4.0` PostgreSQL remote task candidate](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/remote-authority-task-service-v0.md), whose server-side authority now lives in `loopx-project/loopx-cloud`)
is separately qualified through real TLS, restricted roles, task lifecycle and
read-only quota observation. It admits no ordinary host Turn. These service
checks therefore do not qualify an ordinary PostgreSQL feedback Turn or justify
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -324,7 +324,7 @@ Mapping 拒绝顺序、精确整数 IO、会话 ID 解码、轮询时钟及 pend
[CLI 对照](../../../tests/control_plane/test_canonical_authority_fixture.py)
验证真实 File/SQLite 回读及拒绝时状态不变。此前 PostgreSQL 标签会静默
初始化 File authority。既有
[PostgreSQL remote task 候选](../../reference/remote-authority-task-service-v0.md)
[出站 `RemoteAuthority` 客户端契约](../../../loopx/control_plane/coordination/remote_authority_contract.ts)(以及服务端权威现已归入 `loopx-project/loopx-cloud` 的 [`v2.4.0` PostgreSQL remote task 候选](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/remote-authority-task-service-v0.md))
另经真实 TLS、受限角色、任务生命周期和只读 quota 观察验证,仍不准入普通
host Turn。因此这些服务检查不能取得普通 PostgreSQL 反馈 Turn 资格,
也不构成本切片新增执行 profile 的理由。
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ PR to the remaining work. [Decision and exits](ledger/shared-goal-authority-stat

[Roadmap](loopx-overall-roadmap-v0.md) R5 reuses D1 projection, D2 real-backend/capacity/applicable ten-day soak and D3 fenced cutover. R6 connects the selected shared profile to authenticated local/cloud execution. R1–R3 can advance on supported profiles without waiting for PostgreSQL or whole-Goal default promotion.

`e94759d88` adds [PostgreSQL service admission](../../reference/postgresql-authority-service-v0.md), with authentication/tenant verification injection and identity rotation. The [candidate remote task service](../../reference/remote-authority-task-service-v0.md) reuses that seam for TLS claim/progress/lease/read commands, server-owned scoped credentials, bounded pooling, incarnation pinning and receipt recovery. Its source-checkout tests use independent client processes and a restricted role on real PostgreSQL, including lost responses and service restart. This does not qualify deployed local/cloud hosts, shared budget ownership, Host supervision, App/CLI integration, failover, capacity/soak or promotion; these remain with the P lane and R6/D1–D3 owners. R7 must separately report registration, active executors and measured capacity. Directory, presence, a plan or one source read grants no shared authority. Existing fail-closed source, receipt/replay and rollback contracts remain.
`e94759d88` added [PostgreSQL service admission (`v2.4.0`)](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/postgresql-authority-service-v0.md), with authentication/tenant verification injection and identity rotation, and the [`v2.4.0` candidate remote task service](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/remote-authority-task-service-v0.md) reused that seam for TLS claim/progress/lease/read commands, server-owned scoped credentials, bounded pooling, incarnation pinning and receipt recovery (in the Open-Core boundary split, the outbound HTTPS [`RemoteAuthority` wire contract](../../../loopx/control_plane/coordination/remote_authority_contract.ts) and client remain Apache-2.0 in `loopx`, while server-side PostgreSQL authority and multi-tenant services live in `loopx-project/loopx-cloud`). This does not qualify deployed local/cloud hosts, shared budget ownership, Host supervision, App/CLI integration, failover, capacity/soak or promotion; these remain with the P lane and R6/D1–D3 owners. R7 must separately report registration, active executors and measured capacity. Directory, presence, a plan or one source read grants no shared authority. Existing fail-closed source, receipt/replay and rollback contracts remain.

**Observation retirement (2026-09-24).** [Current delivery inventory](ledger/shared-goal-authority-state-provider-v0/2026-09-24-observation-retirement.md)
separates merged code, open PRs and qualification gates. This delivery removes
Expand Down Expand Up @@ -1656,7 +1656,8 @@ Use two distinct lifetimes of the same Goal alias in access qualification.
| Client omits lifetime, server independently binds current lifetime and audience | Evaluate the bound resource and action through the ordinary ACL. Deny outside that scope. |
| Explicit stale lifetime or different resource/version | Deny the mismatched action, even with a valid key and a current store connection. |

The [v0 remote task service](../../reference/remote-authority-task-service-v0.md)
The [`v2.4.0` v0 remote task service](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/remote-authority-task-service-v0.md)
(whose outbound [`RemoteAuthority` wire contract](../../../loopx/control_plane/coordination/remote_authority_contract.ts) remains in `loopx` while server-side implementation lives in `loopx-project/loopx-cloud`)
is a source-checkout candidate. Its strict request and policy accept
tenant/Goal/actor/operation grants and provider incarnation. They cannot
express the resource or Goal lifetime ACL above. A scoped key for that service
Expand Down
Loading
Loading