The local-AI shelf gains a plain-English explainer on the KV cache, the reused past-token memory that caps how many sessions fit on one card. The new page renders at the KV cache explainer, a short pack carries the social copy with the canonical link, and this log entry ships beside both in the same change.
Motivation
Agent workloads keep multiplying live sessions per card, yet newcomers meeting slow long chats or crowded servers for the first time have no page that names the memory behind it. A glossary entry turns that repeated question into a page that teaches and interlinks, and the cited vendor example gives readers a current anchor without inventing numbers. This slot belongs to the cache that trades memory for speed on every token.
What changed
A new explainer now renders at the KV cache explainer: a one-line definition, a section on context length times sessions and agent-session density, a plain-English take on cache quantization with a link to the quantization entry, a cited-example section with vendor-reported labeling and stated limits, and a local-relevance closing on context settings with links to three existing guides. It is filed under the local-AI topic as kind Glossary with the featured flag untouched, and the builder appends the related-terms block automatically. 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 drafted the term page from the established glossary 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. The social copy was counted by hand against its limits before saving, and the cited example states no numbers of its own.
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 builder sections, and the auto-inserted related block, while the sitemap and feed include the new address. Every internal link resolves to an existing page, 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 drafted the term page with the cited example, the pack, and 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.
merge pending
- done — Hosting preflight and branchDEV · — Verified the remote and login, then branched from the fresh main line.
- done — Glossary term and packDEV · — Drafted the term page with cited example plus the pack and this entry.
- done — Build and testDEV · — Rebuilt the site and ran the full suite with the presence gate green.
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 | Drafted the term page with cited example plus the pack and this entry. |
| Build and test | DEV | done | commit | Rebuilt the site and ran the full suite with the presence gate green. |
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 builder-angle sections and a cited example. Numbers stay out unless the cited report owns them, and every internal link points at an existing page. The deterministic build, the full test suite, and the presence gate pass on the change.
- SEC
- Not evidenced in the linked record yet. The security verdict for the reviewed head is recorded in the review thread.
- QA
- Not evidenced in the linked record yet. The quality verdict for the reviewed head, including the buildlog-presence check, is recorded in the review thread.
- 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, and release approval fires only when both verdicts pass that exact head.
Receipts.
●●●