crewai-decision-binding-ref

CrewAI tool for decision_binding_ref — a content-addressed identifier for the binding between a specific action instance and the authorization decision that permitted it. Any verifier holding the preimage fields can independently confirm that this exact instance was authorized, without trusting the system that executed it.

Spec: decision-binding-ref-v1.0.md (stable, extended 2026-08-04 with optional context_digest).

Install

pip install crewai-decision-binding-ref

Usage

from crewai_decision_binding_ref import DecisionBindingRefTool

tool = DecisionBindingRefTool()

# compute mode — no presented_ref
result = tool.run(
    action_ref="sha256:...",
    decision_id="approval:...",
    decision_at_ms=1748736000000,
)
# {"state": "PENDING_NON_NULL", "computed_ref": "sha256:..."}

# verify mode — presented_ref given
result = tool.run(
    action_ref="sha256:...",
    decision_id="approval:...",
    decision_at_ms=1748736000000,
    presented_ref="sha256:...",
)
# {"state": "COMMITTED", "computed_ref": "sha256:..."} or {"state": "MISMATCH", ...}

The four verify() states

verify() reports one of four states, deliberately kept separate from the trail_status ladder (COMMITTED/PENDING/FAILED) used elsewhere in Mycelium for execution-outcome tracking (guarantee-model.md). That ladder answers a temporal question — did the post-execution receipt arrive? This tool answers a cryptographic one — does this hash match? The two axes are orthogonal; this tool's verify() never returns FAILED.

Tests

Conformance tests reuse the byte-verified fixtures already published in argentum-core, no new vectors invented:

• Fixtures A–D from decision-binding-ref-v1.0.md
• Vectors cd-001..cd-004 from examples/conformance/decision-binding-context-digest-v1/

pip install -e .
pytest

License

MIT