A Cold Root Beer and a Small System

A Cold Root Beer and a Small System

It’s starting to get warmer out.

Which, at least for me, means two things:

  • more time outside
  • and the return of cold root beer

There’s something about a really good root beer that feels… complete. Not just sweet, but balanced. A little bite, a clean finish, maybe just enough carbonation to keep things interesting.

Naturally, I had a normal, reasonable thought:

I should build a system for this.


The Problem With Taste

Taste is subjective.

Everyone knows this.

But it’s also surprisingly inconsistent—even for the same person. One day something feels perfectly balanced. The next, it’s too sweet or not sharp enough.

That makes comparisons difficult.

Which, of course, makes it interesting.


Turning Root Beer Into Data

So I built a small system to try and bring a bit of structure to something inherently subjective.

Nothing overly complicated. Just a few attributes:

  • sweetness
  • bite
  • aftertaste
  • carbonation
  • overall balance

Each one gets a score, and those roll up into a simple overall rating.

The goal wasn’t to be perfect.

It was to be consistent.


First Entry

Here’s one of the entries:

👉 https://root-beer-reviews.onrender.com/rootbeers/695fc98acb0e4e4826b8118f

It breaks the score down across each attribute and shows how they combine into the overall rating.

Radar (spider) chart showing root beer ratings across sweetness, bite, aftertaste, carbonation, and overall balance.

A visual breakdown of a single root beer’s profile across key taste attributes.


What Shows Up Quickly

The interesting part wasn’t ranking root beers.

It was how sensitive the results were to the model.

A few things became obvious pretty quickly:

  • Weighting matters more than individual scores
  • “Bite” can completely change the perception of sweetness
  • A strong first impression doesn’t always translate to a good finish

In other words:

The system didn’t just rank root beer. It exposed how I evaluate it.


The Real Lesson

The moment you try to quantify something human, you’re making decisions about what matters.

Those decisions shape the outcome more than the data itself.


What Comes Next

I’ll probably add to this occasionally over time.

Not at any fixed cadence. Just whenever I come across something worth testing.

If nothing else, it’s a good excuse to try more root beer.

Purely for research purposes, of course.


And One Final Question

What’s the best root beer you’ve had?

I’m always looking for the next data point.


(And for the record, my kid recently asked what root beer was made of. I told him: beer squared.)


If you’re curious, the system itself is open source and available in this repo on GitHub as well.

Facebooktwitterredditlinkedinmail

The Hybrid Retrieval Pattern

Pattern Defined

Precise Definition: Hybrid Retrieval is an inference pattern that combines
semantic vector search with traditional keyword-based BM25 (Best Matching 25)
search, using a Reciprocal Rank Fusion (RRF) algorithm to produce a single,
unified result set.

Problem Being Solved

Vector search is excellent at “vibes” but terrible at “facts.” If you ask a
vector database for “Part #882-X,” it might return a document about “Part #881-Y”
because the semantic embedding of a part number is nearly identical to its
neighbor. This is the “Vector Hallucination” problem.

For a Director of Engineering, this creates a reliability gap. Your data needs a
map, not just a list. In the
Sovereign Vault,
where precise data retrieval is a prerequisite for high-integrity governance, a
“near miss” in retrieval is a total failure in compliance. As we saw in
Who Audits the Auditors?,
an agent can only be as reliable as the ground-truth data it can actually find.

Use Case

Consider our Vineyard Manager looking for a specific chemical application record
from 2024.

  • Vector Search might pull records about “organic fertilizers” because the
    “concept” is similar.
  • Keyword Search (BM25) will find the exact string “2024-FERT-08” but miss
    the context of why it was applied.

By using Hybrid Retrieval, the system finds the exact document via keyword
matching while using semantic search to pull the surrounding context of the soil
conditions. The Manager gets the “map” of what happened, not just a list of
similar-sounding files.

Solution

The architecture requires a two-channel retrieval engine:

  1. Two-Channel Retrieval (Parallel):
    • Dense Channel: Generate an embedding and search the vector index.
    • Sparse Channel: Run a BM25 or full-text search against the same dataset.
  2. RRF (Reciprocal Rank Fusion): Apply a mathematical scoring system to
    re-rank the results from both channels into a single, high-confidence list.

Two channels, one result: Dense and Sparse retrieval coverage at the RRF level.

In a FastAPI or Node.js environment using Meilisearch or Elasticsearch, this is often a
native feature that bridges your structured database with your unstructured AI
context.

Trade-Offs

The trade-off is Indexing Complexity vs. Precision. You are now maintaining
two types of indices for the same data, which increases your storage and
infrastructure footprint. While BM25 indices are lighter than vector indices, the
overhead in your ingestion pipeline is real.

For Technical Leaders, the cost is in the “Glue Code.” You must now manage
weightings—deciding if your system should trust the keyword or the vector channel
more for specific domains. This is another area where those two extra sprint cycles
of design are spent: tuning the balance between semantic intuition and keyword
precision.

Summary

Hybrid Retrieval ensures your AI isn’t just “guessing” at meaning. It provides
the literal anchor of keyword matching with the conceptual power of vector search.

Next Up

In two weeks, we move into the Agent Tool-Calling Pattern and build the “bandage” for the
most common break-point in agentic reliability.

Moving from Pattern to Production

The Sovereign Systems Specification will always remain entirely open-source and public. The community deserves a shared architectural vocabulary to fight the Prose Tax and secure local ingestion boundaries.

However, translating these conceptual primitives into hardened, concurrent enterprise infrastructure takes real engineering cycles. If you want to skip the trial-and-error and see these patterns in actual execution, I am opening early-access pre-orders for the Sovereign Systems Implementation Handbook.

While this public blog series explores what these patterns solve, the Handbook delivers the how, complete with:
Production-Ready Blueprints: Fully implemented, modular code frameworks mapping out each pattern.
Working Repositories: Production templates (FastAPI architectures) built for immediate deployment.
Operational Playbooks: Line-by-line code walkthroughs, deployment topologies, and failure-mode checklists.

Secure your copy at the early-access price before the official launch.

Pre-Order the Sovereign Systems Implementation Handbook via Lemon Squeezy

Inference Pattern Series

Facebooktwitterredditlinkedinmail