Event protocol
EOX
Tools can participate in the same workflow without describing their work in the same way. EOX is the protocol I designed to make those exchanges more consistent.
- My role
- Protocol designer
- The work
- Event protocol
The problem
Each integration can introduce another interpretation of a status, message, or command. If every pair of tools needs its own special translation, the coordination layer becomes harder to reason about as it grows.
What I built
Erich OS Exchange separates events, messages, and commands and gives them defined structures. JSON schemas and a reference validator make those structures checkable. Adapters translate vendor-specific hooks into that shared language. Rider is the reference node, giving the protocol a concrete place to be exercised against actual tool activity.
The result
The result is a protocol and implementation foundation for my own connected tools. It makes the meaning of an exchange explicit before adding more destinations or capabilities. EOX is a project-specific protocol, with some profiles still candidates rather than enabled features. The work demonstrates an approach I use elsewhere: make the interfaces understandable before expanding the system around them.