Wire

The patch protocol's outbound half: what the server writes onto the socket.

One message kind so far. The envelope carries kind from the first message on, so the client dispatches on one field forever and a new kind is a new arm rather than a new format. Names are words, not initials: the byte budget is a goal, not a test (design/live.md §1.1), and a frame someone reads in DevTools should say what it is.

Html payloads are rendered here, at the boundary, and nowhere earlier: patches carry trees so the reference applier can apply them structurally, and the wire carries markup because that is what template.innerHTML on the other side wants. Every op spells path the same way, expect is the node name or null (null only at the anchor), and node payloads are always under html — the applier reads one shape, not seven.