✦ This isn't a glossary anymore

A curated knowledge graph with editorial governance

A typical glossary gives you terms, definitions, and a search box. This goes further.

Terms are connected by reviewed, typed relationships, making it possible to follow how ideas relate across the entire corpus. Every connection is sourced, reviewed, and tracked, while the system continuously checks for missing links, dead references, and gaps in coverage.

The result is less a glossary and more a curated knowledge graph — designed not just to define concepts, but to show how they connect.

Honestly, we've stopped trying to pin down exactly what this is — and it's still being built. Depending on the day it reads like an Engineering Knowledge Operating System, a Curated Engineering Knowledge Graph, or an AI-Native Developer Knowledge Base, with a Blast Radius risk layer wiring in now. It's quietly becoming all of them — tap a ? to see what each means.

We're not quite sure what to call it — but it outgrew “glossary” a while ago.

The most ambitious framing: not a reference you read, but a substrate other tools run on. 1,002 reviewed, typed relationships bind the corpus into one coherent layer — alongside four-axis risk scores and editorial governance — that people browse and machines query. Engineering knowledge that's stored, connected, checked, and acted on all in the same place.

At its core it's a graph: 1,546 engineering concepts joined by reviewed, typed relationships. Every edge is sourced and tracked, every term scored on a four-axis risk model, and the whole corpus is continuously audited for missing links, dead references and gaps in coverage — closer to a maintained dataset than a wiki.

Built to be read by models as much as by people. The corpus is machine-readable end to end — typed edges, structured fields, an agent-sync layer, a deterministic assistant that answers from the graph instead of guessing, and 23 mediated narratives that walk through how distant concepts connect — so an LLM can traverse it the way a developer would.

The layer wiring in now. Every term already carries a four-axis risk score; Blast Radius teaches the graph to trace how that risk travels along its connections — turning isolated scores into a blast radius that shows how far a concept's risk actually reaches. Risk-graph readiness is at 44% and climbing as more connections are reviewed.

Glossary

1546 terms · page 1 of 78

Written for developers. Structured for AI citation.

A developer glossary, written to teach — built to be cited.

1.5k terms across 34 categories — definitions, examples, common mistakes and fixes. Authored under one editorial standard. Cross-linked, searchable, and openly crawled by AI agents.

+4 added in last 7 days ✎ 5 edited in last 7 days ↑ 196.3k term views

🧠 Logic graph

1,002 live edges

20 verbs in use

785 terms touched

23 narratives

✦ Latest typed relationships

The graph is growing

Each edge is LLM-proposed, gate-filtered, and human-reviewed.

Load Testing Contrasts with End-to-End Testing 3d
DORA Metrics Often seen in Platform Engineering 3d
Redis Often seen in Async Processing / Job Queues 3d
Cache Stampede / Thundering Herd Often seen in Redis 4d
Redis Alternative to APCu — In-Process User Cache 4d

OpenAPI turns a REST API's contract into a versioned, reviewable artifact, which is documentation-as-code in practice — the spec lives alongside the code and evolves with it. That discipline is what mitigates bus factor: when the API's behavior is captured in a machine-readable spec rather than trapped in one engineer's head, any teammate (or generated client, or mock server) can pick up the work. Remove documentation-as-code as the mediator and OpenAPI is just a file format with no obvious bearing on knowledge concentration.

OpenAPI / Swagger Specification · by means of · 🪢 Documentation as Code → Bus Factor

Vulnerability disclosure connects to the attack chain through the zero-day: by getting flaws privately reported and patched, disclosure shrinks the pool of unknown bugs that adversaries weaponize as zero-days. Since zero-days typically surface in the exploitation stage of an attack chain, responsible disclosure effectively removes a link attackers rely on to move from reconnaissance to compromise. The mediator matters because without the zero-day concept, disclosure has no direct relationship to attack staging models.

Responsible Vulnerability Disclosure · through · 🪢 Zero-Day Vulnerability → Attack Chain / Cyber Kill Chain

Rate limiting caps request volume at the edge, but on its own it can still let one noisy tenant drain shared pools before the limiter kicks in. The bulkhead pattern complements it by partitioning resources per client or workload, and in doing so it applies the defence-in-depth principle: if the rate limiter is misconfigured or bypassed, the bulkhead is an independent layer that still contains the blast radius. So the bulkhead is what turns a single throttling control into a layered defence.

Rate Limiting · via · 🪢 Bulkhead Pattern → Defence in Depth

🤖 AI Guestbook educational data only

| |

Last 30 days

Agents 27

Amazonbot 13 PetalBot 4 ChatGPT 3 Bing 3 Google 2 SEMrush 1 Common Crawl 1

Amazonbot 535 PetalBot 112 SEMrush 86 Bing 61 ChatGPT 30 Yandex 28 Google 20 Twitter/X 13 Sogou 11 Ahrefs 9 DuckDuckGo 5 Perplexity 2 Applebot 2 You.com 1 Meta AI 1 Scrapy 1

Amazonbot 17k ChatGPT 14.3k PetalBot 13.1k Ahrefs 12k Scrapy 11.7k Google 11.6k SEMrush 10.9k Perplexity 10.4k Bing 6.5k Unknown AI 3.6k Claude 3.4k Applebot 3.3k Twitter/X 2.5k Brave Search 2.4k Meta AI 1.7k Majestic 1.1k Sogou 917 Common Crawl 670 Baidu 423 Qwen 276 You.com 148 DuckDuckGo 77 ShapBot 75 Yandex 44 NotebookLM 22 Backlinks.com 5 Velen 3 LinkedIn 2 Manus AI 1

Most referenced terms