Does every event hit the model?

No. Rules run first and the first match wins; repeated decision states are served from the cache, so only ambiguous cache misses reach Jev.

Can I use it without Jev at all?

Yes. Call Subscribe directly with a known event type and GoEventBus behaves as a plain high-performance event bus with no model call in the Publish path.

What order does the decision pipeline run in?

Rules, then cache, then the Jev fallback, then DecideAndSubscribe. A matched rule or a cache hit never calls the model, and execution always stays inside GoEventBus, so there is no LLM call in the Publish hot path.

How is the cache keyed, and what does it key on?

A SHA-256 hash of the event state plus the candidate keys and their descriptions, so a different candidate set is a different entry. The in-memory cache is goroutine-safe with lazy expiry, and the Cache interface is replaceable for Redis, distributed, persistent or application-specific implementations.

How does the Jev call actually reach the API?

Through OpenRouter's Decisions API using the Go standard library, so the Jev integration adds no SDK dependency, with typesafe/jev-1.13 as the default model. Using that fallback requires an OpenRouter API key and network access.

What else is in the bus besides routing?

A bounded MPMC ring buffer built with atomics and cache-line padding, typed or string projections for local dispatch, fan-out plus ordered and batch handlers, middleware, lifecycle hooks, dead-letter handling, and 12 official EventStore broker options: Redis Streams, RabbitMQ, NATS JetStream, Kafka, SQS, SNS, GCP Pub/Sub, Azure Service Bus, Pulsar, MQTT, PostgreSQL and NSQ. It targets Go 1.23+ and is MIT licensed.

What happens when the decision cache fails?

Cache failures are fail-open by default: routing continues through the fallback selector because the cache is treated as an optimization. Set StrictCache: true when a cache failure should fail the routing call instead. The built-in memory cache is goroutine-safe and lazily expires entries.

CommunityJev Integrations & Adapters

GoEventBus

High-performance Go event bus with a bounded MPMC ring buffer, fan-out and ordered handlers, plus an optional routing layer that evaluates deterministic rules first, reuses cached decisions, and asks Jev a typed Choice only for ambiguous cache misses.

See highlights

Open github.com

Stars: 73
Language: Go
License: MIT
Published by: Community
Last verified: Oct 2026

Protocol-Lattice/GoEventBus

Organization repository on GitHub

View on GitHub

GoEventBus — high-performance event bus with a decision layer.

Forks: 9
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

About this project

A high-performance event bus for Go with deterministic rules, cached decisions, and optional Jev-powered event routing. GoEventBus combines a bounded MPMC in-memory event bus with fan-out, ordered and batch handlers, middleware, lifecycle hooks, dead-letter handling, Redis Streams, RabbitMQ, and an optional decision layer for choosing which event type should execute.

Quoted from the project's README. Read the full README.

Tagscommunity go event-bus routing

Works forJev for Routing Jev for Decision gating

Used inJev for Software & DevTools Jev for Data & Analytics

Languages: Go
Platforms: OpenRouter API
Capabilities: Open sourceSelf-hostedRequires API key

Highlights

Pipeline is rules, cache, Jev fallback, then DecideAndSubscribe; matched rules and cache hits never call the model.
Default Jev model is typesafe/jev-1.13, called over OpenRouter with the Go standard library and no SDK dependency.
Cache key is a SHA-256 hash of state plus candidate keys and descriptions; the memory cache is goroutine-safe with lazy expiry.
Ships 12 broker options including Redis Streams, RabbitMQ, NATS JetStream, Kafka, SQS and PostgreSQL; targets Go 1.23+.

Watch out

MIT licensed. The decision layer is optional, and using the Jev fallback requires an OpenRouter API key and network access.

Questions about this entry

Short answers drawn from the linked project or page.

Reactions & coverage

Posts, threads, and videos about this entry from around the web.

Facebook: Intake Router keeps diagnosis out of the answer space at the front desk.

FacebookClinicnotes

YouTube: Jev explained for routing and judging, with a comparison against LLMs.

Hacker News: Vercel on using Jev for defined decisions and GPT-6 Astra when the job also has to write or use tools.

flashbrew4 pointsTypeSafe AI Jev vs. GPT-6 AstraRead the thread on Hacker News

Hacker News: ASTGL replay chose local Laya routing over hosted Jev on one Mac Studio setup.

Jmeg8r15 pointsDoes an open-weight decision model beat a hosted one? Jev vs. LayaRead the thread on Hacker News

Related terms

Glossary definitions related to this entry.

Intent routing

More Jev resources like this

Inbox Zero

12.4k

Open-source AI email assistant (Next.js, Postgres, 12k+ stars) with a decision-model layer that can run on openrouter:typesafe/jev-1.13: Jev-backed questions cover rule selection, cold-email detection, thread status, recurring patterns, unsubscribe pages, and sender categorization, each with evals.

Jev Integrations & Adapters#community#email#gmail

Community

elie222/inbox-zeroTypeScript

Admission Gate

A Kubernetes admission webhook that asks Jev to allow, flag, or deny a manifest change for intent-shaped policies a Rego rule cannot express, keeping hard rules in Rego and failing closed by default.

Jev Integrations & Adapters#community#go#kubernetes

Community

AutoGPT

187.5k

Autonomous agent platform with 187,504 stars for building and running agents from plain English or a visual builder. Its platform features first-class TypeSafe Jev decision blocks for typed routing, filtering, scoring and confidence-gated next-action dispatching.

Jev Integrations & Adapters#community#autonomous-agents#platform

Community

Significant-Gravitas/AutoGPTPython

AgentScope

33k

Alibaba's multi-agent platform, which implements native TypeSafe Jev classification through JevClassifierModel for binary, choice and score routing across agent pipelines. Python 3.11+, Apache-2.0, with a FastAPI agent service and web UI.

Jev Integrations & Adapters#community#multi-agent#framework

Community

agentscope-ai/agentscopePython

GPTCache

8.2k

A semantic cache for LLM queries, fully integrated with LangChain and llama_index. Zilliz's cache integrates TypeSafe Jev Noul checks to evaluate cache hit freshness and time-dependent query validity, cutting repeated requests and API cost.

Jev Integrations & Adapters#community#semantic-cache#langchain

Community