Skip to content
Chad Brown
Chad Brown
  • Human Oversight Is Only as Good as the Conditions That Trigger It

    Putting a human in the loop is the standard answer for the moments when an autonomous system should not act alone. It is also the answer that is easiest to get wrong, because the mechanism everyone talks about, the review step itself, is not where the design lives. The review is downstream. What actually determines whether human oversight protects anything is…

    Read More Human Oversight Is Only as Good as the Conditions That Trigger ItContinue

  • A Validation Gate Is Defined by Where It Sits and What It Does When It Fires

    Once you accept that code, not a prompt, has to enforce a high-stakes constraint, the interesting question is no longer whether to add enforcement but what that enforcement is as a piece of architecture. “Add a validation layer” is a slogan, not a design. A check placed where it cannot see the thing it is meant to catch protects nothing. A check that…

    Read More A Validation Gate Is Defined by Where It Sits and What It Does When It FiresContinue

  • A Prompt Guides Behavior; Only Code Can Guarantee It

    A system prompt is an instruction the model is asked to follow, and most of the time it does. That reliability is real, and it is easy to mistake for a control. It is not one. A prompt shapes the distribution of outputs a model tends to produce; it does not close off the outputs you told it to avoid. On the…

    Read More A Prompt Guides Behavior; Only Code Can Guarantee ItContinue

  • A Fallback That Hides Its Own Degradation Is Worse Than No Fallback

    Most failure handling is built around the case where the system eventually gets what it wanted. Retry the call and it works the second time. Reach for the alternate tool and it returns. That branch is satisfying to design because every path on it ends in success, and it absorbs most of the attention a team gives to reliability. The…

    Read More A Fallback That Hides Its Own Degradation Is Worse Than No FallbackContinue

  • A Retry Is a Bounded Bet on a Passing Failure

    Retrying is the most reflexive move in error handling and the least examined. Something failed, so try it again. The reflex is defensible often enough that it survives without scrutiny, and that is exactly the problem. A retry is not a neutral safety net. It is a wager that the thing which just failed will succeed if attempted again, and that wager…

    Read More A Retry Is a Bounded Bet on a Passing FailureContinue

  • The Most Dangerous Agent Failure Is the One That Looks Like Success

    Most error handling in agentic systems is built for failures that announce themselves. An exception is thrown, a non-zero status comes back, a request times out, and the surrounding code reacts. That machinery is necessary, but it defends against the least dangerous class of failure. The failure that actually corrupts an agentic pipeline is the one that raises no signal at all: a…

    Read More The Most Dangerous Agent Failure Is the One That Looks Like SuccessContinue

  • The Recovery Path for an Agent Failure Is Decided by Where It Began

    When an agent fails, the reflex is to ask what to do about it. Retry, fall back, escalate, alert someone. That is the wrong first question. The right one is where the failure came from, because the answer determines which of those responses has any chance of working and which of them will only waste time and money on the way to the…

    Read More The Recovery Path for an Agent Failure Is Decided by Where It BeganContinue

  • LinkedIn