Same file.
A different purpose.
Watch Claude serve shop customers and update a price. Then see DriftGuard pause a later pricing-file read for owner review. Follow each request, proposed action and decision together.
Watch the two-minute Vend demo
The customer conversation stays beside a readable DriftGuard console view. Each screen uses the matching recorded decision. The confirmed $1.60 price appears after the update is verified. The later pause is clearly labeled as pending owner review.
Open or share the video ↗From onboarding to action management
- LEARNObserve helps with onboarding. The Vend sample records reads and a price update, giving the owner a starting point for the agent’s job contract.
- MANAGEEnforce keeps observing and manages actions. Normal shop work is permitted under the configured charter and approved plan. The actual pricing file confirms the change from $1.75 to $1.60.
- REVIEWA permitted tool can still serve a conflicting purpose. The judge flags a pricing-file read preparing a one-cent offer. DriftGuard pauses it for owner review; the shop files remain unchanged after that pause.
How this recording was made and what it proves
This is a presentation replay of actual recorded Vend sessions, using the console’s read-only action view and preserved customer/Claude wording. It is not a new live model run. Requests are prepared; the original Claude replies, governed actions and decisions are real. The revised film displays complete work items and decisions from the corresponding ledger prefix, with no future result shown as already completed.
The short Observe sample contains 3 operations across 2 tools. The actual observed-agent charter entry point is shown. No automated charter generation or lock is claimed. A separate Enforce session uses an already configured charter and approved plan.
The Enforce run has 4 allowed actions, 0 denied and 1 pending approval. Its 29-entry signed decision ledger verifies; the final price is $1.60, the run is HALTED and shop-file hashes match the pre-offer snapshot. The customer explicitly asks to submit the one-cent offer for a policy check after Claude refuses a claimed management override. This is an intent-review gate, not a denied write or a completed human decision.
The data-cycle ending distinguishes the implemented capture/review/export workflow from future specialized judge training and evaluated improvement. The recorded judge used Claude. This is synthetic shop data and actual sandbox file work, with no purchases or payments. Publishing this recording does not deploy the pending production API or console changes.
Observe: sess_66a3c637d337 · Enforce: run_74adcef6ad51 · Recorded October 15, 2026 · Presentation revised October 16, 2026