Every meaningful state change in any system, expressed in four parts.
Make AI-generated code observable, queryable, and verifiable. Finally know what AI wrote, why it broke, and how to fix it.
Four properties that make EventIDs the universal standard for AI code observability.
payments.charge.failed is instantly understandable. No magic numbers, no cryptic codes. Your entire team can read the event stream without documentation.
Query auth.% for all auth events. Query %.failed:% for all failures. The dot notation enables powerful SQL pattern matching across your entire system.
The structure teaches AI models your domain. They learn that auth contains user and session, that things can be created, failed, completed.
Schema evolves, old events remain parseable. :1 and :2 can coexist. No breaking changes, no migrations, no downtime.
EventIDs close the loop between AI code generation and observable behavior.
Declare the events your system can emit using our DSL. This becomes the contract AI must fulfill.
AI writes code that emits well-defined events from your catalog. Every action becomes observable.
Running system emits typed, queryable events. You can verify correctness in real-time.
"Event X fired 10x more than expected." AI can reason about its own output and improve.
From catalog definition to type-safe emission.
Type-safe, zero-cost abstractions. EventIDs that compile to nothing but correctness.
Whether you want to understand, implement, or experiment.
The formal specification. Grammar, semantics, edge cases, and the claim: what can and can't be modeled.
Read the specBuild EventIDs interactively. Write catalog DSL, see compiled output, query with SQL. No setup required.
Start experimentingWhy we built this. The problem with AI observability today, and why EventIDs are the solution.
Read the storyThe specification is open. The platform is ready. Start building with the universal event model today.