Why We Renamed Fabr to FabrCore

The Domain Problem

When I started building the project site, I went to register fabr.ai. Taken. Not parked, not squatted — someone actually had it. And I wasn't about to reach out with a "hey, can I buy your domain" email. That's not how I want to start a project.

I considered alternatives. fabr.dev? fabr.io? None of them felt right for what we were building. The .ai TLD matters for this project — it's an AI agent framework, and having the domain match the space isn't vanity, it's clarity. When someone sees fabrcore.ai, they immediately know what territory we're in.

Fabr Never Quite Felt Right

Here's the thing I can admit now: I was never really happy with "Fabr" by itself. It always felt incomplete. Like a word with a missing letter — which, technically, it is. The acronym works great: Fabricate Agent Behavior and Reasoning. But as a standalone name? It just sat there. Too short. Too ambiguous. People would ask how to pronounce it. Fab-er? Faber? F-A-B-R?

I stuck with it because naming things is hard and I had actual code to write. But every time I typed it, there was this low-grade friction. It never clicked the way a good name should.

Why FabrCore Works

FabrCore does a few things the old name didn't:

• It's immediately clear what it is. "Core" tells you this is foundational infrastructure — a framework, an engine, the layer everything else builds on.
• It establishes the relationship. OpenCaddis is built on FabrCore. Future projects will be built on FabrCore. The name says "this is the core of the Fabr ecosystem."
• It's pronounceable. Fabric-Core. Nobody's going to stumble over it in conversation.
• The domain was available. fabrcore.ai — clean, memorable, exactly right.

Is it the perfect name? Maybe not. There might be something better out there. But it fits well enough that I'm not losing sleep over it, and that's a significant upgrade from where we were.

What Actually Changed

Practically speaking: not much. The GitHub repository is now at github.com/vulcan365/FabrCore. The NuGet package is still FabrCore. The code, the architecture, the FabrAgentProxy pattern — all the same. The only things that changed are the repo name, the project site, and the way we talk about it.

FabrCore is still:

• An open-source .NET framework for building AI agent systems
• Apache 2.0 licensed
• Built on .NET 10, Orleans, and Microsoft.Extensions.AI
• The infrastructure that powers OpenCaddis

Naming Is Hard

Every developer knows the joke: the two hardest problems in computer science are cache invalidation, naming things, and off-by-one errors. This rename is proof that naming things really is that hard — and sometimes the best solution is to stop overthinking it and go with what works.

FabrCore works. Let's build.