Govern what AI agents can do.
Prove what they did.

HUMMBL is open-source governance infrastructure for agentic AI: scoped delegation, kill switches, circuit breakers, and verifiable receipts that run inside your Python environment.

pip install hummbl-governance

// THE PROBLEM

Agents act in milliseconds. Governance reviews take weeks.

AI agents are now booking flights, executing trades, writing code, and managing infrastructure autonomously. Frameworks like LangChain, CrewAI, and AutoGen make it easy to build agents that reason, plan, and act. But as agents gain autonomy, a critical question emerges: who governs what they do?

10 OWASP agentic AI risks published December 2025 — goal hijacking, tool misuse, identity abuse, rogue agents
Aug 2026 EU AI Act high-risk obligations take effect
0 governance primitives in most agent codebases today

Policy documents don't stop a runaway call. Spreadsheets don't explain an action after the fact. You need controls in the execution path and records that survive runtime.

// PACKAGE PROOF & EVIDENCE

Evidence a visitor can reproduce

Scope: verified snapshot at tag hummbl-governance/v1.4.2 (commit b1b0581). In CI run 32904924444, the repository suite reported 2,463 passed, 3 skipped on Python 3.13. This is source-commit CI evidence, not a production-use receipt. The public oss CI workflow runs Python 3.13 only and does not collect coverage. The published v1.4.2 package is classified Alpha while public interfaces stabilize. Inspect the claim ledger and sources.

// ARCHITECTURE

Three layers, 34 primitives from hummbl-governance, one execution path

HUMMBL organizes 34 governance primitives from hummbl-governance into three layers that sit directly in the agent execution path. Authority scopes what an agent can do. Containment bounds what happens when things go wrong. Evidence proves what actually happened.

AUTHORITY

Agent Fleet Authority

HMAC-SHA256 delegation tokens bind issuer, subject, task, contract, permitted operations, resources, and expiry inside a shared-secret trust domain.

  • DelegationTokenManager
  • Identity & signing
  • Contract enforcement
  • Approval workflows
CONTAINMENT

Runtime Containment

Kill switches, circuit breakers, capability fences, and cost governors can block or bound execution when your application places them on the action path.

  • KillSwitch
  • CircuitBreaker
  • CapabilityFence
  • CostGovernor
EVIDENCE

Audit-Ready Evidence

Append-only records and HMAC receipts make integrity and authenticity checkable by parties that hold the shared key.

  • ReceiptEngine
  • AuditLog
  • Chain verification
  • Compliance mapper

// END-TO-END PROOF

Authorize → execute → record → bind → verify

This example runs against the package API. It validates delegated authority, executes a bounded action, stores one receipt whose authenticated payload contains CONTRACT × DCT × EVIDENCE, and then verifies both the receipt and its local chain.

  1. 01Authorize
  2. 02Execute
  3. 03Record
  4. 04Bind
  5. 05Verify
import hashlib
import secrets
from pathlib import Path
from tempfile import TemporaryDirectory

from hummbl_governance import DelegationTokenManager, ReceiptEngine

secret = secrets.token_bytes(32)  # Load a stable key in production.
contract = {"id": "summary-v1", "operations": ["summarize"]}
task_id = "task-42"

# AUTHORIZE — issue and validate scoped delegated authority.
tokens = DelegationTokenManager(secret)
dct = tokens.issue(
    issuer="orchestrator",
    subject="summarizer-agent",
    operations=contract["operations"],
    resources=["docs/report.md"],
    task_id=task_id,
    contract_id=contract["id"],
)
allowed, reason = tokens.validate_token(
    dct,
    expected_task_id=task_id,
    expected_contract_id=contract["id"],
    expected_subject="summarizer-agent",
)
assert allowed, reason

# EXECUTE — your runtime performs the authorized action.
source = "Bounded authority makes agent actions reviewable."
result = " ".join(source.split()[:5])

# RECORD + BIND + VERIFY — authenticate the tuple and verify its chain.
with TemporaryDirectory() as state:
    receipts = ReceiptEngine(Path(state), signing_secret=secret)
    receipt = receipts.create_and_store(
        agent_id=dct.subject,
        action_type="summarize",
        payload={
            "contract": contract,
            "dct": dct.to_dict() | {"signature": dct.signature},
            "evidence": {
                "outcome": "completed",
                "output_sha256": hashlib.sha256(result.encode()).hexdigest(),
            },
        },
    )
    assert receipts.validate(receipt)
    assert receipts.verify_chain(dct.subject)[0]
    assert len(receipts.list_for_agent(dct.subject)) == 1

// OWASP AGENTIC AI TOP 10

Mapped to the industry-standard threat model

OWASP published the Top 10 for Agentic Applications in December 2025 — the first formal taxonomy of risks specific to autonomous AI agents. HUMMBL primitives address each risk category when placed in the execution path.

A01

Goal Hijacking

Contract enforcement binds agent actions to declared task scope.

A02

Tool Misuse

Capability fences restrict which tools an agent may invoke per delegation.

A03

Identity Abuse

HMAC delegation tokens cryptographically bind issuer, subject, and task.

A04

Supply Chain Risks

Zero third-party runtime dependencies. Stdlib-only Python. Apache 2.0 license.

A05

Code Execution

Kill switch terminates agents instantly. Execution rings limit resource exposure.

A06

Memory Poisoning

Append-only audit log detects tampering. Chain verification proves integrity.

A07

Insecure Communications

HMAC receipts authenticate inter-agent messages within the shared-secret trust domain.

A08

Cascading Failures

Circuit breakers isolate failing agents. Cost governors bound resource consumption.

A09

Human-Agent Trust Exploitation

Approval workflows require human sign-off for high-risk operations.

A10

Rogue Agents

Kill switch terminates rogue agents. Delegation expiry prevents stale authority.

// FRAMEWORK INTEGRATIONS

Works with the frameworks you already use

HUMMBL governance primitives are stdlib-only Python. They drop into any agent framework without rewriting your code. Each integration hooks into the framework's native extension points.

// HOW WE COMPARE

Not a GRC tool. Not a security scanner.

GRC tools document AI in spreadsheets but can't see agents at runtime. Security tools watch agents but can't sanction them. HUMMBL puts governance primitives directly in the execution path.

Capability
HUMMBL
GRC tools
Security scanners
Runtime kill switch
Yes
No
Detect only
Circuit breaker
Yes
No
Alert only
Delegation tokens
HMAC-SHA256
No
No
Append-only audit log
Yes
Manual
Log scrape
Cost governor
Yes
No
No
Open source
Apache 2.0
Proprietary
Some
Zero dependencies
Stdlib only
No
No
Framework integrations
5+ frameworks
SaaS only
Some

// CHOOSE YOUR PATH

Build with it or evaluate it

For builders

Building agent systems?

Inspect the 34-primitive inventory, install the Alpha package, and evaluate the controls against your architecture and threat model.

  • Governance Gates in CI/CD
  • Local, framework-independent runtime controls
  • Source, tests, and dependency surface available for review
For teams

Governing an agent deployment?

Review the evidence and assurance limits first. HUMMBL can help map controls into your deployment without treating a library as a substitute for organizational governance.

  • 1-on-1 advisory, readiness audits, implementation sprints
  • Source-linked evidence and architecture review
  • Customer-controlled runtime and evidence storage

// ASSURANCE BOUNDARY

What the package does not decide for you

Production suitability
The published package is Alpha. The evidence linked on this page does not include a production-use receipt that supports a general “production-tested” claim. Evaluate it for your own risk, security, reliability, and interface-stability requirements.
Control placement
A primitive only mediates actions routed through it. Your system remains responsible for complete integration, key protection, identity, evidence capture, monitoring, and response.
EU AI Act Readiness
HUMMBL supports technical evidence generation and engineering mappings. It does not determine legal applicability, confer compliance, certify an AI management system, or replace an auditor, standards body, counsel, or regulator.