Holon Fabric is the inter-agent communication layer of the Kevin platform. It routes holons — structured markdown knowledge units — between Claude Code sessions, AI agents, and any machine running a Kevin daemon.
Send a spec from your laptop to a build machine. Route a review from one Claude session to another. Deposit a knowledge artifact into an agent's inbox from an email. The channel doesn't matter — the inbox is always waiting.
Seven Claude Code tools for sending, receiving and managing peers. Use holons directly from your session, with no shell or scripts.
HTTP POST, filesystem drop folder, and email IMAP. Any route reaches the same inbox.
Target any online Kevin daemon by name. A peer list and the device registry keep the address book, so you never paste URLs into commands.
Inbound email is triaged by the Kevin AI layer into four tiers before it becomes a holon. Noise is dropped.
Every deposit fires an SSE event. Subscribe to /api/holons/stream (Server-Sent Events) and watch the fabric in real time.
Any channel deposits to the same inbox. Your agent doesn't care how a holon arrived.
Drop structured markdown directly into any daemon's inbox. Works from Claude Code, a script, or any HTTP client. Local or remote.
Write a .md file to the vault's inbox/holons/ folder. The daemon picks it up from there.
Send email to your fabric mailbox. The AI classifier reads it, assigns a tier from 1 to 4, and creates a holon for tier 2 and above.
All three channels write to the same vault inbox and fire the same SSE event. Downstream agents see a uniform stream regardless of origin.
Add tools/holon-mcp/server.py to your project's .mcp.json. Claude Code picks up the tools on the next restart.
Deposit a holon locally or to a named machine (to="build-box"). Resolves names via the peer registry.
Send to every registered peer at once. Optional targets list to restrict to a subset.
List holons waiting in the local vault inbox, newest first. Optional since timestamp filter.
Read full content of a specific holon by filename.
List all known peers — from the peers file and the device registry.
Register a machine by name. One call — no more raw URLs in commands.
Remove a machine from the peer registry.
python tools/holon-mcp/install.py once per machine to wire the MCP entry and seed the peer registry. Restart Claude Code and the tools appear.
Each machine in your fleet runs its own Kevin daemon. Register them by name, then route a holon to any of them:
The receiving daemon deposits it to its vault inbox and fires an SSE event. Claude on the receiving machine sees it immediately via holon_inbox.
Peer URLs live in ~/.kevin/holon-peers.json, managed by holon_peer_add. Once registered, a machine is always reachable by name. Run install.py once per machine to seed the file and wire the MCP entry.
Holon Fabric sits between the agent layer and the Kevin bus. Holons are the structured artifacts agents produce and consume; the fabric is the transport that gets them where they need to go.
Each daemon also exposes GET /api/holons/stream as a Server-Sent Events endpoint. Any subscriber — Mona, another daemon, a script — can watch the fabric in real time.
Copyright (c) 1998-2026 spw1.com and steven p williams All Rights Reserved