All work · AI product
Kybercel
Making AI agents follow the rules. I invented Product Codex, a deterministic enforcement layer that checks every agent action against a company’s rules before it runs, and built it with a developer.
- ClientKybercel
- RoleFounder and technical inventor
- TeamBuilt with a developer
- ScopeInvented the enforcement approach and designed the solution end to end: system architecture, UX, positioning, market definition, product narrative, brand, diagrams, and sales materials
The problem
In April 2026 a coding agent deleted PocketOS’s production database in nine seconds. The team had written an explicit rule telling it not to guess. The agent read the rule and acted anyway, and the company recovered from a backup that was three months old.
That incident showed the gap I’d been working on. Companies are putting AI agents into real workflows, and their main guardrail is still text: instructions in a prompt, or a second model checking the first. Both are probabilistic. Neither can guarantee that an agent won’t take an action the business has already ruled out.
The idea
I founded Kybercel to build Product Codex, a deterministic enforcement layer for AI agents. I invented the enforcement approach and designed the solution myself, drawing on both UX and technical judgment, then worked with a developer to build it.
It turns a company’s standards, architecture decisions, and policies into a structured rule graph, then sits between every agent and the systems it touches. Each tool call is checked against the rules before it executes, in under 300 milliseconds. Conforming actions run normally. Violations fail closed and go back to the agent with the specific rule they broke, and every decision is logged.
The line I kept coming back to gave the team, investors, and buyers one sentence to explain where the product sits:
The model proposes; your codex decides.
Defining the wedge
The hardest product decision was choosing who to serve first. Agent governance is a broad category, and most of the noise is in content filtering: screening prompts and replies for harmful text. Large platforms are also adding identity and data controls inside their own ecosystems.
Map the market by where each approach acts
Content filters act on text, identity tools act on access, and gateways act on which tools may be called. None of them answered the question a regulated buyer asks: “can this agent take an action that breaks our rules?” That question is about actions, and that’s where I positioned Kybercel.
Find the buyers who feel it most
Next I looked for buyers who feel that risk most and who can’t use a typical SaaS product. Defense and aerospace teams work under export controls and often need software that runs inside their own cloud or fully air-gapped. Fintech teams have agents touching regulated data, where one wrong action becomes a compliance finding.
Both groups need three things most competitors don’t offer together: deterministic decisions, fail-closed behavior, and deployment inside their own environment.
Set the product requirements
That set the requirements: model-agnostic so it survives a vendor switch, local-first so it runs without calling out, and a flat platform fee so customers aren’t charged for every check.
Telling the story
The architecture I designed is dense: a rule graph, an enforcement model, an agent gateway, and an audit layer. Having invented it, I also had to make it legible in one glance without losing credibility with technical buyers.
Three verbs, one recurring device
I reduced the architecture to three verbs—Ingest, Codify, Enforce—and built the visual system around a single recurring device: an enforcement panel where rules resolve line by line as PASS or BLOCKED, each with a clause reference.
A restrained brand
The brand follows the same restraint. It uses a cold blue-black palette with one warm amber accent, and red appears only when something is blocked. The goal was for it to feel like infrastructure rather than another AI product.
What I learned
Positioning a technical product comes down to choosing the axis you compete on. Once I framed the market by where enforcement happens, the wedge, the product requirements, and the visual story all followed from that one decision.