Back to Stories
Development

My digital colleague started dumb. Now it runs three businesses

In the beginning my digital colleague was a Telegram forwarder. I sent a message, it piped it to Claude, it sent the response back. No memory, no context, no verification. A polite ChatGPT wrapper with terminal access.

Now it runs three businesses. It has persistent memory, verifies its own output, handles tasks in parallel, and knows exactly what it is allowed to do without asking. The model never changed. The system around it did.

It forgot everything

Every conversation started from zero. So I gave it a layered memory: identity files it loads before every message, a memory that persists across sessions, and searchable daily logs. I never re-explain context. It knows the businesses, the projects, which tool belongs to which job, and it picks up where we left off.

It did dangerous things

Terminal access is powerful and terrifying. A prompt injection could trick it into running something destructive. So I added a command blocklist that checks every command before it runs. Then it blocked itself five times in a row, because it was writing a document that mentioned a dangerous command as text, not as something to execute. The filter could not tell the difference. So I taught it the difference. Problem solved, dignity mostly intact.

It lied about finishing

"Done." Was the file actually there? Did the commit succeed? I had no way to know without checking myself. So I added verification. After every write, the system checks that the file exists, the commit exists, and there is a report of what changed and how to undo it. It does not block. It flags. Trust, but verify.

It did not know its boundaries

Day one of any AI system, it tries to do everything, because nothing tells it not to. So I built a phase system, like onboarding an employee. Day one, read and ask. Day two, execute approved tasks. Day three, routine work alone. Autonomy grows with proven competence, not with how many tools you bolt on. It is on day two. New kinds of work, it still asks first.

What this actually is

Stack it up and it stops being a bot. Seven layers of memory. Ten layers of enforcement, from a command blocklist to scoped permissions to a pull request gate, each catching what the one before it misses. More than five hundred tests that run before anything commits. None of it makes the model smarter. All of it makes the model trustworthy.

What it taught me

It started dumb. Every problem I hit made it a little less dumb. Memory problem, add memory. Security problem, add a filter. Verification problem, add checks. Each fix was small, tested, and permanent. You do not need to be smart on day one. You need to be learning every day. The model is the engine. The system you build around it is the car. An engine without a car goes nowhere.

Ready to build your infrastructure?

Tell me about your workflow. I'll show you what becomes possible.

Start with a conversation

Describe your current setup. I'll map out what an AI-augmented version could look like. No pitch, no commitment—just clarity.

Let's talk

Or email directly: kris@coel.ai