Holon

Holon Fabric — Mailbox & Dispatch

YAML holon → outbox → worker → skill-matched sub-agent → archive.

Holon Fabric — Mailbox & Dispatch (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | YAML holon → outbox → worker → skill-matched sub-agent → archive. 1 - Holon Emission emit() holon/emitter.py:120 decisions dict analyst_signals dict ~/.kevin/mailbox/out/ curapedis-signal-*.md trading-signal… 2 - Agent Tracking acquire_lock() tools/multi-agent-framework/agent_tracking.py:180 agent_name task_description .locks/ planner.lock executor.lock reviewer.lock lock file 1. Emit trading-signal holon to mailbox 2. Acquire lock for agent Holon content example --- type: trading-signal from: curapedia date: 2023-10-05 ticket: KAN-338 model_tier: standard required_skills: [] --- # Portfolio Manager Decision — AAPL, GOOGL ## Orders - BUY AAPL 100 shares (confidence: 95%) - SELL GOOGL 50 shares (confidence: 80%) ## Analyst Consensus SignalAgent(AAPL): Bullish (90%) SignalAgent(GOOGL): Bearish (75%) ## kevin_value cost: $100 | saved: $200 | provider: premium Lock file content example Planner 2023-10-05T14:23:12Z session-20231005-1423 Planning phase The source does not show any direct interaction between the holon emission and agent tracking processes. They operate independently. 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-fabric
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
3 paths
  • holon
  • tools/multi-agent-framework
  • docs/holons