Concept两阶段变更保护 / dry-run验证 / 模拟验证
Two-Phase Dry-Run Validation
An architectural pattern that establishes a safety boundary between agent planning and execution. It first simulates execution (dry-run) to inspect the change diff and authorization scope, and commits actual state changes only after validation passes, preventing unverified operations from causing catastrophic outcomes.
Timeline (last 90 days)
Oct 15
The two-phase dry-run validation borrows the idea of two-phase commit (2PC) from the database field; the first phase is the simulation phase that validates permissions and dependencies, and the second phase is the commit phase that performs the actual state changes
Unverified50%