You’re using Claude Code. Every conversation, it gets dumber. You hit your usage limit after one MCP and one CLI tool. Your CLAUDE.md file is 500 lines of rules that Claude ignores halfway through a session.
I know your pain. I’m Charles Dove, and I’ve been dealing with the same thing. But my business partner Chris Kahler built two solutions that fix these problems. They’re called BASE and CARL. They’re free. They’re open source. And nobody’s talking about them yet.
This is exactly what we covered in Episode 3 of the Agentic Operators series on the Charlie Automates YouTube channel (@charlieautomates). Let me break down everything you need to know.
The Real Problem: Your Workspace Is Rotting
Here’s what most Claude Code users don’t realize. Claude isn’t getting dumber. Your workspace is getting stale.
People work with Claude. Claude does something they don’t like. They add “never do this again” to their CLAUDE.md. They do that over and over. Before long, you’ve got a 300, 400, 500 line CLAUDE.md file. And that file loads every single session, whether those rules matter or not.
That’s a massive problem. You’re sending more noise than signal. Rules don’t get followed halfway through a session because CLAUDE.md has already drifted in the context. You’re burning tokens on instructions that aren’t even relevant to what you’re doing right now.
It’s context rot at the workspace level. And that’s what BASE and CARL solve.
What Is BASE?
BASE stands for Builder Automated State Engine. It sits at the workspace level and works as a layer that manages and maintains your entire workspace.
Think of it as the health monitor for your Claude Code environment. It tracks everything that matters to you, keeps it organized, and signals when things go stale.
Data Surfaces: The Core Concept
The biggest concept in BASE is data surfaces. A data surface is a JSON file that BASE automatically registers and reads. It gives Claude the signals that are relevant to you, and only the ones that matter.
You can create a surface for just about anything you want to persist the state of and have Claude passively know about. Projects. Clients. Tools. Content. Whatever is important to your work.
Here’s what that means in practice. Every time you set up BASE, it installs a single folder in your main workspace. The primary file is your workspace.json. Inside that, you define your “areas,” which are basically data surfaces for the things you care about.
Chris showed this live in the video. He asked Claude to “review active projects and let me know what I should work on today.” BASE immediately pulled up the full picture: active projects, deadlines, which projects were stale, what needed attention.
That’s the Jarvis from Iron Man experience. Claude knows what you’re working on before you even tell it.
Staleness Tracking
BASE also tracks the relevance of your information over time. If something was put in place two months ago, it might not be relevant anymore. BASE monitors that drift.
As information gets older, BASE signals to Claude that things need attention. It tells you to groom your data. It prevents the stale data problem that kills most people’s Claude Code setups.
Most people aren’t managing their workspace. They’re working with outdated context. And stale data is just as bad as context rot. It’s essentially context rot at the workspace level.
What Is CARL?
CARL stands for Context Augmentation and Reinforcement Layer. If BASE manages your workspace, CARL manages your rules.
Here’s the problem CARL solves. People dump every instruction into one CLAUDE.md file. Building an app? Those rules are in there. Writing content? Those rules are in there too. Managing leads? Same file. Every single session loads every single rule, whether it’s relevant or not.
CARL fixes this with a concept called domains.
Domains: Smarter Rule Management
Instead of one massive CLAUDE.md file, CARL organizes your instructions into categories called domains. Each domain gets its own set of rules. You might have a domain for development, another for content, another for projects.
Here’s where it gets smart. You set keyword phrases that you would naturally use when working in a certain area. When you tell Claude “I’m building this app,” CARL detects that keyword, finds the matching domain, and injects only those relevant rules into the system message right before Claude reads your prompt.
That means Claude gets fresh, relevant instructions at the exact moment it’s processing your request. Not 20 messages ago from a 500 line CLAUDE.md. Right now. Just in time.
Chris calls this “serving relevance at the point of time.” That’s exactly what it is.
The “Never” Pattern
One thing Chris discovered through testing is the “never” pattern for writing rules. Instead of telling Claude what to do, you specify what you don’t want. “Never do this. Never do that.”
This pattern gets much better compliance from Claude. It’s a huge factor in getting AI to perform the way you want. When you’re setting up your CARL domains, try framing your rules as things Claude should never do. You’ll see a big difference.
Rule Limits Per Domain
Best practice is to keep each domain to about seven to nine rules. Chris doesn’t go over that. When a domain hits 15 rules, BASE flags it as a candidate for cleanup.
Why? Because too many rules in a single domain defeats the purpose. You want tight, focused instructions. Not another bloated file.
How BASE and CARL Work Together
BASE and CARL are separate repos. You don’t need them together. But they work incredibly well as a pair.
Here’s an example Chris showed live. He ran a command called “BASE CARL hygiene.” This surfaces the full picture of your CARL setup: which domains are active, which rules are stale, and whether anything needs grooming.
The hygiene process showed staged proposals. These are rules that were made on the fly during regular work. When you correct Claude on something, BASE logs that correction to session memory. Later, when you run hygiene, it surfaces those corrections and asks: keep, kill, or defer?
- Keep: Turn this correction into a permanent CARL rule
- Kill: Delete it, it was a one-time thing
- Defer: Save it for the next review
This is powerful. Because here’s the truth: we correct Claude all the time and forget about it. We tell it “don’t do that” and move on. With BASE, Claude doesn’t forget. It remembers every correction. And during hygiene, it reminds you so you can decide if it should become a permanent rule.
The Pipeline for Creating Rules
Chris made an important point about creating CARL rules. It’s always better to create rules based on experience, not by guessing ahead of time. Don’t try to predict what rules you’ll need. Work with Claude. Encounter the problem. Make the correction. Then use the BASE pipeline to promote that correction into a permanent rule.
This approach ensures your rules are relevant and battle-tested. Not theoretical.
The CLAUDE.md Audit
BASE has a command that audits your existing CLAUDE.md file. It reads your file, evaluates what makes a good CLAUDE.md, and then identifies which sections are candidates for CARL domains.
It will generate those domains and rules for you. It rewrites your CLAUDE.md as a separate file. Then you decide if you want to use it.
For anyone sitting on a bloated CLAUDE.md right now, this is the fastest way to get organized. Tell Claude to look at your CLAUDE.md and figure out which rules can become domains. One prompt sets up everything.
Dev Mode: See What Claude Actually Sees
CARL has a feature called dev mode. It’s the coolest part of the whole setup, in my opinion.
Dev mode uses a hook that triggers every time you send a prompt to Claude. It shows you exactly what’s happening under the hood. What rules loaded. What domains matched. What rationale Claude used. Any gaps or issues.
If you set up rules and expect a certain behavior but don’t get it, dev mode shows you why. You can see the signal. You can see which rules Claude actually applied and which ones it missed.
This is like having browser dev tools for your Claude Code session. It helps you dial in your CARL setup until it performs exactly the way you want.
Context Bracketing
One of the techniques Chris covered is context bracketing. This is a strategy for how rules are loaded into the system message.
The idea is simple. Your rules get injected into specific blocks within Claude’s system message. CARL handles this automatically. The bracket keeps your rules fresh and relevant because they arrive at the point of processing, not at the start of the session.
This is a huge deal. When rules are loaded at session start and your session runs for 20, 30, 50 messages, those rules drift. Claude stops following them. With CARL’s bracketing approach, rules stay fresh because they’re reinjected at the moment they matter.
The Vitamin Analogy
Chris made a great analogy in the video. He called BASE and CARL the “two vitamin combo” that prevents early onset dementia with Claude.
If you’re just tinkering with Claude Code casually, you probably don’t need this. But if you’re using Claude Code to build real things, maintain a business, create deliverables, grow social media, run websites, then BASE and CARL are essential.
That’s too much to handle at one time in Claude Code. If you’re not managing everything around Claude, you’re not getting the right outputs. Period.
This Architecture Is Evergreen
One thing I love about BASE and CARL is that the frameworks are evergreen. They’re based on real business frameworks that translate into development.
Think about it. How would you organize your file drawer? Each domain is like a folder. Each rule is like a document inside that folder. You organize them by category. You keep them current. You throw out what’s stale.
The technical repos might change over time. But the principles of organizing context, serving relevant rules just in time, and maintaining workspace hygiene? Those concepts aren’t going anywhere. They work today. They’ll work next year.
How to Get Started
Both BASE and CARL are free and open source on GitHub. Here’s the fastest path to getting set up:
- Clone both repos into your workspace
- Run the BASE setup to install the workspace management folder
- Run the CARL setup to initialize your domain system
- Audit your CLAUDE.md using the BASE audit command to identify what should become CARL domains
- Start working normally and let the system capture corrections automatically
- Run hygiene periodically to review staged proposals and keep everything current
The whole setup takes minutes. And it immediately improves your Claude Code experience.
Why CC Strategic Built This
At CC Strategic, Chris Kahler and I build systems like this because we believe in one thing: if a human has to babysit it, it’s not leverage.
BASE and CARL embody that philosophy. They run in the background. They track what matters. They surface problems before they become real issues. And they make Claude Code dramatically better at following your instructions.
We haven’t seen a full-blown ecosystem for Claude Code like this anywhere else. Other people have built individual solutions. But a complete workspace management and context reinforcement system? That’s what BASE and CARL deliver together.
If you want to go deeper, Chris covers the hooks, the technical setup, and advanced configurations inside our Skool community. The “From Zero to Dangerous” course walks you through everything from level one to level five.
FAQ
What does BASE stand for?
BASE stands for Builder Automated State Engine. It’s a workspace management layer for Claude Code that tracks projects, manages data surfaces, monitors staleness, and keeps your context fresh.
What does CARL stand for?
CARL stands for Context Augmentation and Reinforcement Layer. It organizes your rules into domains that load only when they’re relevant, based on keyword matching from your prompts.
Do I need both BASE and CARL?
No. They work independently. But they’re designed to complement each other. BASE manages your workspace health. CARL manages your rules. Together, they prevent context rot at both the session and workspace levels.
Is this free?
Yes. Both BASE and CARL are free and open source on GitHub.
How is CARL different from just using a CLAUDE.md file?
A CLAUDE.md file loads every rule, every session, whether relevant or not. CARL organizes rules into domains and only loads the ones that match what you’re working on. It reduces noise, saves tokens, and gets better rule compliance from Claude.
What’s the ideal number of rules per CARL domain?
Seven to nine rules per domain. Going above that starts to defeat the purpose. If a domain gets too large, break it into smaller, more focused domains.
What is dev mode in CARL?
Dev mode is a diagnostic feature that shows you exactly what happens under the hood when you send a prompt to Claude. It reveals which domains loaded, which rules applied, and any gaps in your setup. Think of it like browser dev tools for Claude Code.
How does the hygiene process work?
When you run CARL hygiene through BASE, it reviews your setup: checks domain health, surfaces staged proposals (corrections you made during sessions), and lets you decide whether each proposal should become a permanent rule, get deleted, or get deferred to the next review.
Will BASE and CARL still work if Claude Code updates?
The frameworks are based on evergreen business principles of organization and context management. The technical repos might update, but the core approach of managing workspace state and serving relevant rules just in time will stay the same.
Where can I learn more about setting up BASE and CARL?
The best place is the Charlie Automates YouTube channel (@charlieautomates) and our Skool community. Chris goes deeper into hooks, advanced configurations, and the full Claude Code ecosystem inside the premium course.
If you’re serious about getting more out of Claude Code, these two repos are the starting point. Stop fighting a bloated CLAUDE.md file. Stop burning tokens on irrelevant rules. Set up BASE and CARL and actually fix the problem.
Join CC Strategic AI on Skool to get access to the full course, the Apex setup, and a community of builders doing real work with Claude Code.
Want hands-on help building your Claude Code ecosystem? Work with me 1-on-1 and we’ll get your setup dialed in.