I would find it very helpful to have some reference for Crosslink.
Some ideas:
"Base Chains Diagram":
Show bc and bft chains with a few bc forks, which also shows the two edge types (from bc to bft and vice versa), and which shows a "round trip" from bc->bft->bc straddling a bc-fork.
$\mathsf{LOG}_{\mathsf{da}}$ construction diagrams
A subset of "Base Chains Diagram" explicitly focused on the content used to derive $\mathsf{LOG}_{\mathsf{fin}}$ from a single bc-block. (Thus is has one edge in each direction.)
The preceding diagram plus a visual indicator of sanitizing that input to compute the literal $\mathsf{LOG}_{\mathsf{fin}}$
The preceding diagram, plus a visual indicator of appending the appropriate blocks / 0-conf txns to compute $\mathsf{LOG}_{\mathsf{da}}$-
Sanitization Diagrams
A variation of "Base Chains Diagram" that zooms into granularity to show txns within the bc chain, then show two pairs of a transaction and its dependent, where one pair is sanitized out.
If the case chosen can implicitly cover some "surprising" or unexpected behaviors of sanitization that might be helpful unless it obscures the happy-path case. If so, then we should have two diagrams for two different cases of sanitization.
Suggested Improvement
I would find it very helpful to have some reference for Crosslink.
Some ideas:
"Base Chains Diagram":
Show bc and bft chains with a few bc forks, which also shows the two edge types (from bc to bft and vice versa), and which shows a "round trip" from bc->bft->bc straddling a bc-fork.
$\mathsf{LOG}_{\mathsf{da}}$ construction diagrams
Sanitization Diagrams
A variation of "Base Chains Diagram" that zooms into granularity to show txns within the bc chain, then show two pairs of a transaction and its dependent, where one pair is sanitized out.
If the case chosen can implicitly cover some "surprising" or unexpected behaviors of sanitization that might be helpful unless it obscures the happy-path case. If so, then we should have two diagrams for two different cases of sanitization.