hdp-crewai
HDP (Human Delegation Provenance) middleware for CrewAI — attach a cryptographic audit trail to any multi-agent crew with zero changes to your existing code.
Every task a CrewAI crew executes on behalf of a human is recorded in a tamper-evident chain of Ed25519 signatures, verifiable offline with a single public key.
pip install hdp-crewai
Quick start
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PrivateKey
from crewai import Agent, Crew, Task
from hdp_crewai import HdpMiddleware, HdpPrincipal, ScopePolicy, verify_chain
# 1. Your signing key (store in a secrets manager, never in code)
private_key = Ed25519PrivateKey.generate()
# 2. Define what the human is authorising
scope = ScopePolicy(
intent="Analyse Q1 sales data and produce a summary",
authorized_tools=["FileReadTool", "CSVAnalysisTool"],
max_hops=5,
)
# 3. Create the middleware
middleware = HdpMiddleware(
signing_key=private_key.private_bytes_raw(),
session_id="q1-review-2026",
principal=HdpPrincipal(id="analyst@company.com", id_type="email"),
scope=scope,
)
# 4. Build your crew as normal
crew = Crew(agents=[...], tasks=[...])
# 5. Attach HDP — one line, zero crew changes
middleware.configure(crew)
crew.kickoff()
# 6. Verify the delegation chain offline
result = verify_chain(middleware.export_token(), private_key.public_key())
print(result.valid, result.hop_count, result.violations)
Five design considerations
| # | Consideration | How it's handled |
|---|---|---|
| 1 | Scope observation | step_callback compares each AgentAction.tool with the declared authorized_tools and records out-of-scope attempts. It does not gate tools. |
| 2 | Recording depth | ScopePolicy(max_hops=N) caps the recorded chain. CrewAI actions continue after the chain is full. |
| 3 | Token size / performance | Ed25519 signatures are 64 bytes each (~2.6 KB for a 10-hop crew). Recording failures are logged as warnings. |
| 4 | Verification | verify_chain(token, public_key) checks record integrity offline. valid covers integrity only; recorded_after_period lists hop sequence numbers at or after expires_at. |
| 5 | Memory integration | after_kickoff persists the signed token JSON to CrewAI's storage directory (db_storage_path()) alongside task outputs for retroactive auditing. |
API reference
HdpMiddleware
HdpMiddleware(
signing_key: bytes, # Ed25519 private key (raw 32 bytes)
session_id: str, # unique ID for this crew run
principal: HdpPrincipal, # the human delegating authority
scope: ScopePolicy, # what is authorised
key_id: str = "default", # label stored in the token header
expires_in_ms: int = 86400000,
strict: bool = False, # Deprecated; True raises ValueError at construction
persist_token: bool = True, # False → skip storage write
)
| Method | Description |
|---|---|
configure(crew) |
Attach all hooks to a Crew instance |
export_token() |
Return the token dict (or None before kickoff) |
export_token_json() |
Return the token as a JSON string |
verify_chain(token, public_key)
result = verify_chain(token_dict, public_key) # Ed25519PublicKey or raw bytes
result.valid # bool
result.hop_count # int
result.violations # list[str]
result.hop_results # list[HopVerification]
result.recorded_after_period # list[int] of hop seq values at or after expires_at
HDP tokens are records and cannot gate actions. authorized_tools records a declaration and does not authorize or block tool use. Expiry does not affect valid. The strict option remains for compatibility; setting it to True raises ValueError during construction. HDPScopeViolationError remains importable but is deprecated and never raised.
ScopePolicy
ScopePolicy(
intent: str,
data_classification: str = "internal", # "public" | "internal" | "confidential" | "restricted"
network_egress: bool = True,
persistence: bool = False,
authorized_tools: list[str] | None = None,
authorized_resources: list[str] | None = None,
max_hops: int | None = None,
)
Spec
This package follows draft-helixar-hdp-agentic-delegation-03 (latest revision).
License
Apache License 2.0 — Helixar Limited
Metadata
Release files for hdp-crewai 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hdp_crewai-0.2.0.tar.gz | 16.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hdp_crewai-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.6 kB
Release files / hdp_crewai-0.2.0.tar.gz
| Download URL | hdp_crewai-0.2.0.tar.gz |
|---|---|
| Size | 16.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
735529bbb8d3945ed24f1bcafdb13cb76ad335b388556fc1b2dce14228b6d241
|
|
BLAKE2b-256 checksum How to use checksums |
046ab76da5620ec4468558c8c2f8d59c07615b75704ae70dac227e3eac226712
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logRelease files / hdp_crewai-0.2.0-py3-none-any.whl
| Download URL | hdp_crewai-0.2.0-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e94502ca283e6fea573fc268e2259f33523a852c57ba76c1980c1e5c41704de5
|
|
BLAKE2b-256 checksum How to use checksums |
5edd427e5024f445467b2517428eecb132dd13f7a903a83b336cb1dad095117f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency log