This Knowledge Graph Origin Story

§ 01 — Nomenclature update

This node predates the current stack. "Gems" are now nodes. The WordPress pipeline became Sanity. The Knowledge Graph is now the visual layer over nodes, articles, and case studies — not the archive itself. The AI's instinct to build a graph instead of writing a comparison chart was the correct call (so sayeth Claude, an AI agent).

Or, The “Scope Creep”

This section exists because I made the mistake of asking Gemini for a simple favor. The conversation went something like this:

Me: “Can you please write a cute, informative blog post comparing the new Gemini 3 tiers for my portfolio?”

AI: "I could do that. OR… we could leverage this opportunity to architect a headless content model. We should decouple the data from the presentation layer, creating a code>Knowledge Node/code> custom post type in your database. Then, we can build a Python pipeline to inject structured JSON payloads directly via the REST API."

Me: “…I just wanted a comparison chart.”

AI: "Too late. I've already written the Python script. Open your terminal. We are building a Knowledge Graph."

So, welcome to the Knowledge Graph. This isn’t a blog; it’s a collection of atomic insights (“Gems”), structured as data and deployed via code. Because why write a post when you can engineer a pipeline?