Your AI Doesn't Need to Think. It Needs to See.
The bottleneck isn't cognition. It's perception.
The Objection
If you’ve read Agents Are the Wrong Abstraction, you already know the claim: every operation decomposes into six primitives — Policy, Procedure, Asset, Person, Event, Ledger. The agent is a pre-molded house kit. The primitives are the LEGO bricks.
But there’s an obvious objection. The one every technical person asks within five minutes:
Isn’t this just a glorified rules engine?
Yes. The deterministic core is a rules engine. That’s the point.
But a rules engine alone has two fatal problems.
Problem 1: It Can’t See
A rules engine needs structured input. The real world is unstructured.
A resident texts water everywhere kitchen floor with a blurry photo. A steward says anode rod looks pretty worn, some flaking into a voice note. A work order arrives as a voicemail. A family member writes the dishwasher is making that noise again in a group chat.
A rules engine can’t process any of that. It needs someone — or something — to turn messy reality into structured fields before a single rule can fire. Without that, the engine sits idle, waiting for data it will never get.
AI is the sensory system. It perceives — photo to condition report, speech to structured fields, free text to classified event. No rules engine can do this. No dropdown menu competes.
A dropdown says select issue type. AI reads water everywhere kitchen floor, classifies it as a plumbing emergency, extracts the location, and creates a structured event — all before the first rule fires. That’s not thinking. That’s seeing.
Problem 2: It Can’t Bootstrap
A rules engine needs rules. But most organizations don’t have written rules.
They have habits. Tribal knowledge. The way we’ve always done it. The person who knows how to inspect a water heater has been doing it for 15 years and never wrote it down. The office manager who routes work orders makes 30 judgment calls a day based on patterns she can’t articulate. The technician who just knows which vendor to call — that’s a policy, but it’s stored in his head, not in a system.
AI is the bootstrapper. It observes behavior and proposes rules.
I watched you route the last 10 HVAC calls. You always send TechCorp to buildings over 50 units and QuickFix to the smaller ones. Want me to formalize that as a routing policy?
You’ve inspected 30 water heaters. Every time the anode rod shows flaking, you flag it for replacement within 90 days. Should that be a policy?
Then the human approves, edits, or rejects — and now it’s a rule. Explicit, inspectable, auditable.
The Synthesis
A rules engine is the brain. AI is the eyes and the scribe.
When you try to make the AI the brain (the agent), you get hallucinations. When you make the AI the eyes (perception), you get a system that can actually scale.
You don’t need a smarter model. You need a better architecture.