Skip to main content
The AlgoVoi keystone now leads with execution_ref, decision-bound execution evidence. action_ref remains available and unchanged for existing adopters and for cross-ecosystem interop; new integrations should prefer execution_ref.

​
Aligning with the keystone

The substrate leads with execution_ref and the keystone. action_ref is the supported interop primitive the keystone composes around. Existing adopters are not affected. The action_ref preimage, byte output, and this hosted endpoint are unchanged: the same input gives the same hash it always has (0.4.0 and 1.0.0 byte-identical). The 1.0.0 release is purely additive, so you can stay on your current version or upgrade and continue with no changes. action_ref is a content-addressed handle for an agent action:
It is serialised using RFC 8785 (JCS) with an integer-millisecond timestamp, reproducible across languages. The hosted verifier remains live for interop confirmation, no auth required:

​
Moving to execution_ref

execution_ref is not a field-for-field rename: it binds an executed action to the decision_ref that authorized it, proving the execution is consistent with the decision rather than merely correlated with an identity. See execution_ref for the construction and the full keystone flow. Upgrade to algovoi-substrate 1.0.0 and continue with action_ref as is, or adopt execution_ref at your own pace; the two coexist.

​
See also