The spec exists at docs/PROTOCOL.md, and the README itself covers the wire format, cryptographic scheme, and security architecture in detail. HTTP and WebSocket aren't interchangeable choices here: HTTP handles send/API calls, WebSocket handles real-time push delivery. They coexist intentionally.

The version jumps look like churn from the outside but 2.0 and 2.1 each landed substantial additions (persistent inboxes + mesh networking, then integrity chain + E2E encryption). Fair to be skeptical of the "reinvent email" motivation, that's a real conversation worth having, but the architecture criticism doesn't hold up on closer reading.