A holon is a markdown document with a small header describing what it is and who should handle it. It can be a task, a spec, a review or a piece of knowledge. Because it is plain markdown, a person can read it and a program can act on it.
Holons are generic by design. The same document can show up as a message in one place, a note in another and a job on a worker, depending on how each product is configured to display it.
A document becomes a task. It lands in a queue on another machine, where a worker picks it up and runs it.
The same holon can render as a message, a note or data, depending on the product that receives it. One source, many views.
The queue is backed by SQLite with an atomic claim, so two workers cannot take the same task. If a worker disappears, its claim expires and the task goes back in the queue.
A holon names the role that should handle it, and Grant decides which roles may add to or read from the queue.
Holons are the common currency between products. Marco is where you author and watch them, workers execute them, and the bus announces what happened. See Holon Fabric for how to send and receive them.
Copyright (c) 1998-2026 spw1.com and steven p williams All Rights Reserved