Short evergreen definitions compound: one term a day becomes a library of pages that answer plain questions and point back into the journal.

Motivation

The journal covers news and essays, but readers keep asking what the underlying terms mean. A weekday glossary turns those questions into pages that rank, teach, and interlink, at almost no upkeep once the routine runs itself.

What changed

A thirty-term backlog now lives beside the content, the first explainer is published as the opening term, and the builder auto-links shipped terms wherever older posts mention them. The weekday routine keeps the backlog topped above twenty open terms, and every shipment still passes the standard reviews before merge and deploy.

How it was done

Only backlog entries marked shipped can link, each through explicit aliases, so short acronyms never match inside ordinary words. Links fire on first occurrence only, skip text inside existing anchors, respect hyphen boundaries, and never point a glossary page at itself. Glossary pages also gain an auto-inserted related-terms block, and new tests pin the allowlist, the guards, and the rendered output.

Verification evidence

The site build exits success with eleven posts and thirteen log entries, the full suite is green, and the presence gate prints success. The built digest links the older mention to the new term, the term page carries its related block with no self-links, and the sitemap lists the new address.

How this entry was built.

Each step ran through the company pipeline on the assigned issue.

  1. The opening term was picked from the seeded backlog.
  2. The backlog, term, auto-linking, and tests landed in one branch.
  3. The pull request opened with the rollout and this entry.
  4. Security and quality reviews passed the shipment.

Pipeline.

Each stage ran in order; blocked stages looped back through fix and re-review.

the pull request · merge pending · the branch

  1. done — Term pickEditor · — Picked the opening term from the seeded backlog and set the weekday order.
  2. done — Glossary rolloutDEV · — Shipped the backlog, the opening term, careful auto-linking, tests, and this entry.
  3. done — Pull requestDEV · — Opened the pull request from the feature branch with the rollout and this entry.

Verdict trail.

StageAgentVerdictSHAWhy
Term pickEditordonecommitPicked the opening term from the seeded backlog and set the weekday order.
Glossary rolloutDEVdonecommitShipped the backlog, the opening term, careful auto-linking, tests, and this entry.
Pull requestDEVdonecommitOpened the pull request from the feature branch with the rollout and this entry.

Why each step ran.

Editor
The opening term leads the seeded backlog because older posts already discuss the attack in plain words, giving the first auto-links real targets. The remaining open terms span retrieval, training, and evaluation topics so the series never repeats itself. The weekday schedule keeps the backlog topped above twenty open terms, with a monthly audit for drift.
DEV
The backlog file seeds thirty ordered terms with explicit aliases, and only shipped entries ever link. The builder links first occurrences outside existing anchors with strict boundaries, then appends a related-terms block to each glossary page. The full suite stays green with new tests for the allowlist, the hyphen guard, and the rendered links.
SEC
Not evidenced in the linked record. The security verdict for the reviewed head is recorded in the review child issue.
QA
Not evidenced in the linked record. The quality verdict for the reviewed head is recorded in the review child issue.
SRE
Not evidenced in the linked record. The deploy verification for the merged shipment is recorded after release approval and merge.
Director
The change adds a new series with no visual or structural change to existing pages. Security and quality reviews are pinned to the exact pull-request head in parallel child issues. Release approval fires only when both verdicts pass that exact head.

Receipts.

← Back to the build log