Event Publish¶
Publish one event onto the work-buddy Events backbone — a fire-and-forget fact ("X happened") delivered to 0..N consumers. For manual or agent-initiated emits. The type is reverse-DNS (ai.workbuddy.
. . ).
MCP name: event_publish
Category: events
Mutates state (retry policy: manual)
Parameters¶
| Name | Type | Required | Description |
|---|---|---|---|
data |
dict |
No | Opaque JSON-serializable payload |
durable |
bool |
No | If true (default), the event is logged + delivered at-least-once; if false it is a lossy UI-only fan-out |
source |
str |
No | URI-ref identifying the producer (default /wb/agent) |
subject |
str |
No | Optional CloudEvents subject |
type |
str |
Yes | Reverse-DNS event type, e.g. ai.workbuddy.demo.ping |
Details¶
Publish a single event onto the Events backbone. Durable events are appended to
db/events (deduped on (source, id)) and delivered at-least-once to any
registered consumers whose type filter matches; they also fan out immediately to
the lossy dashboard projection. durable=false events skip the log entirely
(lossy fan-out only — for UI refresh / heartbeats).
This is the controlled producer used to exercise the spine end-to-end. It is a fact emitter, not a command — to make something happen, a consumer reacts to the event.