Hokma Solutions / Case study

An operating system for AI agents, with a person in charge

My own system, in a private repo. Built and tested on my own work and on sample data. Not a product for sale, and not yet run for a client.

My role. Designer, builder and only operator

Stack: Next.js, React, Postgres with row-level security, Python, Node test runner

Follow one request through the system

Seven stages, two moments where a person decides, and a hard stop when something breaks.

Animated sample. Every name, task and number in it is invented.

  1. QueueWork comes in
  2. StepsSplit into steps
  3. ClaimOne agent at a time
  4. GoA person starts it
  5. BuildOn its own branch
  6. ReviewA second model checks
  7. Final cardA person says yes

Stage 1 of 8

Three requests are waiting.

Each one is a goal written in plain words, not a prompt. Nothing has started yet.

  • Refresh the trial onboarding emailsNext
  • Summarise last month's refund requestsWaiting
  • Tidy the pricing page wordingWaiting

Who may do what

Access comes in steps that a person grants. Try a request and see where it stops. A job title or a clever line of text grants nothing.

  1. Anything elseRefused in code
  2. One named actionOnly after a person says yes
  3. DraftWrite something, never send it
  4. ReadOpen records this person may see
  5. ShowSee that a record exists

Pick a request

The marker shows how far it gets.

The problem

Most AI agent setups either do too little or do things nobody approved. I wanted several AI models working as one team on real work, and still never sending, spending or publishing anything without a yes from a person.

How it was built

  • Work goes into one queue, split into steps. Each step is claimed by one agent at a time for a limited time, so the same work never runs twice. A failed step is retried once, then stopped for a person to look at.
  • A person taps go before work starts. The work happens on its own branch and ends as a draft with a preview. A second, independent model reviews it, and the person gets one final card.
  • Who may use what is kept apart from what the business wants. A job title or a clever prompt grants nothing. Access comes in steps: show, read, draft, then one named action after a person says yes. Anything beyond that is refused in code.
  • A next-move finder reads only the records the signed-in person may see. Each finding cites its evidence and is marked as fact, estimate, guess or unknown. A finding that rests on a record the person cannot read is dropped.
  • A launch checklist covers eight areas, from demand to trust, and returns ready or not ready with the reasons. A plan alone never counts as done.
  • A plan-first prototype for work that takes many steps: the agent writes the whole plan, and every call is checked for permission, time and cost before it runs.

Results I can show

  • Unit, database and race tests, plus end-to-end simulations of the queue, run on every change. I show the suites running on a call.
  • The finder and the capability map run on sample companies and pass their tests, including a job title trying to grant access and a prompt trying to.

Limits

  • Built for one owner first. No client has used it yet, and I do not quote time or money saved.
  • The finder and the capability map run on sample data only. No industry is claimed as supported.
  • The plan-first prototype is not production enforcement. It is the basis for a design review, not a product.
  • Private repo. I walk you through it on a call.

Try the demos

Synthetic data. The local rules engine is the real deterministic code. The AI layer here returns sample output. No model is called.

A simulation of the two-tap approval card and the multi-provider pace router, on synthetic tasks. The agent's prediction stays hidden until you decide.

Pace router

  • Anthropic (Claude Sonnet): 54% used this week, resets in 52h (behind pace (-14 pts))
  • Google (Gemini Flash / Gem): 38% used this week, resets in 52h (behind pace (-30 pts))
  • OpenAI (gpt-4o-mini API): 79% used this week, resets in 120h (ahead of pace (+11 pts))

sc-sender · effect: external (medium)

Send today's outbound batch: 4 verified prospects

The agent's prediction is committed and hidden until you decide.

Fifteen minutes, and you will know if it's a fit.

Tell me what your team is dealing with. I will tell you whether I can help and what it would cost.

Book a 15-minute call

Prefer to write?

Send a short brief