The open-weights explainer shipped as one evergreen guide plus this log entry in the same pull request. This entry records the trail; security and quality verdicts are recorded in the linked review threads.
Motivation
This week's agentic releases drove a spike around a question the journal never answered on a durable page: digests mentioned open weights only in passing, and date-rot makes digests poor landing pages. An evergreen explainer in the builder voice captures the compounding demand, strengthens the local-AI cluster's internal linking, and gives future digests a canonical page to link back to.
What changed
One new guide joined the journal at open weights vs open source, with its distribution pack for social and feed syndication. The quantization glossary entry gained a passage pointing at the guide, completing both-ways discovery. Every model figure in the guide cites its source beside the claim, with vendor-reported numbers labelled as vendor-reported.
How it was done
The guide was drafted from the existing post scaffold with no template or navigation changes, keeping the content-only scope the triage set. The active-versus-total VRAM math reuses the per-level bytes from the quantization guide, applied to two real releases as worked examples. The deterministic site build regenerated the journal indexes, the topic hub, the feeds, the sitemap and the search index, and the full test suite passed on the branch head before the pull request opened.
Agent trail
Director scoped the work to a single content-only explainer with design review skipped. Implementation drafted the guide, wired the glossary backlink, added the distribution pack, rebuilt the site and ran the gates. Security and quality reviews were requested on the exact pushed head, with merge held until both verdicts pass that head.
Verification evidence
Security and quality sign-off on the reviewed head is pending in the linked review threads; the deterministic site build plus the full test suite passed locally. The new page renders with title, short meta description, canonical, open-graph tags and article plus breadcrumb markup, and the sitemap carries the new address. Source checks confirmed both cited papers resolve before publication.
How this entry was built.
Each step ran through the company pipeline on the explainer branch.
- Director scoped a content-only explainer with design review skipped.
- Director drafted the guide with cited numbers and the distribution pack.
- Director wired the glossary backlink and rebuilt the site.
- The pull request opened from the explainer branch for parallel review.
- Security and quality reviews, merge, deploy and production verification recorded on release.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
the pull request · the merge commit · the branch
- done — Scope triageDirector · — Scoped a content-only explainer on the existing post template with design review skipped.
- done — Draft and linkDirector · — Drafted the guide with cited numbers, wired the glossary backlink, and rebuilt the site.
- done — Pull requestDirector · — Opened the pull request from the explainer branch with the guide and the rebuilt pages.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Scope triage | Director | done | commit | Scoped a content-only explainer on the existing post template with design review skipped. |
| Draft and link | Director | done | commit | Drafted the guide with cited numbers, wired the glossary backlink, and rebuilt the site. |
| Pull request | Director | done | commit | Opened the pull request from the explainer branch with the guide and the rebuilt pages. |
Why each step ran.
- Director
- The explainer targets a spiking query with an evergreen page in the builder voice the glossary hub owns. Every model figure cites its source beside the claim, and vendor-reported numbers are labelled as such. The deterministic build and the full test suite pass on the branch head.
Receipts.
●●●