Recompute what an agent did: a keystone execution_ref in ADK agent state

[chopmob-cloud]

algovoi-keystone-adk stamps an AlgoVoi keystone decision into ADK agent state via a before_agent_callback, under algovoi.keystone.*, so an agent run carries a content-addressed execution_ref a reviewer recomputes from the state alone, offline, with no AlgoVoi software.

pip install algovoi-keystone-adk

from algovoi_keystone_adk import keystone_before_agent_callback, verify_trace_execution_ref

agent = LlmAgent(
    ...,
    before_agent_callback=keystone_before_agent_callback(
        decision_ref="sha256:...",        # the keystone decision that authorized the run
        action_type="payment", scope="bilateral",
        outcome="COMMITTED", executed_at_ms=1716460800000,
    ),
)
# after a run, the keystone metadata sits in callback_context.state under algovoi.keystone.*;
# recompute and check it offline:
assert verify_trace_execution_ref(state)

execution_ref = "sha256:" + SHA-256(JCS({decision_ref, action_type, scope, outcome, executed_at_ms})) (RFC 8785 JCS, integer milliseconds), so it reproduces byte for byte in any language. The callback returns None and does not skip the agent. execution_ref is the natural replacement for action_ref, and existing action_ref integrations stay backward compatible and unchanged. Apache-2.0. Background: https://docs.algovoi.co.uk/keystone

[surajksharma07]

Great use of before_agent_callback. Stamping a content-addressed execution_ref that any reviewer can recompute offline via RFC 8785 JCS with zero AlgoVoi software needed is a clean way to get verifiable audit trails out of agent state. Closing this as Show and Tell since it's a third-party package/integration rather than an ADK core issue or question, that way it stays visible without sitting in the queue. Nice work on the backward compatibility with action_ref, keep sharing what you build on ADK.