mudRPC, gRPC for unstable networks

Backlog

The idea, in one breath, so every item is judged against it: a sealed envelope with gRPC’s service model inside; a nonce the host’s storage makes unique; one lifetime knob; a sans-IO peer the host pumps.

To do

  1. The reference firmware for one board (RP2040 or STM32F4, under $20), no crates: UART as the radio stand-in to a host running lan, the block in a flash sector with the epoch written first, provisioning read once over the UART; one SKILL.md, the Rust MCU integrator’s front door. Test: partition-heal over the UART shows the simulator’s peer lines; a power cut between save and epoch write is Rollback at the ground station. Blocked on one board.

  2. An HTTP/1.1 transport, for networks and hosts that pass only HTTP: a wire is a request’s body between listed peers. Waits on the owner: CLAUDE.md’s rule is that nothing listens on the internet, and a cloud host is the internet, so the rule widens or the transport binds private addresses as lan does.

Gates that need the owner, each a sprint when its input arrives: the release tag, signed with the key whose public half is .github/release-key.asc and verified by ./ci.sh release <tag>; the independent audit, last, on frozen code; the packages published under the owner’s accounts, packages/build.sh’s comment naming each command; GitBook and the articles, each naming the repository’s page as its canonical original; Xcode for the iOS simulator run and the Android SDK for the emulator run; item 16’s decision on the internet rule.

What is never built, with the reason already in SPEC.md: a transport, a byte-pipe stream, a second handle for the management plane, padding and cadence in core, a supersedes flag, a registry or broker, packages before 3.0.

Later (not a sprint)