Protocol Laboratory

Protocol Laboratory

Protocol Laboratory is the first executable cross-language control path.

It connects:

Rust elahd controller
        |
        | loopback-only gRPC
        v
Java dummy worker

What it proves

The laboratory proves that generated Rust, Java, and TypeScript bindings agree on the same versioned Protocol Buffer contracts.

Its hosted release gate:

1. starts the Rust controller;
2. registers a Java dummy worker session;
3. records a heartbeat;
4. force-kills the worker;
5. repeats with a fresh session generation 25 times;
6. sends a heartbeat from the original retired session;
7. requires the controller to reject that stale session.

Session rules

Worker identity and session identity are separate. A fresh session advances the generation and retires the previous session. Heartbeat sequence numbers are monotonic. A duplicate heartbeat cannot replace newer load information.

Boundary

The current registry is in memory. Plaintext transport is restricted to loopback addresses. The laboratory has no Minecraft runtime, storage, placement, ownership, failover, or gameplay authority.

It is evidence for protocol and lifecycle behavior, not a deployment example.