Explanation

Background and design: why the library is shaped the way it is. These pages explain; the API reference gives the exact contracts.

• The update model
• Backends and resources
• Results and versions
• Hypergraphs and hyperedge ids

Planned: containers in depth (graph row layouts, the ESCHER store’s trees), batches and their semantics in depth (today: ADR 0010), determinism levels, errors, ids and sentinels, frontiers and operators (with the Gunrock / cuGraph / GraphBLAS name map), tiers and fused engines.