AI Executive Office — CXO Assistant Platform  ·  View 30 of 30  ·  7 · Assurance

Audit and Lineage

Everything captured, how custody is proved, and why the evidence is a snapshot rather than a query to re-run.

Editable source SVG draw.io All views
Captured at ask Caller object id · roles Question verbatim Tenant and config config version Captured at execution Plan agents selected Every tool call args · latency · result hash Model and prompt both versions Tokens and cost Evidence Value snapshot as-of, not re-run Passages cited document version Purview lineage source → measure Decision record Situation Options shown including rejected Approval who · when · limit Action + external ref Outcome verdict Custody Hash chain per tenant, per day Immutable storage legal hold · 10 y Writer cannot delete separate identity Produced on demand Evidence pack signed export To Sentinel access events Regulator view read-only what they actually saw Audit and Lineage — Reconstructing a Decision Four Months Later Security / platform Data store Application we own External / third party synchronous The evidence is a snapshot, not a query to re-run. Re-running gives today's number, which is the wrong answer to "what did the approver see?". v 1.0 · owner Data & AI Global Practice · date 2026-09

The decision that makes this work

  • Evidence is snapshotted at the moment of the answer. Re-running the query four months later gives today's number, which is the wrong answer to "what did the approver see?" — and it is how a correct decision comes to look negligent
  • The identity that writes the audit trail cannot delete from it. Immutability is enforced by a storage retention policy rather than by application logic, so an application compromise cannot rewrite history
  • Options that were shown and rejected are retained. An audit of a decision is an audit of the alternatives too

Numbers

  • 10-year retention with legal hold; per-tenant, per-day hash chain over the record set
  • Evidence pack produced on demand as a signed export, reconstructing question, plan, tool calls, model version, evidence, options, approval, action and outcome
  • Access events forwarded to Sentinel; reading a decision record is itself an audited action

Assumptions

  • Retention of 10 years assumed from public-sector norms and confirmed per contract. It is the dominant driver of long-term storage cost and should be priced explicitly
  • Purview supplies lineage from source through to measure. Where a source sits outside Purview's reach, the lineage stops at the ingestion boundary and the record says so
◀  AI Governance and Guardrails All views
Solution Architecture v1.0 · Azure-native, multi-tenant, sovereign-capable · Data & AI Global Practice · 2026-0930-audit-and-lineage