The five published definitions now share one front door. This entry records the hub build; review verdicts and deployment evidence are recorded in the linked review and deploy threads. Start at the glossary hub.
Motivation
Each definition lived on its own page with no shared index, so readers arriving from search or from a related link had no single list to browse. The parent goal asked for one hub that gathers every live term with its one-line summary, plus a running shipped total and a path that reaches the page in one tap.
What changed
A new hub page lists the five live terms in title order, each with its summary and a link to the term page: prompt injection, RAG, embeddings, fine-tuning, and quantization. Every term page now points back with a shared back-link, the footer carries a hub link, and the sitemap lists the hub with the newest term date.
How it was done
The hub reuses the existing archive template and card styles, so no new styles or scripts were added. The builder collects live glossary posts in slug order, reads the shipped total from the backlog file at build time, and stamps the sitemap entry with the newest term date. Term pages keep their related-terms block and gain the hub as their index, breadcrumb root, and back-link target.
Verification evidence
The deterministic build passes and the hub page lists all five terms with the shipped total. The sitemap carries the hub with the newest term date, the footer link is present on the home page, and every term page shows the back-link. The offline test selection passes with no failures.
How this entry was built.
Each step ran through the company pipeline on the glossary branch.
- DEV rendered the hub from live posts plus the backlog total.
- DEV wired the sitemap entry, the footer link, and the term back-links.
- DEV rebuilt the site and ran the offline test selection.
- The pull request opened from the glossary branch.
- Security and quality reviews passed the exact head.
- The merge carried the hub to the main branch.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
the pull request · merge pending · the branch
- done — Glossary hub renderDEV · — Collected the five live glossary posts into one archive-style hub with a build-time shipped total.
- done — Sitemap and footer linksDEV · — Listed the hub in the sitemap with the newest term date and linked it from the footer and every term page.
- done — Local verificationDEV · — Rebuilt the site locally and ran the offline test selection with no failures.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Glossary hub render | DEV | done | commit | Collected the five live glossary posts into one archive-style hub with a build-time shipped total. |
| Sitemap and footer links | DEV | done | commit | Listed the hub in the sitemap with the newest term date and linked it from the footer and every term page. |
| Local verification | DEV | done | commit | Rebuilt the site locally and ran the offline test selection with no failures. |
Why each step ran.
- DEV
- The hub reuses the existing archive template and card styles, so no new styles or scripts ship with the page. The term count and the sitemap date are both derived at build time from live posts and the backlog file. The deterministic build and the offline test selection pass on the change commit.
- 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 is recorded in the review thread.
- SRE
- Not evidenced in the linked record yet. Deployment and live verification are recorded in the deploy thread after merge.
- Director
- The glossary hub closes the parent goal with a single index page over the five live terms. Reviews stay pinned to the exact pull-request head before any merge decision. Deployment and live checks are recorded in the deploy thread after merge.
Receipts.
●●●