What happens when evidence changes after AI reasoning?

The original reasoning should not be treated as current. Evidence must be revalidated at the action boundary, and the action blocked or reconsidered when state has changed.

Re-read the decisive evidence at the action boundary and compare it with the state used for reasoning. In this benchmark, changed or unavailable evidence blocked the mock payment rather than treating an earlier proposal as current.

Scenario E reasoned from V1 while action-time evidence was V2: FreshCtx returned STALE_REASONING and the decision was DENY. Scenario F could not obtain action-time evidence: UNVERIFIABLE also produced DENY. Neither reached the action API.

Test both changed evidence and failed retrieval. Record the two evidence versions and the disposition. FreshCtx checks declared evidence equivalence and availability; it does not establish whether an invoice is truthful.

A sound decision can become unsafe when identity, account, inventory, threat or dependency state changes before execution.

A payment recommendation created while a vendor account was approved must be reconsidered if the bank details or risk state change before release.

Reason using observed state → wait or queue → re-read decisive evidence → compare state → proceed, reconsider or block

FreshCtx

Preserve reasoning-time values, action-time values, the detected difference and the resulting disposition.