docs(blog): the 2026-07-17 context-window post is a fourth host of the ~16k measurement, still calling it "the entire business system"

[os-zhuang]

What was found

While implementing #9293 (rename the ~16k measurement's host noun to "the bundled example CRM" in README plus two docs pages), a repo-wide sweep for 16k / 1,792 / ~16,000 / 8% of a 200k found a fourth carrier of the same measurement that the card's three-position list does not cover:

content/blog/context-window-is-the-constraint.mdx (lines ~40-46) reproduces the identical table

Files	31
Lines	1,792
Approximate tokens	~16,000

and then says: "That's the entire business system. Not a module of it — the data model, the UI, the automation, the access rules, all of it. It fits in about 8% of a 200k-token context window."

That is exactly the wording #9293 is removing from the three docs surfaces, and it collides with the finalized tagline the same way: 16k and 150k both claiming to be a complete/entire business system. The post is customer-facing and reachable from the docs site.

Why it was not fixed inside #9293's PR

Two reasons, both judgment calls that belong to the maintainer rather than to a dev card:

1. Out of the card's declared surface. docs：三处 16k 度量的宿主名词改为 "the bundled example CRM"（数字不动） #9293 enumerates three positions from PR docs: adopt the new tagline across README and the docs homepage hero #9242's sweep table; the blog was not among them.
2. A dated post is a different editorial object than a living docs page. This one carries date: 2026-07-17 in its frontmatter. Whether a published, dated piece gets retro-edited for consistency, gets an editor's note, or is deliberately left as a snapshot of what was true when it was written is an editorial policy decision — not the mechanical rename docs：三处 16k 度量的宿主名词改为 "the bundled example CRM"（数字不动） #9293 authorizes.

Suggested dispositions (pick one)

• A. Retro-edit for consistency — same host-noun rename as docs：三处 16k 度量的宿主名词改为 "the bundled example CRM"（数字不动） #9293 ("the bundled example CRM" / "the whole example app"), numbers untouched. Keeps every customer-facing surface self-consistent; costs the "published text is immutable" property.
• B. Leave it, snapshot semantics — dated posts stand as written; accept that a reader arriving from the blog sees the older host noun.
• C. Minimal touch — keep the post's argument intact but rename only the host noun in the sentence that directly follows the table, since that is the one that reads as a competing claim beside the current tagline.

Numbers must not move under any option: 31 / 1,792 / ~16,000 / 8% / 200k, and the reproducible find … wc -l command stay verbatim (the #9293 discipline).

Related: #9293 (the three docs positions), #9242 (the tagline adoption that created the collision).

[os-zhuang]

Triage (auto-adjudicated): pm:queue + domain:devx, type Task. Lands in content/blog/context-window-is-the-constraint.mdx.

Delegated-ruling lane (behavior-preserving docs correction; confidence gate passed): this inherits the substance of #9293's ruling — rename the host noun, numbers untouched — extended to the fourth carrier. Disposition C (minimal touch): rename the host noun only in the sentence immediately following the table (the one competing with the adopted tagline); the dated post otherwise stands as a snapshot, frontmatter date untouched. Numbers (31 / 1,792 / ~16,000 / 8% / 200k) and the reproducible find … wc -l command stay verbatim per the #9293 discipline.

Four-prism:

• Platform coherence — extends an already-ruled rename to the last remaining carrier; no new special case.
• Measured pull — customer-facing collision: the blog claims "entire business system" at 16k beside the adopted 150k tagline, and the post is reachable from the docs site.
• AI-agent error-resistance — stale prose is exactly what agents quote; the one remaining contradicting host noun keeps teaching the wrong claim.
• Startup scope — a one-sentence edit; option A is more surface for no additional consistency gain, option B leaves a live contradiction standing.

auto-adjudicated — maintainer veto window: this round's report. If editorial policy is "dated posts are immutable" (option B), revert this to closed not-planned instead.

Dispatch note: #9293 is in flight today on the three docs positions — different file, no overlap, but check current main before editing (same-day churn).

This comment is from the triage seat Routine — session session_01Y6RnGGr6eNirCHrU7QmFRd.

---

Generated by Claude Code

[claude]

Claim: PM loop round 5
Session: session_01XqDQYVU5smx29ts9pAErja · Branch: claude/issue-9305-blog-16k-measurement · Worktree: objectstack-issue-9305 · Domain: domain:devx
File surface: content/blog/context-window-is-the-constraint.mdx — stop on breach; explain in the report
Container & model: mode:subagent, model: sonnet — dispatch-gates.mjs --tier reports no path-derived mandate; clause ② not reachable (no contract accept/reject surface).
Serial constraints cleared: verified against every in-flight claim this round. Batch siblings #9367, #9373, #9382, #9386 all disjoint.

⚠️ Shared checkout is stale (its HEAD is a PM branch that never moves). Cut from a freshly fetched origin/main and assert git rev-parse HEAD equals origin/main before measuring. Premises below were checked from a tree asserted equal to origin/main (51a46a440).

Premise ✅: content/blog/context-window-is-the-constraint.mdx present.

⚠️ This is the FOURTH host of the ~16k measurement. ⛔ Do not sweep the other three — but do read how they now describe it, so this page does not become the fourth different description. If the four disagree after your change, that is a worse outcome than the stale phrasing you were sent to fix; report it rather than unilaterally reconciling.

⛔ It is a blog post — a dated artifact. Correcting a measurement's characterisation is in scope; rewriting the post's argument is not.

Gates: re-derive from your actual path; check:nul-bytes applies. skip-changeset before the first push.

---

Generated by Claude Code