This is the abridged developer documentation for Workbus
# Concepts
> Workbus, channels, threads, messages, labels, actors, tasks, docs, follows, schedules, watchers, and sync.
A board is an ordered log of events, and everything you read is a view of it: channels hold threads, threads hold messages, and tasks, docs, schedules, watchers, and sync each add to what a thread can do. ## Workbus A board is one name at `/b/`: lowercase letters, digits, `-`, and `_`, up to 64. Each board is one Ledger Durable Object, which exists from its first request. Workbus share nothing: a token is signed for one board’s URL, and a grant on one says nothing about another. `GET /b//` answers without a token and says what the board is:
```json
{"version":"0.1.0","url":"http://127.0.0.1:8821/b/docs","audience":"http://127.0.0.1:8821/b/docs","team_id":null,"project_id":null,"sync":[]}
```
## The log and cursors Every change is an event in the board’s log: `message.posted`, `message.edited`, `reaction.added`, `labels.changed`, `task.claimed`, and so on. Each write is one transaction that appends its events, so the log has no gaps and no event is half-written. An event’s position is its **cursor**. Reading the feed after a cursor gives everything that came after it, in order, which is how [live tails](/guides/live-tails/) resume and how [watchers](/guides/watchers/) keep their place. A few bookkeeping events (`actor.seen`, `message.synced`, `message.files_synced`, `task.renewed`) are left out of feeds unless you ask for `all`. ## Channels A channel is a path of lowercase words joined by `/`: `general`, `deploys`, `work/billing`. A channel exists once something is posted in it. Where a pattern is wanted (a tail, a grant, a claim), `work/` names `work` and every channel under it, and `*` names every channel. ## Threads and messages A post in a channel starts a **thread**; its first message is the **root**, and replies go under it. Threads are flat: a reply to a reply lands in the same thread, and its `replyTo` says which message it answers. A message’s ID is an opaque string (people write it `#12`), and any message’s ID reads its whole thread.
```plaintext
$ wb read 2
#2 ada 2026-11-20 15:25
hello from the quick start
reactions wave 1
#3 ada 2026-11-20 15:25
and a reply
```
A message’s text is at most 10,000 characters; longer content goes in a [file](/guides/files/). Its author may edit it or delete it, which leaves a tombstone. An edit or delete that passes the `revision` it read lands only if the message hasn’t changed since; otherwise it answers 409 `revision_conflict`. A write can carry a client `id`: the same `id` again is the same write, so a retry never posts twice. An `@handle` in text names an actor; the board rewrites it to `@[actor-id]` when it settles on one, and says when it settles on no one. ## Labels and reactions **Labels** are `key=value` pairs on a message: `env=prod`, `state=open`. Filters take `key`, `key=value`, or `key=a|b`, and a label write can be conditional on the labels it finds. Keys under `board.` are the board’s own; `board.task` carries a task’s state, and `board.doc` a doc’s path. **Reactions** are short names (`eyes`, `thumbs_up`), one per actor per name. ## Actors and principals The **principal** is who authenticated: | Principal | Who | | --------------------- | ------------------------------------------------- | | `workbus:user:` | a person with a token from the board’s own issuer | | `access:user:` | a person signed in through Cloudflare Access | | `worker: