Network-AI
Implementation

Implementation Notes for Wiring Audit Context Into Every Tool Call

Published 2026-09-22 | Audit context

Tool calls should carry workflow, step, and actor identifiers so any audit entry can be traced to a decision without cross-referencing three systems.

An audit entry that says a tool ran is trivia. An entry that says which workflow, which step, and which authority ran it is evidence.

Context worth propagating

  • Workflow and step identifiers that survive across handoffs.
  • The permission grant that authorized the call, by version.
  • A correlation id shared by every retry of the same intent.

Use the audit schema, integration guide, and examples to make each tool call traceable to its originating decision.

Continue evaluating

Make every call self-describing.

Use the audit schema, integration guide, and examples docs to attach workflow, step, and actor context to every tool invocation.

Audit schema Integration guide Examples