Skip to main content

5 posts tagged with "ai-agents"

View All Tags

The harness, not the brain: how a bluffing laptop model became an agent I trust

· 13 min read
Ivan Baha
Software Team Lead & Architect

Several months ago, I asked Azek to draft and send an email. A few seconds later, it replied, politely and confidently, that the draft was ready. I opened my email client – nothing there. No draft had been created, and no email tool had even been touched. My milestone note from that evening is shorter than usual: "No draft was created. No email was drafted. Azek lied."

In the first article of this series, I set out the bet behind the project: can a small AI model running privately on my own hardware do real everyday work with my mail, messages, and calendar if I build enough scaffolding around it? In the second, I showed how a tiny helper model runs alongside the main one to handle small chores, and ended by promising to show what happens when that small model is asked to supervise the big one.

Between that phantom email back then and today lie months spent living with the bet. It wasn't a straight line. There were stretches when I doubted a laptop-sized model was capable enough for real life, and for a while I switched the main seat to cloud models just to get my daily work done while I kept building. This post is the story of how I got from an assistant that bluffed to one I actually trust, and why the turning point had much less to do with the AI's brain than with the workspace I built around it.

Spec-Driven Development Is Simpler Than You Thought

· 8 min read
Ivan Baha
Software Team Lead & Architect

Spec-driven development usually arrives as a framework: a sequence of phases, a command for each, templates, a governing document, and the assumption that one developer drives one agent through one repository. Seen that way, it looks like a heavy process to adopt – and for a team with its own tracker, its own roles, and dozens of services, adopting it that way is heavy and often unnecessary.

Under the packaging, SDD is a handful of ideas. My team runs it without a framework. I designed the process around those core ideas; the team adopted it, and five months later it is simply how we work – a team lead, two engineers, a PO/BA and two QA engineers, responsible for 80+ microservices. Agents write every document; people decide, direct each stage, and take responsibility for the result. Two things made it simple: an AI-native meta-repo, where the agent sees the whole system at once, and a triage step that keeps most work away from specifications altogether.

It isn't free. A home-grown process has no community or upgrade path behind it. It fits one team's context rather than every team's, and it leans on the workspace – without one, it becomes considerably heavier.

This piece is the argument, with my team's version as the example. The mechanism, decision by decision, is in RA-005.

Two flows: why a second, simpler model runs beside the primary

· 10 min read
Ivan Baha
Software Team Lead & Architect

The most expensive thing my agent can do is ask its smartest model a trivial question.

That sounds backwards – trivial questions are supposed to be cheap. A two-line summary, a yes/no judgement, a bit of text cleanup: milliseconds of honest work for a competent model. But Azek runs on one machine, and on one machine the flagship model's attention is the scarcest resource in the system. Every small job it handles personally gets paid for twice: once in the GPU it occupies, and once in a currency most people never see billed.

So Azek – the self-hosted agent from the first post – runs two models side by side, on purpose. The big one talks to me. The small one does everything else. This post is about the second lane: why it exists, what drives on it, and why the split turned out to be one of the best decisions in the whole project.

Why I'm building my own AI agent (and why it runs on my hardware)

· 9 min read
Ivan Baha
Software Team Lead & Architect

Last month my AI agent spent eight minutes turning one email into a calendar event. Five of those minutes were pure waste – the model fumbling with tool parameters, failing validation, retrying, fumbling again. I sat there watching tool_input_invalid errors scroll past, produced by software I own completely, running on hardware I paid for, doing a task any cloud assistant finishes before you've put the phone down.

I'd do it all again tomorrow. This post is about why – and it's the opening move of a series about what it actually takes. (Part 2 looks at why a second, simpler model runs beside the primary, and Part 3 tells the story of how the harness finally made the local model reliable.)

Because the obvious question deserves a straight answer. It's 2026. Capable AI agents are a commodity: sign up, connect Gmail, press "allow," done. Why would anyone build one from scratch and insist it runs on a laptop?

Enterprise AI Compliance: Steerings Over Skills

· 5 min read
Ivan Baha
Software Team Lead & Architect

Engineering teams frequently misconfigure AI coding agents (Copilot, Kiro, Claude, Codex, and others) by relying exclusively on on-demand skills — callable procedures and tool descriptions defined in an agent's tool registry (such as those conforming to the agentskills.io standard) — to enforce strict project rules. This approach fundamentally misunderstands the architecture of foundation models. When compliance mandates are embedded within dynamic tool descriptions, they are subject to conditional execution and instructional distraction. To prevent agents from silently violating security baselines and tooling mandates, organisations must implement a dual-layer architecture: static steerings for immutable boundaries and dynamic skills for isolated execution.