Module explain_digest 

Why are these two related — as lines.

One renderer, because there are two callers: the explain_association MCP tool and mushroomdb why. The CLI had no door to GraphDb::explain at all until 0.7, and the code-graph why it borrowed the name from answered a different question out of a code graph.

Structs

ExplainedEdge

One explained edge, with the values that made the predicate true.

Enums

Evidence

What the two nodes actually had in common, per predicate kind.

Constants

MAX_EVIDENCE_CHARS

Characters of evidence one digest line carries before it is cut with ….

Functions

explain_with_evidence

Every rule-derived edge between a and b, each with the values that made its predicate true.

predicate_summary

A predicate in one clause: what it compares, on which fields, and the threshold it had to clear.

render_explain

One header, then one line per rule-derived edge, capped like every other task digest.