Skip to content
Bahman Shadmehr Independent AI Systems & Automation Engineer

System patterns

11 guarantees behind reliable AI systems.

Choose what must stay true.

These are design guarantees: properties each pattern is built to keep. They are not a service warranty.

Each guarantee names something that must never fail. Next to it is the pattern that holds it: the decisions, authority, and failure modes behind it. The first six are built into my open-source honeworks packages and marked "Open source"; the others are reference designs, marked as such.

  • Every taste score says whose taste it learned and why it scored.

    The output is correct and still nobody would want it.

    Stand-in Human Judgment

    Ask people rarely, and ask them well. Open source

  • A cause stays suspected until a replay test confirms it.

    No single run looks broken, but the outputs keep getting worse.

    Cross-Run Failure Analysis

    Some bugs only exist across a thousand runs. Open source

Will be published soon

Three more patterns from the same packages, written up next.

  • Will be published soon

    Missing Is Not Zero

    Keep 'could not score', 'could not answer' and 'could not call' as distinct, typed outcomes through a whole pipeline, so failures never turn into numbers that decisions are made on.

  • Will be published soon

    Offline-First Tests for AI Code

    Test model-calling code with public fakes, recorded HTTP and contract checkers by default, and run real-model tests only behind a lock and a marker.

  • Will be published soon

    Plan, Approve, Then Run

    Declare a model or prompt comparison as a file, show its plan and cost, get a person's approval, and run it under recorded conditions so the result is worth trusting.

Not sure which fits?

Let's build something real.

Tell me what must stay true. I will suggest the right pattern.

Let's build something real Email me