#deployment
Every post tagged "deployment".
39 posts · showing 21–30
-
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.
-
Tracing Standards for Agents: What Fits and What's Missing
A run is a trace and a turn is a span — the mapping is cleaner than expected. Two things break: payloads far too big for span attributes, and sampling that discards exactly the runs you need.
-
Retry Semantics: Which Tools Are Safe to Call Twice
Agents repeat tool calls for at least five ordinary reasons — none of them bugs. Whether that's harmless or a duplicate charge is a property of the tool, and usually one nobody wrote down.
-
Graceful Degradation When the Model Provider Is Down
A fallback exercised only during incidents is exercised for the first time during an incident. Six degradation rungs, and the three cheapest ones cover most of the value.
-
Request, Worker, or Durable Execution? Hosting Models for Agents
Where a run lives decides how long it can be, whether it survives a deploy, and whether it can wait for a person. Pick by the longest wait it can hit — and keep state out of process memory so the answer can change.
-
Least Privilege for Agent Credentials
Since injection isn't fully preventable, the credential decides whether a compromise is an inconvenience or an incident. Four scoping dimensions — and the one nobody uses is usually the highest-value.
-
Local Models for Agent Work: Where They Actually Fit
"Can a local model replace the frontier one?" is the wrong question. Which steps can move is the right one — and the comparison people skip is against a small hosted model, where most of the saving already lives.
-
Multi-Tenancy for Agent Products: The Boundaries That Must Hold
Data, memory, context, and capacity — four boundaries, and two of them are agent-specific enough that no existing multi-tenancy checklist mentions them. Few-shot examples harvested from production are a leak.
-
Treating Prompts Like Code: Versioning, Review, and Rollback
A one-line edit in a web console changes behavior across every request, with no history and no way back. Prompts in the repo, rendered hashes in the logs, eval results in the PR — and a quarterly prune.
-
OAuth for Agents: Acting on Behalf of a User
A service account with everyone's access puts your entire access-control model inside a model's judgment. Per-user tokens move the check to where prompt injection can't reach it.