Notes

How Claude systems actually survive production.

Short field notes from certified engineers. We write about eval harnesses, MCP servers, Claude Code, and the hiring mistakes that keep pilots stuck in demo mode. Every piece is meant to help you ship, or to tell you honestly when you should not.

What we publish, and why

This is a studio blog, not a newsroom. We publish when we have a pattern that keeps showing up in repos: missing evals, tool schemas Claude will not call, agents with no budget ceiling, teams hiring generalists to learn Claude on the client's clock.

The notes sit in four clusters that match the work we sell. Production agents cover evaluation, guardrails, and cost. MCP and tools cover the contract between Claude and your systems of record. Claude Code covers repo conventions and enablement. Hiring covers when an audit is enough and when you need a six-week build.

If you want the work done inside your repository rather than described here, book a 15-minute discussion.

Production agents

Eval harnesses, guardrails, cost ceilings, and agents that survive real traffic.

Production agents

LLM-as-judge rubrics you can defend in CI

LLM-as-judge is fine when the rubric is boring, structured, and checked by a human. Here is how we score Claude agents without turning CI into a $12 hobby.

June 22, 2026/2 min read

Production agents

Golden datasets for Claude agents

A golden dataset for Claude is a named, versioned set of real cases with invariants, not a folder of happy-path chats. Here is how we build one that CI can fail.

April 27, 2026/2 min read

MCP and tools

Tool schemas Claude actually calls, and MCP servers that clear a security review.

MCP and tools

MCP server security review that clears InfoSec

An MCP server is a permissioned adapter, not a chatbot plugin. Here is the security review we run before Claude gets hands on Salesforce, SAP, or your internal APIs.

June 1, 2026/2 min read

MCP and tools

Tool schemas Claude actually calls

Claude skips, mis-fills, or over-calls tools when the schema is written for OpenAPI completeness instead of for a model. Here is how we design MCP tools that get used correctly.

May 4, 2026/5 min read

Claude Code

Repo conventions, CLAUDE.md, and enablement so your team keeps shipping after we leave.

Claude Code

CI eval gates for Claude Code changes

If Claude Code can edit prompts and tools, CI must be able to fail those edits. Here is how we gate agentic coding the same way we gate application code.

August 17, 2026/2 min read

Claude Code

CLAUDE.md that the team actually follows

CLAUDE.md is repo policy for Claude Code, not a novel. Here is what we put in it so agentic coding stays inside your conventions after we leave.

June 15, 2026/2 min read

Hiring certified engineers

When to audit, when to build, and when certification is the hiring filter.

Hiring certified engineers

Six weeks to a production Claude agent

Prototype by week two, live traffic by week six. Here is the path we run on a Production Agent Build, and what has to be true on day zero or the calendar is fiction.

August 24, 2026/3 min read

Hiring certified engineers

IP ownership when a vendor builds your Claude agent

If the prompts, evals, and MCP servers do not live in your git from day one, you are renting a demo. Here is the IP rule we sign before week one, and what to reject in a vendor contract.

July 6, 2026/3 min read

Hiring certified engineers

Architect vs Developer staffing on a Claude engagement

Developer-certified engineers build the tools and agents. Architect-certified engineers decide what must not be built. Here is how we staff both so you do not get a clever system nobody can govern.

June 8, 2026/3 min read

Subscribe in a reader via RSS.