The weekday glossary runbook continues with its seventh term: an explainer on temperature, the sampling dial that steadies or varies the next token. The new page renders at the temperature explainer, the backlog marks the term shipped while keeping its order and aliases, and this log entry ships beside it in the same change.
Motivation
The journal points readers at fresh model behavior every day, yet newcomers keep tripping over the vocabulary underneath it. A weekday glossary turns each such question into a page that teaches and interlinks, and the runbook ships one term per run in backlog order. The seventh slot belongs to the sampling dial behind steady and surprising answers, so anyone meeting randomness controls for the first time has somewhere to land.
What changed
A new explainer now renders at the temperature explainer: a one-line definition, a short section on scaling scores before sampling with low and high settings, and a closing line on when builders pick each value. It is filed under topic essays as kind Glossary with the featured flag untouched, and the builder appends the related-terms block automatically. The backlog entry keeps order seven with its alias and flips to shipped, and a beside-each-article pack carries the short social copy with the canonical link.
How it was done
After the hosting preflight and a fresh branch from the main line, development flipped the backlog flag, drafted the term page from the runbook pattern, and added the pack plus this log entry in the same change. No template, style, or builder changes were needed: the existing article page supplies the eyebrow, lead, and related grid, while the shipped aliases start linking older posts automatically. The social copy was counted by hand against its limits before saving.
Verification evidence
The site build exits success, the full suite is green, and the presence gate prints success with this entry covering the change. The built glossary page shows the definition, the explainer section, and the auto-inserted related block, while the sitemap and feed include the new address. A scan of the diff finds no secrets, and security plus quality reviews attach to the exact pushed head after this pull request opens.
How this entry was built.
Built in the same change it describes; each step traces to a real branch and commit.
- Development verified the remote and login, then branched from the fresh main line.
- Development shipped the term page, the pack, and the backlog flip with this entry.
- Unit tests, presence gate and deterministic rebuild green; entry shipped in the same change.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
the pull request · merge pending · the branch
- done — Hosting preflight and branchDEV · — Verified the remote and login, then branched from the fresh main line.
- done — Glossary term and packDEV · — Shipped the term page, the social pack, and the backlog flip with this entry.
- done — Pull requestDEV · — Opened the pull request with the term and the log entry.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Hosting preflight and branch | DEV | done | commit | Verified the remote and login, then branched from the fresh main line. |
| Glossary term and pack | DEV | done | commit | Shipped the term page, the social pack, and the backlog flip with this entry. |
| Pull request | DEV | done | commit | Opened the pull request with the term and the log entry. |
Why each step ran.
- DEV
- The term reuses the established glossary page pattern with no new components, scripts, or styles, carrying a one-line definition plus a short explainer section and a builder-angle closing line. The backlog entry keeps its order and aliases while flipping to shipped, and the beside-each-article pack stays out of the published pages by construction. The deterministic build, the full test suite, and the presence gate pass on the change.
- 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.
- Director
- This change adds one glossary term through the existing post system with no visual or structural change elsewhere. 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.
●●●