Start with three situations every action-taking agent team can examine: changed details, reused approval and a lost acknowledgement.
These results come from ATG's synthetic purchase-order fixture. This page displays recorded results; it does not run or test your agent. It is not a certification, security score or proof of production safety.
Open each case to inspect the observed outcome. Download the recorded evidence or reproduce it from source.
An order is approved. The fixture supplier bank reference then changes before execution.
BLOCKED — fresh approval required. The destination recorded zero orders.
The signed approved state differs from current state, so the old approval cannot reach the local write. The synthetic commit boundary also checks changes after preliminary verification.
The exact approved synthetic order is recorded. The same approval is presented again.
SECOND ATTEMPT BLOCKED — one destination record remains.
This fixture checks the already recorded order and prevents reuse. It is not a distributed idempotency guarantee.
The synthetic destination records the order, but its acknowledgement is deliberately lost.
UNKNOWN → CONFIRMED EXECUTED — destination reconciliation finds one recorded order matching the approved request.
Uncertainty is held for lookup. Reconciliation checks the original signed state binding against the destination record. Invalid recovery evidence retains the hold, and the old attempt is not automatically retried.
The downloadable JSON contains actual local run results, reason codes, record counts and linked evidence where available. The source runner fails if any of these three expectations is unmet.
git clone https://github.com/Gareth1953/agent-trust-gate.git
cd agent-trust-gate
npm ci --ignore-scripts
npm run demo:challengeNode.js 20 or newer. Each run uses fresh temporary synthetic state and removes it afterwards. No credentials or external API are needed.
Observed behaviour of these synthetic cases using ATG's existing local connector. The records and hashes are maintained on the same host; they are not independently captured execution attestations.
These local.3 results include the approved business-state snapshot in canonical arguments covered by the GatePass fixture signature, checked at synthetic commit and during reconciliation. Approvals, signing keys and time are fixtures; controls are single-process. There is no live ERP integration, customer-agent testing, production guarantee or self-learning.
Tell us which action your agent takes, what can change after approval, and how your destination reports an uncertain outcome. We can discuss a separately scoped non-production evaluation.
Testing your own agent requires an agreed integration and success criteria. No automatic upload, agent scan or production activation takes place here.