17. Running a Fault-Injection Exercise for an Agent
A successful happy path proves that the system can run. A controlled failure shows whether it knows where to stop and how to recover.
Technical research notes and engineering experiments
18 篇文章,按顺序阅读或从当前问题进入。
A successful happy path proves that the system can run. A controlled failure shows whether it knows where to stop and how to recover.
A regression suite is not a rerun of a few demos. It is an executable record of failures the system must not repeat.
Authorization decides whether one principal may perform one action on one resource under specific conditions
Concurrency shortens only independent waiting time and adds result joining, cancellation, and resource pressure
Longer retention does not create stronger knowledge; unverified memory carries old errors into new tasks
A plausible answer does not prove that evidence is real, execution was authorized, or interruption recovery is correct
The model does not receive one prompt. It receives context blocks assembled from different sources for different purposes.
The model does not observe local execution; the runtime must carry evidence into the next turn
The model does not operate the system directly; it selects from the actions exposed by the runtime
Retrying a model call spends computation; retrying a send, payment, or create operation can change the external world twice