#guardrails
Every post tagged "guardrails".
39 posts · showing 11–20
-
Injection That Crosses a Handoff
The fetcher had no write tools and the analyst never saw a web page. The separation held perfectly — and routed the payload around itself, through the one field that carries prose.
-
Agent Vocabulary: What the Terms Actually Mean
People discussing the same word are frequently discussing different things. Four of the distinctions are load-bearing — and when an agent conversation isn't converging, it's usually one of them.
-
The First Agent to Deploy in a Company That Has None
The first one shapes how much latitude every later one gets. Which means the right choice usually isn't the most valuable use case — it's the one most likely to succeed where people can see it.
-
Compliance and Audit for Agent-Written Systems
The audit questions don't change — who's responsible, how do you know it's correct, show me this case. They become answerable differently, and an actor field saying "agent-service" answers the first one not at all.
-
Security Review When Nobody Wrote the Code
Human vulnerabilities carry a tell — hurried code, an obvious shortcut. Generated code is uniformly careful-looking, so scanning for the suspicious part stops working. But its consistency cuts both ways.
-
Who Adopts First, and Why It Isn't the Biggest Companies
The organizations with the most resources are frequently not the ones deploying furthest. Four things gate adoption, and large companies are structurally worse at three of them — none of which are about technology.
-
Accountability Cannot Be Delegated to a Model
"The agent decided" answers nothing — not legally, not organizationally, not to the person affected. What accountability actually requires has design consequences, including why a rubber-stamp gate is worse than none.
-
The Deploy Step Nobody Should Automate Yet
It's the easiest step to automate, saves the least time, and carries the largest tail risk. Automate the readiness report and the rollback instead — and separate deploying from releasing.
-
The Tool That Changed Under You: Supply-Chain Risk in Agent Tooling
No deploy, no prompt edit, and an ops agent started restarting services mid-investigation. A maintainer had improved a tool's documentation — and documentation, in an agent, is instruction.
-
Running Agents on a Schedule: What Changes Without a User
An agent someone triggers has a safety property nobody designs for: a person is watching. Put it on a schedule and that goes away — along with the feedback loop that was catching the errors.