mudRPC, gRPC for unstable networks

mudRPC — how we work

SPEC.md says what we build and why. BACKLOG.md says what is being built now. This file says how. Nothing else lives here.

Rules

The loop

Each sprint takes one feature off To do in BACKLOG.md:

  1. Design its tests, for robustness, not minimality. The tests in SPEC.md are the floor.
  2. Make them green with the fewest lines, then apply the review question to each line.
  3. Harden: fuzz it, break it, try the hostile scenario against it.
  4. Write the one-line lesson in the commit message. Pick the next item. Do not predict the sprints after it.

Done means

Testing

Two layers, two files per subject, never mixed.

CI is ci.sh, run here before every push on the commit being pushed, never on GitHub: both layers, then core cross-built for the targets in SPEC.md with its size and branches checked and the two boards under QEMU; ./ci.sh release <tag> adds the long counts and builds only after they and the gate are green. Bench and relay rungs run the same scenario files through lan on the reference rig in the sim skill.