Skip to content

docs(readme): add 24/7 always-on agent architecture mapping and solo-to-team guide - #8786

Merged
loopx-agent merged 1 commit into
mainfrom
codex/readme-always-on-7x24-20261115
Nov 14, 2026
Merged

loopx-agent merged 1 commit into
mainfrom
codex/readme-always-on-7x24-20261115

Conversation

@loopx-agent

@loopx-agent loopx-agent commented Nov 14, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Aligns both README.md and README.zh-CN.md around 24/7 always-on agent execution without overclaiming unshipped organizational surfaces:

  • Hero tagline & navigation: Frames LoopX as an open, harness-neutral control plane for 24/7 always-on agents scaling from local SQLite workflows to multi-agent teams, and adds a direct #always-on-agents navigation link while keeping the Trendshift [codex] Harden release readiness control plane #1 hero badge invariant intact.
  • News feed (2026-11-01): Adds the verified progressive context delivery blog post (32.5% single-layer progressive view across 213 wakes; 3.0% body / 5.0% CLI stacked first-read entry across 112 in-cycle continuations) and cross-links the 47-day freshness postmortem.
  • New #always-on-agents section: Maps Anthropic's 5 always-on primitives (Event Inbox, Timers & Wakeups, Memory & Compaction, Permissions & Deferred Calls, Outbox) to LoopX's control-plane subsystems, and lays out the Solo local SQLite -> peer multi-agent team / staged PostgreSQL remote authority / organizational governance roadmap path.
  • Cross-link in Personal Agents section: Connects Building always-on agents alongside Meta Muse and Grok Bot to #always-on-agents.

Verification

  • uv run --extra test python -m pytest tests/test_readme_presentation.py tests/test_kiro_cli_host_surface.py tests/test_capability_code_maps.py -v: 20 passed
  • uv run --extra test python -m pytest tests/test_contributing_guide.py -q: non-workflow checks passed; pre-existing failure on origin/main test_node_minimum_is_stated_once_everywhere (.github/workflows/package-smoke.yml pins Node.js ['26.0.0'] vs 22.22.3, untouched here)
  • uv run --extra test python scripts/check_rfc_bilingual.py --base origin/main --head HEAD: passed
  • uv run --extra test loopx canary premerge --from-git-diff --git-diff-base origin/main: passed (13/13) including loopx check --scan-path README.md --scan-path README.zh-CN.md

…to-team guide

Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>

@loopx-agent loopx-agent left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewer: actor_kind=model_agent; declaration_source=self_reported; model=Gemini; provider=Google DeepMind

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

动机 / Motivation

本次改动面向寻找“7×24 常驻在线 Agent”解决方案的个人开发者与工程团队,触发场景是读者阅读 README.md 与 README.zh-CN.md 进行架构选型与快速评估。此前首页摘要只强调“连接 Codex、Claude Code、DeepSeek Harness 等运行时”,2026-11-01 发布的渐进式上下文交付文章尚未收录进首页动态,读者即使对比业界提出的五类常驻 Agent 原语(Event Inbox、Timers、Memory、Permissions、Outbox),也无法在首屏快速看清 LoopX 已交付哪些对应控制面能力、哪些仅属预置或路线图范围,实际代价是潜在用户误以为仍需自建队列/审批/上下文恢复脚本,或误读多租户治理成熟度。

修改后的可观测改善在于:首屏副标题与导航直接锚定 #always-on-agents,新增章节用两张紧凑对照表把五大原语精准映射到 LoopX 既有控制面子系统,并诚实区分“个人本地 SQLite + hard lease 立即开箱”与“工程团队多 Agent 协作 / 预置 PostgreSQL 共享权威 / 路线图级 RBAC·SSO”。本 PR 的明确边界(non-goals)是仅更新公开中英文文档表述,不改动任何 CLI、TypeScript/Python 控制面代码或构建配置,也不提前宣称未验收的多租户 SaaS 治理已 GA(仅遗留 GitHub 页面排版渲染未在浏览器实机截屏验证)。

改动思路 / Approach

从控制面职责划分看,本次 README.md(+42/-7)与 README.zh-CN.md(+33/-6)仅属于公开文档呈现层改动,零代码、零新增协议状态或序列化入口;原有 Goal / Todo / Hard Lease、Guarded Heartbeat 预设、Progressive + Delta 上下文交付以及人工 Gate 均已由既有代码与博文承载,本次只做公开导航聚合与双语语义对齐,因此机制成本最小(无需拆出单独新文档造成首页阅读跳转割裂)。

核心设计取舍有二:第一,保留首页开篇唯一 Trendshift #1 徽章在首个 </div> 内的结构不变量,只调整 <sub> 副标题与快捷导航条以嵌入 [24/7 Always-On](#always-on-agents) / [7×24 常驻架构](#always-on-agents);第二,核对仓库实情后收紧团队与企业级表述——已核实 postgresql_authority_store.ts 属于源码已有但外部环境尚待全面验收的共享权威 Provider,而 RBAC、SSO、签名审计仍位于 saas-opportunity-assessment 路线图(packages/ 与 loopx/ 尚无 RBAC 实现代码),因此在表格中明确标注“预置 PostgreSQL”与“组织治理路线图”,杜绝越界宣传。正向路径上,读者从顶部导航或学习索引点击即可一跳直达 #always-on-agents 核对组件映射与公开数据,反向边界则清晰守住“LoopX 保留人工 Gate,不是全自动无审批生产控制器”。

具体改动 / Changes

关键内容讲解

  • Spec 与基线对照:本 PR 为纯公开 README 文档增强,无独立 RFC/需求文档规定本章节内容(spec_basis: no_spec, spec_source: none);改动严格对齐仓库既有事实源,包括 apps/presentation/site/public/blog/context-delivery/index.html、blog/five-freshness-incidents/index.html、docs/guides/installing-loopx.md、docs/product/release-readiness.md、examples/collaboration-delivery/README.md 及 docs/product/roadmaps/saas-opportunity-assessment*.md。
  • README.md 与 README.zh-CN.md 首屏导航与动态(Hero & News):仅更新 <sub> 说明文案并在顶栏链接新增 [24/7 Always-On](#always-on-agents) / [7×24 常驻架构](#always-on-agents);在 ## 📰 News / ## 📰 最新动态 顶部按已验证的 UTC 发布时间 2026-11-01 插入中英文 context-delivery 博客条目(披露 213 次唤醒 32.5% 单层渐进视图、112 次续跑 3.0% / 5.0% 叠加首读及 47 天保鲜复盘链接)。
  • 新增 #always-on-agents 双语对照区与个人 Agent 交叉引用:在 #learn-loopx / #学习-loopx 速查表增加对应入口行,并在 <details> 控制面折叠说明之后插入 <a id="always-on-agents"></a>:先以表格对照 Anthropic《Building always-on agents》(已验证 URL 返回 HTTP 200)五原语与 LoopX 组件及故障预防效果,再对比“个人开发者本地运行(python3 -m pip install --upgrade loopx,本地默认权威 SQLite + hard lease)”到“工程团队协同与组织级路线图”;末尾《Personal Agents / 个人 Agent》章节补充该文章与 #always-on-agents 互链。

对主干的风险 / Risks

对主干行为与兼容性的总体风险极低,未触及 loopx/、packages/、apps/ 或任何工作流文件,所有已有 CLI/Agent runtime 入口与默认行为均保持原样(default_off_isolation / behavior_change_disclosure 与运行态开关隔离均不涉及运行时行为变化,仅通过公开文档新增可发现路径)。在负面/误用边界测试上:若团队误将 #always-on-agents 理解为“接上即可绕过人工确认或立即获得多租户 RBAC”,新增表格与既有 LoopX is not an autonomous production controller 声明显式把最终权限留在人类 Owner Gate、并把 RBAC/SSO 明确归类于路线图文档,避免了权威语义夸大。

本地对精确提交 8084d7b36f337968d84a6cedc6da68609fbd068b 独立执行了完整校验矩阵:

  • tests/test_readme_presentation.py、tests/test_kiro_cli_host_surface.py、tests/test_capability_code_maps.py:PASS(20 passed,验证中英文 Hero 唯一 Trendshift 徽章与宿主表契约)。
  • scripts/check_rfc_bilingual.py --base origin/main --head HEAD:PASS(双语同步 diff 通过)。
  • loopx canary premerge --from-git-diff --git-diff-base origin/main:PASS(13/13:直接检查 4/4、目录 Canary 4/4、内容风险 Smoke 8/8、公开边界扫描 loopx check --scan-path README.md --scan-path README.zh-CN.md 1/1,零人工 hold)。
  • 仅运行 tests/test_contributing_guide.py 时,与本 PR 无关的 test_node_minimum_is_stated_once_everywhere 因 origin/main 既有 .github/workflows/package-smoke.yml:50(node-version: "26.0.0" vs 22.22.3)而 FAIL(已核实 origin/main 基线存在同一行);远端 CI 中 Sign-off(DCO)、dependency-review、Summary 已 PASS,inspect-pr-diff、changes、build、prepare 尚处于队列/运行中(作为非阻塞诊断项记录,不影响代码实质审阅结论,合并就绪闸门仍独立生效)。

我的整体评价 / Verdict

本 PR 在不扩大维护半径、不虚标能力成熟度的前提下,精准提升了 7×24 常驻场景的认知可达性与中英文文档一致性:对 long_horizon 与 user_experience 均判定为 improved(复用既有 LoopX 词汇表如 Goal / Todo / Hard Lease、Guarded Heartbeat、Progressive + Delta、Owner Gate,无自造术语或额外配置负担)。所有相对路径、外部链接(HTTP 200)及实证数字(213 次唤醒、32.5%、112 次续跑、3.0% / 5.0%、253 轮 / 47 天 / 5 次保鲜事故)均逐一核对原始产物。visual_review 因未修改交互式前端/桌面 UI 而适用性为 not_applicable(已人工审计全部 Markdown 表格与 HTML <details> 边界;GitHub 网页窄屏折行渲染未做浏览器实机截屏,列为 unverified_scope)。当前精确 head 8084d7b36f337968d84a6cedc6da68609fbd068b 无阻塞问题,建议合并。

English verdict: APPROVE — exact head 8084d7b verified with 20/20 README/surface pytest checks, bilingual RFC diff check, and 13/13 canary premerge gates passing; no blocking findings.

@loopx-agent
loopx-agent merged commit 2592d4a into main Nov 14, 2026
35 of 36 checks passed
@loopx-agent
loopx-agent deleted the codex/readme-always-on-7x24-20261115 branch November 14, 2026 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant