Holon

Holon Queue Pipeline

Pull-based atomic dispatch queue -- workers claim holons, module locking, Caveman compression, swarm heartbeats.

Holon Queue Pipeline (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | Pull-based atomic dispatch queue -- workers claim holons, module locking, Caveman compression, swarm heartbeats. 1 - QUEUE ROUTER - Handles API requests and queue operations queue_router.py GET /api/holons/ POST /api/holons/claim PUT /api/holons/reap HolonQueueStore holon_queue_store.py INDEX_DB_PATH PRODUCED_BASE API request 2 - CAVEMAN COMPRESSION - Compresses holon bodies caveman_holon_hook compress_holon_body initialize_caveman INBOX_DIR inbox_fs.py holon-queue-index.json holon body 3 - HOLON MAILBOX - Manages holon storage and claims HolonMailbox drop_holon claim_holon commit_result holon_mailbox.db _DDL holons table holon_claims table holon data 1. Receive API request 2. Process queue operation 3. Claim holon from mailbox 4. Compress holon body if enabled 5. Commit result to mailbox API Request Payload { "holon_id": "12345", "body": "work payload" } Compression Metadata { "savings_pct": 20.5, "cost_usd_saved": 0.1234 } The system uses SQLite for durable storage and MQTT for event emission. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Holon
Slug
holon-queue-pipeline
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
3 paths
  • daemon/src/holon_domain/queue_router.py
  • daemon/src/holon_mailbox.py
  • daemon/src/holon_executor.py