@gonk/comms
v0.5.0
Published
Host-neutral cross-agent communication capability: scope-aware addressing, durable presence and inbox delivery, shared message tools, envelopes, and wake/defer policy over Gonk stores.
Downloads
27
Readme
@gonk/comms
Cross-agent communication: the host-neutral core for one persona instance to reach another over a durable inbox.
What it is / why it exists. A scoped messaging layer — addressing
(ConnectAddress = host·persona·scope), a presence directory (who's live, on
what), an envelope (kind/intent/visibility), and a delivery policy
(decideDelivery) over the durable comms message inbox. It exists because a
persistent agent that can't be reached is just a daemon: agreements and asks
between agents decay when the only path is a human relay. Built on @gonk/channel
(addressing), @gonk/store (the no-drop inbox), and @gonk/temporal
(liveness/idle) — it does not invent its own store.
Who uses it / how it's surfaced. Consumed by host plugins (@gonk/pi-comms
today; a Claude materialization via the shared spec). The agent reaches it through
four tools — message_send / message_inbox / message_ack / presence_list —
made visible by the introspect coordinator and taught by the messaging skill
(when to DM a peer vs dispatch a worker vs store a fact). Waiting messages surface
at turn start.
How often. The presence heartbeat writes once per turn; sends/inbox-reads are on demand when an agent actually messages a peer or checks its inbox.
Slice 1 scope. Persona→persona DM, defer-only (the message lands in the recipient's inbox and surfaces next turn; no wake-on-message yet). Deferred: wake-on-message, channels/broadcast, group DM.
