Vine· Signals

Webhooks that arrive — once.

Stripe webhooks are at-least-once delivery, opaque ordering, and no replay. Vine is signed, ordered, cursor-paginated, with 90-day deterministic replay — the kind of event spine an auditor and an agent can both rely on.

Open Garden See how it works

Garden Financial · v1.3.2 — DesktopLIVE

Search…⌘K

AACME Holdings

Events

Updated Apr 29 at 14:02

VINE · /dev/events

Event spine · streaming

cursor 92,010

13:42:08Cabbage
invoice.issued
INV-2941 · ACME Holdings · $14,820.00
info
13:42:19Chard
payment.authorized
pi_2c4f1a · adyen · 240ms · 3DS
ok
13:42:30Bean
journal.posted
J-2026-04-29-04417 · sealed blake3:9f3a2c…
ok
13:42:41Celery
recon.drafted
drift −$0.18 · confidence 0.98
info
13:42:52Greenhouse
transfer.signed
cold/01 → ops/03 · 2 of 3 · USDC
ok
13:43:03Sage
ofac.hit
case 7e2c · adverse media · low
review

SIGNED · AT-LEAST-ONCE · 90D REPLAY attested ed25519

FIG. 0.A — GARDEN DESKTOP / DASHBOARDThe actual UI. No marketing simulator.

Delivery + DLQ

At-least-once delivery, with the receipts.

Every outbound webhook gets exponential-backoff retries up to 12 attempts. Failures hold in a dead-letter queue for 90 days where you can inspect, retry, or drop. Every attempt is ed25519-signed and consumers ack by cursor — replaying from any point is two API calls.

VINE · /events/deliveries

Delivery · evt_91a8c4f · invoice.issued · 4 attempts → ok

delivered · sealed receipt

SUBSCRIBERhttps://acme.example/hooks/garden

EVENT · CURSORevt_91a8c4f · invoice.issuedcursor 92010

RETRY POLICYexponential backoff · 12 attempts max2 → 32 → 256 → 1024 s …

SLAat-least-once · ordered per tenant90-day replay window

Attempts · 4

#	When	Status	Latency	Body	Outcome
#1	14:02:11.184	503	240 ms	service unavailable	fail
#2	14:02:12.402	timeout	30 s	no response · subscriber slow	fail
#3	14:02:44.118	500	1.2 s	internal · stack trace truncated	fail
#4	14:04:18.402	200	118 ms	ok · ack received	delivered

Dead-letter queue · 3 events held inspect to retry or drop

evt_4f12behttps://helsinki.example/hooks412 precondition failed · cursor stale5 attempts—
evt_7c01a8https://forerun.example/gardentls handshake failed · expired cert7 attempts—
evt_2c0911https://pinnacle.example/hk/grdnsubscriber endpoint moved · 301 not followed3 attemptsin 4m 12s

every attempt is ed25519-signed · consumers ack by cursor · DLQ events stay 90 days for manual replaySSE · webhooks · AMQP · WebSocket

Vine vs. webhook stacks

An event bus you can prove things about.

Webhooks aren't enough. You need ordering, signatures, and replay.

Capability	Stripe Webhooks	Segment	Snowplow	Vine
Signed events	secret-based	—	—	✓ ed25519
Strictly-ordered per tenant	—	—	—	✓ cursor
Deterministic replay	—	—	—	✓ 90 days
At-least-once delivery	✓	✓	✓	✓
Posts ledger entries on delivery	—	—	—	✓ Bean
Agent-readable schema	OpenAPI	—	—	✓ MCP descriptor
Schema evolution policy	additive	—	—	✓ versioned
Dead-letter visible	—	—	—	✓ inspectable

Agent-native

Agents that subscribe, not poll.

An agent connects to Vine, subscribes to topics under a capability scope, and receives ordered events as they happen. Replay from any cursor is two API calls.

MCP descriptor

tool   vine.events.subscribe   Subscribe to topic(s) under scope
tool   vine.events.replay      Replay from cursor
tool   vine.events.ack          Acknowledge cursor advance
resource  topics://vine        Live topic registry

Typed REST API

GET  /vine/v1/events              Cursor-paginated event stream
POST /vine/v1/subscriptions       Create webhook subscription
POST /vine/v1/replays             Replay from cursor
GET  /vine/v1/topics              List topics + retention
GET  /vine/v1/dlq                 Dead-letter queue

Lineage headers

Authorization: Bearer arsenal:act_vn…
X-Garden-Capability: vine.events.subscribe · topics=cabbage.* chard.*
X-Garden-Cursor: 92010
X-Garden-Signature: ed25519=…

Capability matrix