Caching layers guide plus two glossary stubs

The caching cluster gains its comparison hub: a verdict-first guide stacking four caching layers in one grid, plus prefix-caching and prompt-caching stubs that define one layer each and point back at the hub. The new pages render at the caching layers guide, the prefix caching stub, and the prompt caching stub, with a beside-each-article pack per page and this log entry shipping in the same change.

Motivation

Readers keep meeting four ideas under one name: the per-request attention store, the server reusing it across requests, the provider billing that reuse at a discount, and the application cache matching by meaning. Without one page stacking them, each new mention re-teaches the same distinctions and local runners misconfigure the layer they actually control. A single comparison hub plus two missing glossary stubs closes that gap inside the existing templates.

What changed

A new comparison now renders at the caching layers guide: a verdict-first grid over layer, stack position, resource saved, scope, and infrastructure need, one section per layer with local-runner notes on server flags, breakpoint placement, stable-content-first layout, and threshold plus retention pitfalls, followed by honest limits and answers. Two stubs join it at the prefix caching stub and the prompt caching stub, each linking the guide and each other while the builder appends the related-terms block automatically. Three beside-each-article packs carry the short social copy with canonical links.

How it was done

After the hosting preflight and a fresh branch from the main line, development drafted the guide from the comparison pattern and the stubs from the glossary pattern, verified the server flags against current upstream sources, labeled vendor-reported pricing figures as vendor-reported with links, and added the packs plus this log entry in the same change. No template, style, or builder changes were needed: the existing article pages supply the eyebrow, lead, and related grid, and the glossary index picks up the new stubs automatically. The social copy was counted by hand against its limits before saving.

Agent trail

Development implemented the pages on the feature branch and opened the pull request; security and quality reviews attach to the exact pushed head in parallel, and the merge follows only when both verdicts pass that head. Each handoff is recorded in the linked review thread so the chain stays observable.

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 guide shows the comparison grid, the per-layer sections, and the limits plus answers, both stubs render with the auto-inserted related block, and the feed plus sitemap list all three addresses. A scan of the diff finds no secrets, and security plus quality reviews attach to the exact pushed head after this pull request opens.