| Property | Agent-Transaction Semantics | Systems Challenge | Techniques |
| Atomicity | A dependency-aware set of model invocations, tool calls, document mutations, and external actions. Its effects become visible only if all required operations and postconditions succeed; otherwise, all recoverable effects are rolled back or compensated. | Agent workflows are long-running, dynamically generated, and may invoke external tools. Failures can therefore leave partially updated workspaces, duplicated external actions, or outputs unsupported by completed execution. | Treating each exploration-execution-validation cycle as a semantic transaction unit with commit-or-retry semantics, validated effect-only commits, and test-driven transactional skill hubs. |
| Consistency | The execution trace may be non-deterministic, but its committed outcome must satisfy the transaction’s preconditions, postconditions, and evidence obligations. | LLM-generated plans can be syntactically executable yet semantically invalid because of incorrect tool selection, unsupported claims, schema or policy violations, stale observations, and divergence between the user’s intent and the committed outcome. | A confidence-based validation mechanism that integrates multiple reliability signals, including execution errors, decision/code confidence divergence, and LLM-based reflection feedback, with materialized skill reuse. |
| Isolation | Concurrent agent transactions must not observe or produce semantically invalid interference. Their committed effects should be equivalent to an execution permitted by a declared isolation level, while allowing safe information sharing and collaboration. | Conflicts extend beyond reads and writes to encompass prompts, memory, intermediate artifacts, tool budgets, external side effects, and derived semantic state. Moreover, conflicts often cannot be identified in advance because agents discover resources dynamically during execution. | Isolating agent and operation contexts through dependency-aware isolation policies, isolated environments, versioned workspaces, and validation-based state control. |
| Durability | Once committed, a transaction’s effects, evidence, and recovery metadata persist across failures, enabling its state to be reconstructed and audited independently of the transient LLM context. | Agent state is distributed across conversation context, model outputs, tool responses, files, databases, and external services. Model and prompt evolution complicate deterministic replay and long-term interpretation of prior executions. | Maintaining transaction-aware memory and append-only workspaces through LLM-managed knowledge-graph evolution, provenance tracing, and version-aware recovery. |