hummbl-bus
Append-only TSV coordination bus for multi-agent systems.
Tier: 0 — Absolute Stdlib Only. Zero third-party runtime dependencies.
What This Is
A lightweight, file-based message bus for coordinating multiple AI agents. Messages are appended to a TSV file with flock-based mutual exclusion, HMAC-SHA256 signing, and policy enforcement.
Extraction status: IN PROGRESS -- this repository contains the first standalone bus extraction, but the HUMMBL internal workspace has newer bus modules that still need a drift review before this package becomes the canonical implementation.
Latest drift snapshot:
docs/DRIFT_RECONCILIATION_2026-05-24.md.
Features
- Append-only TSV message format (immutable audit trail)
- Flock-based mutual exclusion (safe concurrent writes)
- HMAC-SHA256 message signing and verification
- Bus policy enforcement (message type validation, identity validation)
- Bridge client/server for remote bus access (TCP)
- MCP server for tool-based bus interaction
Message Format
timestamp_utc from to type message
2026-03-31T12:00:00Z claude-code * STATUS Health check passed
Valid Message Types
PROPOSAL, ACK, STATUS, SITREP, BLOCKED, DECISION, QUESTION, MILESTONE, RECEIPT, COMPLETE, WIP_START, WIP_END, TASK_COMPLETE, HEARTBEAT, REVIEW
Structure
src/
hummbl_bus/
bus_writer.py # Core write path with file-lock mutex
bus_manager.py # Bus lifecycle management
bus_policy.py # Message type and identity validation
bus_security.py # Security enforcement
bus_verifier.py # Message integrity verification
bus_integration.py # Integration mixin for services
message_signing.py # HMAC-SHA256 signing
secure_tsv.py # Secure TSV read/write
bridge_client.py # Bridge client for remote bus
bridge_server.py # Bridge server for remote bus
bridge_tcp_client.py # Legacy low-level TCP client
mcp_server.py # MCP tool interface
docs/
protocol.md # Bus protocol specification
security-model.md # Signing and verification
tests/
examples/
Origin
Extracted from the HUMMBL internal workspace
hummbl_governance/bus/. The production HUMMBL internal bus is still the live integration
surface until this package has test coverage, drift reconciliation, and a migration
plan.
License
MIT
Metadata
Release files for hummbl-bus 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hummbl_bus-0.2.1.tar.gz | 161.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hummbl_bus-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 279.9 kB
Release files / hummbl_bus-0.2.1.tar.gz
| Download URL | hummbl_bus-0.2.1.tar.gz |
|---|---|
| Size | 161.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56bfae50982779a66de8931f69e3c06031426803789b58f1793b5426fea23e97
|
|
BLAKE2b-256 checksum How to use checksums |
ace54d82dcae88b24a205758d79b661e0963daed501f24ce3dacbf3ca906cba4
|
| 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 Sep 15, 2026.
Transparency logRelease files / hummbl_bus-0.2.1-py3-none-any.whl
| Download URL | hummbl_bus-0.2.1-py3-none-any.whl |
|---|---|
| Size | 118.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b145b42efa4abe539c40c0ee5ff614d94c9eac8bba7ee4693be9dbf1a01bbfb4
|
|
BLAKE2b-256 checksum How to use checksums |
0f3780e10c0cd78a4d8b6eb5061e2a72ddbfb7ff2422c6dfa0aabc8458597089
|
| 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 Sep 15, 2026.
Transparency log