Simple Cortex

Simple Cortex · Homepage · simplecortex.com

3 points

123

1The whole offer in four words2Many doors, one practice3Proof over adjectives

01 · The whole offer in four words

Better systems is what the practice sells. Better business is what the client keeps. The positioning leads with the promise, not a menu of capabilities.

TL;DR

Most AI consulting starts with prompts and ends with drift. I built Simple Cortex to sell the missing piece: governance, designed into the operating layer instead of buried in a prompt. It is a live full-service firm, web and brand and strategy at the core, run since 2025 out of Northern Virginia, with active client engagements. AI is the operating edge, not the headline identity. As founder and principal I built the operating model end to end: the agent contract, the routing layer, and the rules every contributor reads. That system is what the firm sells and what carries each engagement I lead.

AI was never the constraint. The operating model was.

Everyone has access now. That is not the hard part.

The hard part is knowing what work goes to which model, what it should cost, what voice it should use, what tools it can touch, and when a human must review. Without answers to those questions, AI fluency is just speed without quality. Engagements drift. Outputs lose consistency. Cost is invisible until it is a problem.

Simple Cortex treats AI like an operating model, not a shortcut. Work is routed. Voice is governed. Instructions are inspectable. Cost is visible. Judgment is designed into the system instead of buried in a prompt.

What I did

• Built the practice around governed delivery, not one-off prompting: agent personas, execution loops, tool surfaces, and review checkpoints all defined as reviewable artifacts committed to version control.
• Designed a local-first routing layer. The OpenClaw Router runs locally and classifies work across six semantic routes (code, research, organization, conversation, visual, architect), sending most of it to local models and reserving cloud fallback for the calls that need the most judgment.
• Named the registry of seven models the router chooses among, so routing is concrete, not abstract: a local classifier (llama3.2:3b) triages, local models handle companion (qwen3.5:9b), engineering (qwen3-coder-next), analysis (openclaw-qwen35-a3b-think), and vision (qwen3-vl) work, and two cloud models sit at the top of the ladder: a senior model (claude-sonnet-4-6) and an architect model (claude-opus-4-6) for the hardest calls.
• Created production agent infrastructure. Three agents in production (a CEO, a Founding Engineer, and a Researcher), each defined by a four-file contract, so persona, instructions, tools, and execution rhythm are independently reviewable.
• Codified voice, tool access, and decision rules as living documents that any contributor, including AI contributors, reads before touching client work.
• Applied the system across active client engagements in brand, product, automation, and AI-enabled operating systems.

The decision worth defending is how agents ask for a model. I made agents call the router by intent rather than name a model inline. The alternative, letting each agent hardcode its own model ID, reads simpler at first: the model an agent uses is right there in its definition. I rejected it. Binding an agent to a model ID means a swap, whether for cost, quality, or a provider outage, becomes an edit across every agent that named that model, and the cost of each call disappears into the agent instead of surfacing at the routing layer. Calling by intent puts model selection, fallback, and cost accounting in one place the operator can inspect. Portability and one line of routing change beat vendor loyalty and a sweep across prompts. <!-- TODO(mohsin): confirm this reflects the real design history. Verified from source: agents call by intent, router owns selection and fallback. NOT independently verified: that agents ever named models inline first and were migrated. If the inline-first history is real, say so; if not, the beat already stands on the rejected-alternative framing without it. -->

Two properties fall out of building it this way, and they are the reason the discipline is worth selling. Because routing lives in one layer, cost is visible by default rather than a surprise on a billing dashboard. <!-- VERIFY: an ocr costs CLI command is documented in the Simple Cortex source vault as an operator-facing cost surface, but it is not Restore the specific command name only after adding a facts.yaml entry for it. --> And because every agent is four files committed to version control and reviewed in pull requests, an operator can audit persona, instructions, tools, and execution loop instead of reverse-engineering one monolithic prompt. AI fluency here is not a model list; it is governance an operator can inspect.

Reflection

Simple Cortex supports rather than competes with the product work. It is the operating discipline behind the current ventures, including the Kintsu Medspa engagement. A practice that runs lean on governed local inference can sell that discipline back to its clients, not just the output. The forward move is pulling the persona and voice files into a shared style guide so every new agent inherits the rules by default, the same way a design system enforces token discipline across components.

Two things I would tell anyone building the same thing:

1. Governance is the product, not the overhead. The instinct on a fast engagement is to skip the contract and just prompt. I built the four-file contract and the routing layer first anyway, because the alternative is speed that quietly loses voice and blows past cost. The discipline is what a client is actually buying. 2. Local-first is a real tradeoff, not a free win. Routing most work to local models keeps cost visible and low and keeps client data off third-party servers by default. It also means I own the latency and the reliability that a cloud vendor would otherwise absorb, and I keep two cloud models on the ladder precisely because the cheapest local path is not always the right one. Choosing where judgment belongs is the design work; pretending local is always better would be a lie.