A house is not a building code.

I wrote about using ChatGPT + Codex to derive a protocol specification for Reticulum/LXMF from its Python implementation—turning “look at the source” into something closer to a language-neutral contract, with test vectors to follow.

https://salemdata.net/johnpress/?p=812

#Reticulum #LXMF #Codex #AIcoding #ProtocolDesign #EmbeddedSystems #TBeamSupreme #ESP32

@VogueLaGalere nice! However this kindnof breaks because sideband and meshchatx inject more data into LXMF packets for telemetry. I didn’t get into details too much tbh. In general anyone can add ‘protocol layer’ on top of reticulum by attaching a packet named scope. I for example was thinking of experimenting with specific telemetry packets, like Meahtastic has.
@circfruit Yes, but having a conversation about such a pure protocol as you are considering will lead to a more informed discussion if it can be parsed and a specification formulated from your code. Consideration of a protocol is best had when your have the terms of the specification defined, using AI to extract them ought to be very helpful.
@VogueLaGalere totally agree with your point. It’s much easier when you have clear specs.