AI Executive Office — CXO Assistant Platform  ·  View 20 of 30  ·  5 · Runtime

Governed Execution

How an approval becomes a write in a system of record, and how the platform knows whether it worked.

Editable source SVG draw.io All views
CXO Decision service Policy engine Action queue Execution plane Procurement Outcome monitor 1. approve option 2 2. who may approve this value? 3. within limit · dual approval not required 4. write approval to the record 5. action proposal + idempotency key 6. claim (peek-lock) 7. re-check at execution time 8. still authorised 9. create purchase request 10. external reference PR-4471 11. executed · reference recorded 12. watch KPI for 14 days 13. compare against forecast 14. no improvement 15. reopened, with what changed Governed Execution — Approval to Verified Outcome The AI identity holds no write scope anywhere. The execution plane is the only component with a write credential, it uses a distinct connector identity per system, and it re-checks authority before it writes. v 1.0 · owner Data & AI Global Practice · date 2026-09

The control

  • The AI identity holds no write scope anywhere in the estate. The execution plane is the only component with a write credential, and it uses a distinct connector identity per target system so a compromise is bounded to one system
  • Authority is checked twice: when the approval is given, and again at execution time. Between the two, a person can leave a role or a limit can change
  • Every action carries an idempotency key. A retried queue message must not create a second purchase request

Numbers

  • Approval to write: under 30 seconds when the target system is healthy
  • Approval thresholds and dual-approval rules are tenant configuration, not code
  • Outcome watch window defaults to 14 days, set per action class

Risks

  • The failure that matters is the unknown one: the write may have succeeded while the response was lost. The action then sits in a terminal-unknown state and is reconciled against the target system's own record rather than retried blindly
  • If the decision store is unavailable, the platform refuses to execute rather than executing unrecorded. That is the one place it fails closed (view 25)
◀  The Closed Loop All views Deployment Topology  ▶
Solution Architecture v1.0 · Azure-native, multi-tenant, sovereign-capable · Data & AI Global Practice · 2026-0920-governed-execution-sequence