@zclaudia/gateway-protocol
v0.3.0
Published
Canonical wire types and constants for Gateway Protocol v4: handshake, registry, heartbeat, control plane, channels, topics, streaming HTTP, plus auth/admin/notification service DTOs. Zero dependencies.
Maintainers
Readme
@zclaudia/gateway-protocol
Canonical wire types and constants for Gateway Protocol v4 — the public contract the gateway needs for routing, connection management, and its optional services. Zero runtime dependencies.
Entries
.— handshake (peer_hello/peer_ready), registry, heartbeat,gateway_errormodel, thebackend_server_messagedirected fallback, and the channel/topic/streaming-HTTP frames, plus thePeerToGatewayMessage/GatewayToPeerMessagedirection unions.auth— credential metadata (zgd_/zgb_/zga_prefixes, public credential info) and the/api/backend/tokenexchange DTO. Storage, hashing, and issuance stay inside the gateway server.admin— DTOs for/api/admin/session,/api/admin/overviewand/api/admin/credentials. The admin token is an administrative credential and never a peer handshake secret.notifications— the optional gateway push-notification service:push_notification_requestwire message and the management API config DTO. The gateway delivers by generic fields (name filter, severity → priority); application event semantics are not interpreted here.
Application payloads are opaque (unknown): ZClaudia business contracts
live in @zclaudia/protocol.
Protocol version is 4; v3 hellos are rejected.
Shared by @zclaudia/gateway-client
and @zclaudia/gateway-backend.
Protocol spec and gateway server: zclaudia/zclaudia-gateway.
