We should add a reference about BFS-based graph compression. The canonical citation seems to be this one:

• Alberto Apostolico, Guido Drovandi, *Graph compression by BFS*, Algorithms 2009, 2(3), 1031-1044. mdpi <https://www.mdpi.com/1999-4893/2/3/1031/pdf>_

I'm missing an introduction of sort here, linking together the references above to the sections below.

Ideally we want a dataflow picture here, showing a pipeline of the various phases and which files are produced as byproduct of each phase and which ones are used as input of the next one. Could be an ASCII art, a graphviz-based diagram, or a hand-created diagram (e.g., using draw.io) that is then referenced by the .rst doc.

use active voice here (and in general): "we can use" → "we use"

• "the graph" → "the resulting BV graph" (I think)
• "stored using multiple files" → "stored as a set of files"
• adding a brief (even very brief) description of what each one of this file contains would be useful

• "The ordering" → "The resulting ordering"

as many files have been involved during the process, we should list here which (and all) files form the final compressed representation of the graph

• style: use active voice here
• similarly about what we did above, we should probably give here a pointer to what class/tool is used to implement this step

This is great, but the other phases are inconsistently documented w.r.t. this one. Can we please have a pointer to the relevant class that implements the transformation in all phase descriptions?

Please generate (and clean) also SVG here.

I'm guessing for sphinx favors PNG, and allows to do its popup thingie on PNG images, but as the diagram is vectorial, it's nice to also have a non-lossy version of it available.

these should be rm -f, otherwise make clean as a whole can fail if the first file format that make tries to remove is not available on disk