Control the purchase an AI agent may execute
A proposed £1,500 evaluation of one synthetic purchasing workflow.
See how exact-action controls separate reviewer identity, human approval and one-use execution.
One controlled live Microsoft identity run is verified. The £4,000 purchase was synthetic. No real funds or purchasing API.
Controlled demonstration · synthetic purchasing · 1 / 8
A sign-in does not authorise a purchase
An agent can prepare an order while its amount, supplier or underlying business state changes.
- Identify the reviewer.
- Obtain separate authority for the exact action.
- Recheck the action and business state at execution.
- Retain a distinct execution outcome; hold uncertainty.
Controlled demonstration · synthetic purchasing · 2 / 8
One live identity run; one synthetic £4,000 order
Genuine Microsoft Entra authentication
followed by two separate manual confirmations.
Retained evidence: one executed attempt, one destination record, consumed nonce and committed exposure. No duplicate or UNKNOWN outcome.
Identity admission granted zero approval, GatePass or execution permission. Separate approval used public synthetic fixture authority.
Controlled demonstration · synthetic purchasing · 3 / 8
Exact action, exact state, one use
Verified in the successful run
Reviewer/request binding, signed business-state binding and GatePass signature; separate linked decision and execution receipts.
Covered in offline cases
Changed details and state, identity substitution, replay, expired sessions, failures and UNKNOWN reconciliation.
No live mutation or replay test was performed. The shared approval/execution prompt deadline remains 120 seconds.
Controlled demonstration · synthetic purchasing · 4 / 8
Choose the evidence for the right component
| Component | Identity / distribution boundary |
|---|---|
| Controlled companion | One genuine sign-in with synthetic execution; separate repository workflow. |
| Offline source demo | Mock identity; reproducible synthetic cases; default buyer walkthrough. |
| Published local.7 | Existing synthetic SDK/CLI/MCP; no new Microsoft login packaged. |
| Operational record candidate | Separate record-update path; this run does not qualify its deployment or login. |
Controlled demonstration · synthetic purchasing · 5 / 8
£1,500: clear deliverables for one workflow
- One agreed synthetic scenario and up to five acceptance questions.
- One guided walkthrough, up to 90 minutes, with sanitised evidence review.
- Written findings: results, limits, integration gaps and GO / conditional GO / NO-GO.
- Handover up to 30 minutes and one factual-correction pass.
Proposed fee, subject to scope, availability and written agreement. Tax, payment, dates and acceptance terms to be agreed. No favourable outcome guaranteed.
Controlled demonstration · synthetic purchasing · 6 / 8
Keep the evaluation bounded
Default session: offline mock identity, synthetic inputs, no buyer credentials or system access. The prior live run is discussed through sanitised evidence only.
Excluded: new live sign-in, buyer-tenant setup, production deployment, coding, financial APIs, key custody, certification and SLA.
Public fixture keys, fixed synthetic time and same-host receipts remain limits. Historical Windows failures remain disclosed. No Microsoft endorsement or independent attestation.
Controlled demonstration · synthetic purchasing · 7 / 8
Bring one workflow to review
Nominate a workflow owner and technical reviewer.
Agree up to five acceptance questions.
Use fictional data. Agree attendees, confidentiality, access, retention and report recipients before sharing anything.
The evaluation may conclude GO, conditional GO or NO-GO. A new live integration requires separate design and approval.
Read the integration summary · Inspect sanitised validation facts
Controlled demonstration · synthetic purchasing · 8 / 8