google / google/adk-python-community

feat: post-execution audit trail pattern to complement AgentGovernancePlugin

オープン
#142 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
Python
スター
182
フォーク
75
PR マージ指標
30日以内にマージされた PR はありません

説明

Now that #141 (AgentGovernancePlugin) is merged, the pre-execution governance loop is closed: policy load → tool-call decision → allow/review/block.

The natural next question is post-execution: once the tool call is allowed and executed, is there a standard pattern for recording what actually happened in a tamper-evident way?

The gap: AgentGovernancePlugin captures the decision. Nothing currently captures the outcome — tool name, args hash, output hash, timestamp — in a form that an external auditor can verify independently.

**Proposed pattern:** an optional `audit_backend` parameter on `AgentGovernancePlugin` (or a companion hook) that receives a structured post-execution record after each allowed tool call. Implementations could range from local JSONL to on-chain anchoring (e.g. Mycelium Trails).

This would complete the loop: pre-execution policy check → execution → post-execution evidence. Both sides independently verifiable.

Happy to contribute a spec or draft implementation if there's interest.

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。