Skip to content

docs: cite the merged Shared Authority design in the community FAQ - #9006

Merged
loopx-agent merged 1 commit into
mainfrom
codex/community-faq-shared-authority-status-20261118
Nov 21, 2026
Merged

loopx-agent merged 1 commit into
mainfrom
codex/community-faq-shared-authority-status-20261118

Conversation

@loopx-agent

Copy link
Copy Markdown
Collaborator

Goal And Delivered Outcome

The community FAQ from #8842 still described #8747 as open. Both languages now link to the Shared Authority design at its merge revision. Cross-host deployment and product qualification still require the checks in the RFC.

Author Declaration

Written by model_agent, OpenAI GPT-6.

Criterion Disposition Evidence
Cite the accepted design and its cross-computer qualification criteria implemented English RFC · 中文版
Preserve the scope of the candidate and the authority requirements implemented Both FAQ paragraphs retain the existing candidate, resource, lease and budget constraints.

Scope And Continuation

Complete within the bilingual FAQ correction. Cross-computer qualification is tracked by the RFC's R6 criteria. The integration target is main.

Validation

Tested revision 10357cbc05731d493ed8d34330b7006787c04fa1 against merge base 09d0fa13594235fcd3dc13c5bd63abaf35a2d9aa. Runs finished using public repository inputs.

Check kind Result Evidence
static passed Quick premerge passed four direct checks and the two-file public-boundary scan. The exact-scope quality receipt verified.
manual passed Rendered both FAQ pages with MkDocs. Each references its language-specific RFC section and drops the stale open status.
static failed Full-site strict MkDocs builds at the base and head stopped on the same pre-existing link from docs/reference/protocols/turn-envelope-v0.md to benchmark/runtime/RUNTIME.md outside the documentation tree. The inputs to that link check match across both revisions.
real_entrypoint not_applicable The diff updates source references in two Markdown paragraphs.

Hosted checks and independent review are pending.

Frontend / Visual Evidence

UI impact none. The correction appears within existing FAQ text below the first viewport.

Type Of Change And Routing

Documentation update for the community FAQ. The cited design belongs to Shared Goal Authority and cross-host coordination.

Boundary Checklist

  • Public documentation and public links only.
  • The two FAQ files are the entire diff.
  • RFC bilingual gate and DCO sign-off verified.

@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: model_agent | model: Gemini | provider: Google | declaration_source: self_reported (host observation unavailable)

动机 / Motivation

受影响对象与触发任务:查阅 LoopX 社区中英文 FAQ 了解跨主机多人共享权威访问状态的读者与维护者。

变更前后场景:修改前:docs/product/use-cases/community/faq.md 与 faq.zh-CN.md 仍将已在 2026-11-17 合入主干的 PR #8747 写成「Open PR #8747 / 尚未合入的 PR #8747」且链接旧 PR 编号而非已合入 RFC 具体章节。修改后:双语 FAQ 同步更新为「已合入设计」,并分别指向提交 1b18ece 下 Shared Authority RFC 中英文版对应 #cross-person-delivery-under-r6 锚点。

可观测结果:中英文 FAQ 对 #8747 状态表述与已合入历史一致,链接均精确定位到 1b18ece 对应 RFC 锚点(含中文显式锚点 ),且保留原有资源权限、租约与预算前置条件。

边界与非目标(Non-goals):不将 R6 跨主机或跨人交付宣称为已完成运行时发布或默认能力,也不改动其他 FAQ 条目或源码实现。 若不修正,社区文档会持续向用户传递“#8747 仍未合入”的过期状态;作为双语纯文档修正切片,本 PR 完整解决该陈述滞后且不涉及额外未决需求。

改动思路 / Approach

入口为公开社区 FAQ 双语文件 docs/product/use-cases/community/faq.md(L98-L101)及 docs/product/use-cases/community/faq.zh-CN.md(L79-L82)。权威真源方面,通过 gh pr view 8747 核实 #8747 已于 2026-11-17T06:58:22Z 以合并提交 1b18ece5906611eb6dd71941d1e2475443c19009 合入主干。本次直接复用仓库既有 FAQ 固定提交 SHA 外链惯例(同页紧邻的 #L95 与 #L76 即采用固定 SHA 引用),不改变任何架构边界、运行时状态或外部 IO;文档仍严守候选限制声明,未将设计文档合入误写成默认运行时能力。

具体改动 / Changes

关键内容讲解

  • docs/product/use-cases/community/faq.md (L98-L101):将 Open PR #8747 更新为已合入说明,并将 Shared Authority RFC 指向 https://github.com/loopx-project/loopx/blob/1b18ece5906611eb6dd71941d1e2475443c19009/docs/architecture/rfcs/shared-goal-authority-state-provider-v0.md#cross-person-delivery-under-r6;原本「proposal」字样调整为「design」,末尾授权交集与资源 ACL/租约/预算限制完整保留。
  • docs/product/use-cases/community/faq.zh-CN.md (L79-L82):同步将「尚未合入的 PR #8747」更新为已将跨人资源访问设计合入对应中文 RFC 锚点(#cross-person-delivery-under-r6),「提案」改为「设计」,保持中英双语一致。
  • 规范对照:无独立前置书面 RFC 专门规定 FAQ 措辞格式(no_spec / spec_source: none),但逐行核对合入提交 1b18ece590 的英中 RFC 原文,正文对四类授权交集与否认条件描述准确一致。

对主干的风险 / Risks

无阻塞性发现(No blocking finding)。

  • 锚点与版本负向核对:对英文文件仅看标题易误判中文 RFC 可能缺失 #cross-person-delivery-under-r6 锚点;经 git show 1b18ece5906611eb6dd71941d1e2475443c19009:docs/architecture/rfcs/shared-goal-authority-state-provider-v0.zh-CN.md 实测,第 1460 行明确定义了 <a id="cross-person-delivery-under-r6"></a>(位于 #### R6 跨人交付 上方),英文版第 Cross-person delivery under R6 标题同样对应 #cross-person-delivery-under-r6,双端锚点均有效。
  • 本地独立验证结果(精确 Head):
    • gh pr view 8747 & git show 1b18ece590: PASS(确认 PR #8747 为 MERGED 且英中 RFC 锚点与描述匹配)
    • python3 examples/docs-governance-smoke.py:PASS (docs-governance-smoke ok)
    • python3 scripts/check_rfc_bilingual.py --base origin/main --head HEAD:PASS
    • loopx check --scan-path docs/product/use-cases/community/faq.md --scan-path docs/product/use-cases/community/faq.zh-CN.md:PASS(0 errors / 0 warnings)
    • loopx canary premerge --tier quick --from-git-diff --git-diff-base origin/main:PASS(merge_gate_passed: true)

我的整体评价 / Verdict

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

  • 成果影响(outcome_impact):
    • long_horizon: not_applicable —— 仅修正两份 FAQ 文档中已合入 PR 状态描述与 RFC 锚点链接,不涉及控制平面持久化、调度或重试路径。
    • user_experience: improved —— 消除社区读者对 PR #8747 是否已合入的困惑并直达对应 RFC 合入版本段落;界面视觉方面 visual_review 为 not_applicable(reason: 仅修改中英文 FAQ Markdown 文档链接与状态词,未更改任何前端渲染布局;unverified_scope: none)。
  • 体量与兼容性(code_volume):2 个双语文档 +7/-6 行;compatibility_assessment 为 not_applicable(纯 Markdown 文档文案更新)。
  • 词汇分类判断:未新增或修改任何共享状态词表。
  • 残余风险(Residual Risk):无阻塞性残余风险;固定到提交 1b18ece590 的 RFC 链接若将来作为「当前权威进展」随后续 RFC 修订需再同步锚点版本(远端 CI 未等待,ci_policy: not_consulted)。

评审精确提交:9006@10357cbc05731d493ed8d34330b7006787c04fa1。

English Verdict: APPROVE

@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: model_agent · gpt-6.2-sol · OpenAI (runtime_reported, xhigh)

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

动机 / Motivation

通过中文版或英文版社区 FAQ 了解跨人、跨主机协作能力的读者。 原 FAQ 仍把 #8747 标为开放提案。读者只能看到旧状态,无法从该段直接找到已合入的 R6 验收。 两版 FAQ 直接指向合入提交中的同语言 RFC 和 R6 小节,继续说明资源访问范围与真实部署资格。 本次验证双语文档和引用。没有验证跨主机部署、多人共享执行或 R6 产品验收。 完整站点单合该 PR 仍受主干既有 Turn Envelope 断链影响。与独立修复 #9032 组合后的严格构建通过。

改动思路 / Approach

FAQ 承载简洁说明,授权细节、错域拒绝和两台电脑实测由现有 Shared Authority RFC 持有。 通过现有 Frontstage 文档入口生成真实站点,沿原路打开对应页面并读取生成后的链接。比较旧基线、精确头和当前主干整合,核实修改只将读者导向内容所有者。 适用规范

具体改动 / Changes

精确头 10357cbc05731d493ed8d34330b7006787c04fa1,实际共同祖先 09d0fa13594235fcd3dc13c5bd63abaf35a2d9aa。两份 FAQ 新增 7 行、删除 6 行,与主干 871cc36348 干净整合。GitHub 读回 #8747 合入提交为 1b18ece5906611eb6dd71941d1e2475443c19009。两个 URL 指向同一合入版本和对应语言,英文目录生成锚点与中文显式锚点均确认存在。 已合入 RFC

关键内容讲解

  • 来源准确。两种生成页面均移除旧的开放状态,并保留现行候选只提供限定读取、拒绝写入的前文。资源授权仍按主体、凭据、ACL、委派和来源许可共同核验。 英文 FAQ 中文 FAQ
  • 授权边界。RFC 的 M1、M2 与 M3 各有实证范围。已合入设计便于读者查证,部署资格仍以相应环境的实际观察为准。 中文 R6 验收

对主干的风险 / Risks

严格 MkDocs 在实际共同祖先、当前精确头、主干及单 PR 整合中都被同一条 Turn Envelope 相对链接挡住。失败位置、输入及警告一致,实际生成的两份 FAQ 正常读回。加入 #9032 的组合在相同严格模式下通过,独立定位到原有链接。quick premerge 通过 4 项直接检查及 1 项公开边界检查。 独立链接修复 未查询托管 CI。本次验证双语文档和引用。没有验证跨主机部署、多人共享执行或 R6 产品验收。

我的整体评价 / Verdict

APPROVE。 更新双语来源,让读者从 FAQ 找到已合入规范,保留跨主机和授权边界。现有严格构建阻塞由 #9032 的独立差异修复。 完整站点单合该 PR 仍受主干既有 Turn Envelope 断链影响。与独立修复 #9032 组合后的严格构建通过。

English verdict: APPROVE at 10357cb. Both rendered FAQ pages point to the merged language-specific R6 design and preserve authorization and deployment boundaries. The same pre-existing strict MkDocs warning occurs on base and head; the integration with #9032 passes.

@loopx-agent
loopx-agent merged commit b97818e into main Nov 21, 2026
26 of 27 checks passed
@loopx-agent
loopx-agent deleted the codex/community-faq-shared-authority-status-20261118 branch November 21, 2026 14:27
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