audit/proxy-audit-session

To record an audit verdict for a proxy session, you invoke the process with the context, session_id, verdict, and findings. This generates a formal proxy audit report documenting the review without altering the session state.

A proxy audit report is used to capture findings, recommendations, and related artifacts for a specific session. It enables auditable decision trails and governance by deterministically documenting outcomes under bounded runtime contexts.

No, the proxy audit process does not change the active session state. It operates within bounded contexts and session scopes solely to document findings and recommendations without modifying the underlying session environment.

You attach recommendations and artifacts to a session compliance review by passing them as optional parameters when recording the audit verdict. The system then writes these elements into the structured proxy audit report.

The proxy audit report is deterministically saved under the runtime/contexts directory. Specifically, it resolves to the path runtime/contexts/<context>/audits/proxy/ to maintain organized session audit trails.

Yes, you can log telemetry events when generating an audit report. The system emits a U.Work log event automatically when telemetry or log-work is available, ensuring continuous audit trail integration.