Use the short path to learn the programming surface, the complete workflow to understand the network beneath it, and the books/reference material when you want the full argument and engineering record.
The original learning resources remain below. Continue from them to the full Ribbit programming rules, FD&F network construction, the implementation map and the conversion record. The original books, video sequences, mechanism pages and specification remain the long route into the system.
The argument and mental model. Why the architecture rejects assumptions inherited from message-oriented distributed systems.
The engineering book: how FrogNet works, why it was built this way, and what the implementation taught us.
Programming models, semantic transport and the path from existing applications toward native shared-state programs.
Source-grounded implementation notes intended to stop the documentation from drifting away from the code.
Two different ways into the same architecture: one through the ideas, one through the engineering.
The programming model: publish your own truth, read the truths you depend on, and stop rebuilding message choreography above shared state.
Read How to Think Like a FrogThe larger engineering record behind FrogNet: the architecture, the implementation decisions, the experiments, and what happened when the conventional distributed-programming machinery was removed.
Read Magnum CroakusFrom §1 Scope and §2 Architectural invariants through discovery, routing, ponds, the broker, elections, Memory, UnREST, the wire, security, failure, performance, reference applications, conformance and known limits. It mirrors Magnum Croakus, and every page on this site links to the sections that define what it describes.
The rest of the site teaches FrogNet in a useful order. The inventory is the coverage specification: every architecture claim, extension point, demonstrated application class, measurement family and explicit boundary in one place.