Event Registry

The Event Registry is CNS's planned answer to a question every multi-tenant event platform eventually hits: once dozens of event_types exist across many apps and tenants, who governs what an event type means, what shape its data must carry, and how that shape can evolve without silently breaking a consumer? The intent is a governed, per-tenant event catalog, with versioned schemas (authored as YAML) and reusable schema Components shared across event types — so a tenant can see, at a glance, every event type it emits, validate payloads against a real schema (not just "is this valid JSON"), and evolve those schemas deliberately rather than by convention.

:::info Coming soon This chapter is a placeholder. The full design will be written up once AGENTS/specs/2026-09-20-cns-event-registry-design.md is finalized — this page will be filled in from that spec rather than drafted ahead of it. :::

What exists today

The Admin API already has a /admin/v1/event-catalog resource — a tenant-admin can register an event_type with a description and an opaque JSON Schema. Today that schema is validated only as well-formed JSON; it is not yet enforced against POST /v1/events payloads. Treat today's event catalog as a precursor to the Event Registry, not the finished feature — see API Reference → Admin API for its current shape.