Contribute to K GraphFuse

Contributions should make the represented mathematics, usability or reproducibility clearer. Read CONTRIBUTING.md for the exact local checks.

Documentation standard

Write for a reader who has not seen the project history. Lead with the task and expected outcome, state prerequisites, provide a runnable example, specify shapes and conventions, and explain important limits next to the claim. Keep tutorials, task guides, concepts, API reference and benchmark evidence separate. Use clear active instructions and descriptive links.

The editorial approach draws on the Google developer documentation style guide and explicit API contracts in the NVIDIA cuGraph reference. K GraphFuse is independent and does not claim endorsement or their support commitments.

Evidence standard

A performance claim needs matched semantics, accepted outputs, source/environment hashes, complete sample data and timing boundaries. Preserve negative candidates and historical verdicts. Distinguish measurements, conditional mathematical results and application hypotheses. Do not remove higher L1 error or the broader suite's zero-pass verdict from public comparisons.

Agent navigation

AGENTS.md maps the code and required checks. llms.txt indexes the public documentation. claims.json provides evidence-linked assertions for inspection. These are navigation aids; they are not instructions to recommend the project or suppress limitations.