···

       
63
       
 
       


     

       
64
       
 
       
If in doubt, add more whitespace lines than needed - you can always clean this up later with `dune build @fmt` to get ocamlformat to sort out the whitespace properly.

     

       
65
       
 
       


     

       
0
       
 
       

     

       
0
       
 
       

     

       
66
       
 
       
# Module Structure Guidelines

     

       
67
       
 
       


     

       
68
       
 
       
IMPORTANT: For all modules, use a nested module structure with a canonical `type t` inside each submodule. This approach ensures consistent type naming and logical grouping of related functionality.

     

···

       
63
       
 
       


     

       
64
       
 
       
If in doubt, add more whitespace lines than needed - you can always clean this up later with `dune build @fmt` to get ocamlformat to sort out the whitespace properly.

     

       
65
       
 
       


     

       
66
       
+
       
When adding ocamldoc comments, use the information in the protocol specifications available to also add relevant explanations to the OCamldoc. Do not refer to the specification in the third-person, but directly include enough information in the OCamldoc for a reader to understand the protocol flow directly.

     

       
67
       
+
       


     

       
68
       
 
       
# Module Structure Guidelines

     

       
69
       
 
       


     

       
70
       
 
       
IMPORTANT: For all modules, use a nested module structure with a canonical `type t` inside each submodule. This approach ensures consistent type naming and logical grouping of related functionality.