Skip to content

docs(blog): lead context delivery with progressive and delta evidence - #8486

Merged
huangruiteng merged 1 commit into
mainfrom
codex/context-delivery-evidence-front-20261110
Nov 10, 2026
Merged

huangruiteng merged 1 commit into
mainfrom
codex/context-delivery-evidence-front-20261110

Conversation

@huangruiteng

Copy link
Copy Markdown
Collaborator

Goal And Delivered Outcome

  • Outcome basis: move the Context Delivery blog's progressive/differential ablation evidence earlier, in both languages.
  • Before → after: readers previously encountered the eight-task byte comparison and 18-hour ablations after the mechanism walkthrough. They now reach both immediately after the introduction, with the byte comparison first, then model-input/task-outcome ablation, then the walkthrough.
  • Intended base: main; verified merge base 708ed0f9d0ba44d4733e4eb749ca37e8ca89c59d.

Author Declaration

  • Written by: model_agent — OpenAI Codex.
  • Specification: no separate written specification; the editorial request stated above is the basis.
Criterion Disposition Path / evidence
Surface progressive and delta evidence before mechanisms implemented Both blog/context-delivery/index.html and blog/zh/context-delivery/index.html; rendered opening and TOC order
Preserve experimental values, sources and limitations implemented All original tables, charts and captions unchanged; all existing anchors retained; cohort/provenance text and counterexamples remain present
Keep the early evidence readable implemented Three scannable byte-summary bullets; full tables available through native details controls; cohort qualifications and the ablation interpretation remain outside collapsed tables

Scope And Continuation

Complete within this scope. Static article HTML only: no runtime, benchmark execution, scoring, dataset, shared stylesheet or publication workflow changes. No new experimental result is claimed. One identical duplicated release/disable paragraph is consolidated without dropping its instructions. No successor is needed for this editorial slice; merge and deployment remain separate.

Validation

  • Tested revision: 9997f5c0454eaf68905a861fad15e669a57e815e.
  • Run state: finished.
  • Input classes: public_fixture.
Check kind Result Public-safe evidence / limitation
static passed git diff --check; public-boundary scan of added lines
integration passed node examples/blog-bilingual-index-smoke.mjs — bilingual links, chart references and eight-task arithmetic
integration passed node examples/frontstage-share-bundle-smoke.mjs — complete static export, bilingual blog and public-boundary checks; the initial missing-dependency attempt was rerun successfully after preparing dependencies
static passed node apps/presentation/site/scripts/seo-smoke.mjs against the assembled share bundle — canonical targets, assets and metadata
regression_parity passed Compared base/head table and figure/caption HTML byte-for-byte as unordered collections; all existing IDs retained, no duplicates; both packaged article files exactly match reviewed source HTML
manual passed Browser inspection of both languages at desktop/narrow widths; both data sections precede mechanisms; 390px table expansion retains all nine rows and constrains horizontal scrolling to the table, not the page

Coverage: publication structure and static delivery are exercised. Existing measurements were not rerun, and this PR does not validate a new causal or performance claim. No backend or runtime change requires qualification here.

Frontend / Visual Evidence

  • UI impact: changed — article ordering, TOC ordering and native details controls.
  • Before: 40740e3434870e9c2b51d7e9650b5b1948d9aeb6 (article files unchanged by the intervening main commits).
  • After: 9997f5c0454eaf68905a861fad15e669a57e815e.
  • Boundary: browser-rendered static public article, not an installed runtime or a deployed-site readback. The assembled export was separately checked to contain byte-identical article HTML. No public branch preview is available yet.
  • Viewports: desktop 1440×1000; narrow 390×844. The existing title/hero is retained; narrow first-viewport composition is intentionally unchanged. The results viewport below shows the actual reordered content.
  • Source data: public_fixture — existing published article and charts only.
  • Attention review: lead with research evidence rather than a long mechanism tour; summarize the two distinct wake cohorts explicitly; keep first-read bytes separate from episode model input. Detailed tables can be expanded without pushing the entire mechanism walkthrough farther down. Counterexamples, source limitations and one-step image enlargement remain accessible.
  • Craft review: reuse existing article typography, chart assets and details/table-scroll styles; no added cards, colors, motion or decorative labels. Loading/error/permission behavior is unchanged.

First viewport — desktop before / after

Before: mechanism-first article opening After: results begin immediately after the introduction

First viewport — narrow before / after

Before: narrow article opening After: retained narrow opening and introductory context

Reordered results — desktop / narrow

Results first: progressive and delta evidence on desktop Results first: distinct cohorts and three readable summaries on narrow screens

Type of Change

  • Documentation update

LoopX Area

  • Public docs or presentation surface

Shared-authority RFC fixture impact

N/A — no authority, runtime, RFC or fixture semantics changed.

Boundary Checklist

  • No private state, credentials, raw trajectories, internal links or local machine paths in the diff or public evidence.
  • No duplicated benchmark execution or new performance claim.
  • Change scoped to the editorial request; no paired RFC changed.
  • Visual evidence is embedded above; one-run captures are not committed.
  • The commit has a DCO Signed-off-by trailer.

Signed-off-by: huangruiteng <huangrt01@163.com>

@loopx-agent loopx-agent left a comment

Copy link
Copy Markdown
Collaborator

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.1-sol | OpenAI | runtime_reported | reasoning_effort=max

APPROVE:准确 head 9997f5c0454eaf68905a861fad15e669a57e815e 未发现阻断项。完成整个 PR 的独立审查;最重要的边界是“研究结果更早可读”,而不是新增了模型节省或性能因果证据。

动机 / Motivation

读者打开中英文 Context Delivery 文章,想先判断渐进读取和差分交付有什么证据、适用范围与反例。

旧版先展开语音任务和机制,八题字节对照及 18 小时消融靠后;新版在两段导言后先给字节对照、再给消融,随后继续原机制说明。

实测两版的结果段已前移,八题和合计行、消融负向观察、来源及复现入口均可读取,原表格与图注没有改变。 本次只改变静态文章的阅读次序与详细表格展开方式,不新增实验、运行时开关或已安装收益声明。

旧顺序要求读者先经过很长的机制讲解才看到实证。只改目录能缩短跳转,但仍保留正文的机制优先顺序;这次把已有结果整体前移,并将逐项表格放入就地展开入口,是完整且可回退的编辑改进。没有要求补做一次研究来证明这项排版调整。

改动思路 / Approach

复用既有静态页面、原生 details/summary 与 table-scroll 样式即可完成编辑目标,没有引入新的状态、脚本或运行时决策 owner。 当前 PR 只重排两篇文章、增加两处原生表格披露并合并一段逐字重复的发布/关闭说明;发布与部署分别验收。

我从不可变基线 708ed0f9d0ba44d4733e4eb749ca37e8ca89c59d 对比整个两文件 diff,同时检查未改动的 blog.css、双语目录、公开聚合 JSON 与静态导出调用。五张表格、四组 figure/图注在各语言内均与基线逐字节相同,所有旧 id 仍在且没有重复;较大行数主要来自整段搬移。既有发布/关闭段落由重复两次变为完整保留一次,没有缩短其 off、trial、unsupported host 或安装/采用边界。

默认路径为“导言 → 八题字节对照 → 分层消融及限制 → 机制 → 复现”。表格展开是浏览器本地阅读状态,不会启动模型、注册工作或写入控制面。无需增加控制器、异步数据加载或第二套表格组件。

具体改动 / Changes

依据已接受的 docs/development/design.md,固定 spec_revision 为 708ed0f9d0ba44d4733e4eb749ca37e8ca89c59d;独立的编辑请求见本 PR 的 Goal And Delivered Outcome。设计契约没有在此 PR 中改写。

criterion_id 当前 head 的判断与证据
earn-the-users-attention implemented:结果、单位和两种唤醒组在机制之前出现;未把首读字节大小解释为整轮模型输入。1200px 基线/新头次序对照及当前宽窄屏实际页面支持此判断。
explanations-on-demand implemented:两处原生披露保留完整表格;关键口径和不能作因果推断的说明仍在表外。键盘 Space 折叠、Enter 展开和表格区域方向键滚动均实际执行。
populated-page-review implemented:检查真实长篇中英文文章的默认、展开与页尾复现区域;覆盖 1440×1000 和 390×844 的实际页面,并读取展开后的三条反例。

关键代码讲解(静态 HTML)

  • #results 与八题摘要:八题对照位于消融之前,三条摘要分别保留 213 次全组唤醒、112 次周期内续跑,以及同一续跑组的首读正文/CLI 比例。公开 JSON 独立求和得到 22,408,690 / 7,285,951 / 4,488,335 B,Progressive 为 32.51395%;约 12.53 MB 的续跑分母仍明确为已四舍五入的另一个组。
  • details 八题表:新增容器只控制披露,不改变八道题和合计行。原生汇总检查在基线和 head 都通过;分别删去英文或中文首条任务行后,同一检查准确拒绝 8 != 9。真实 HTTP 浏览也看到突变副本缺行,而原 head 展开后有完整九行。
  • 中文消融披露:完整保留早窗 +304.7%、进程 stdout 增幅和跨题 Historical Grid 反例。桌面展开与窄屏末行均检查过;不能将控制包裁剪率等同模型输入节省的正文仍在披露外。
  • 既有共享样式:继续使用 focus-visible 和 overflow-x,不新增 CSS 或脚本。390px 页面宽度仍为 390px,八题表可在约 302px 的区域内浏览原 880px 表格;没有通过缩小正文隐藏问题。

仓库经验提示文档变更也要判断用户结果:这里采用“先读现有契约、再走实际阅读路径”的建议。其旧 RFC 案例没有成为本 PR 的结论,也没有额外要求本次交付恢复运行时或证明记忆收益。

对主干的风险 / Risks

主要风险是搬移时丢行、改变分母,或把负向观察藏得难以发现。我对完整基线/head 做了表格、figure、锚点和脚本/样式比较;浏览器展开、键盘回收和缺行突变提供了独立检查。原有历史测量、源码日期、版本与安装采用区别仍保留。本次没有修改通用 schema、配额、调度、授权、benchmark 阈值或自动加载的 Agent 指令;局部 results id 不构成新的共享词汇。

验证 结果与边界
node examples/blog-bilingual-index-smoke.mjs PASS,10 对文章;包括已有的配对导航及图表事件口径负例。
基线/head 与两种缺行突变 PASS / 预期拒绝;两版真实 HTML 完整行数均恢复为九行,缺行不会被“折叠正常”掩盖。
标准 canary premerge --from-git-diff --git-diff-base 708ed0f9d0ba44d4733e4eb749ca37e8ca89c59d PASS,4 项直接检查、3 项 canary 全通过;不是整仓全量测试或合并许可。
实际静态导出与 SEO PASS,完成导出及 28 个 canonical sitemap 目标检查;两篇输出与评审源码逐字节一致。首次导出因缺少网站依赖失败,补齐既有锁文件依赖后成功,原失败保留;未改源文件或降低断言。
两文件原生 public boundary scan PASS,扫描完整两篇文章,0 error / 0 warning。

导出验证使用独立输出目录;未运行会删除固定共享临时输出目录的整份 share-bundle smoke,相关文章路径由实际导出、内容一致性与 SEO 检查覆盖。两次浏览器探针分别因缩写 aria 标签和假定文字间距失败,按当前 DOM 修正后完成;这是评审探针错误,没有归因为产品缺陷。没有查询、轮询或等待 GitHub CI。

我的整体评价 / Verdict

这项编辑目标已实现;long_horizon 为 preserved,文章没有改变工作继续、失败恢复或证据采用规则;user_experience 为 improved,读者先看到结果和限制,再决定是否阅读机制。结果先于机制进入阅读主线;两张详细表默认折叠,展开后保留完整行与范围说明。正文维持 16px,表格沿用 14px;窄屏八题表在自身区域滚动,反例表仍可完整阅读。

复用既有静态页面、原生 details/summary 与 table-scroll 样式即可完成编辑目标,没有引入新的状态、脚本或运行时决策 owner。 当前 PR 只重排两篇文章、增加两处原生表格披露并合并一段逐字重复的发布/关闭说明;发布与部署分别验收。 现有重复说明的合并是本次适度的简化;没有必要为两篇本就成对维护的文章另建数据或组件层。未验证部署后网站、Safari/Firefox 或真实读者理解效果;没有重跑归档研究,截图与源文一致不能证明新的因果收益。

本结论覆盖该静态编辑切片;没有继承历史 PR 批准,没有为原实验新增可信度,也不授予合并、部署或安装权限。发布前仍需准确 head 读回与独立的合并条件检查。

English verdict: APPROVE 9997f5c; no blocking finding. Bilingual result ordering, complete data, native disclosure, static export and affected local gates verified; deployment and new experimental benefit remain unverified.

@huangruiteng
huangruiteng merged commit 39a99f2 into main Nov 10, 2026
22 of 27 checks passed
@huangruiteng
huangruiteng deleted the codex/context-delivery-evidence-front-20261110 branch November 10, 2026 17:25
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.

2 participants