Read vs write
Separate exploratory reasoning from actions that change external systems.
Agent Reliability
Agent failures become operational incidents when actions are irreversible, retries duplicate side effects, or a model continues despite missing evidence. Recovery must be part of the workflow design.
Bound every action, make tools idempotent where possible, checkpoint durable state, use circuit breakers and approval gates, and test rollback and resume behavior under partial failure.
Use these dimensions to make the architecture decision explicit and testable.
Separate exploratory reasoning from actions that change external systems.
Limit scope, spend, records, and time per execution.
Issue short-lived, task-specific credentials.
Define the condition the system returns to after interruption.
Use these dimensions to make the architecture decision explicit and testable.
Persist plan, state, approvals, and completed side effects.
Use request keys and deduplication so retries do not repeat writes.
Define reversible actions or compensating transactions.
Stop repeated failure and require review before resuming.
Use these dimensions to make the architecture decision explicit and testable.
Validate inputs, permissions, and external state immediately before action.
Confirm the intended change actually occurred.
Inject timeouts, malformed responses, stale state, and tool outages.
Expose pause, resume, cancel, inspect, and rollback controls.
Use this as a design-review gate before release.
Place this pattern inside a broader agent architecture and operating model.
Browse memory, planning, frameworks, reliability, safety, and observability.
Open the tutorial library →Start with agent features, design patterns, benefits, challenges, and industry applications.
Open the guide →