Unverified50% confidenceFactExact time
FalkorDB's betweenness centrality algorithm follows edge direction, and in Khoj's initial model the edge direction was Person→Company, causing all betweenness centrality scores to return zero; this was fixed by adding a reverse HAS_DIRECTOR edge for each director relationship.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFalkorDB query results are objects keyed by the RETURN alias rather than positional arrays; indexing an object with [0] silently returns undefined without an error.61% similarUnverifiedA reranker can only reorder within the candidate set already recalled; it cannot pull back a correct answer that never entered the top K.55% similarUnverifiedWhen the action response lacks an after object, the controller must obtain a standard investigation from FalkorDB to avoid making the next decision based on stale evidence.53% similarUnverifiedThe benchmark scoring rules specify that any out-of-bounds violation or unparseable output results in a score of 0; otherwise, the score is the average of schema, defer, and faithful.53% similarUnverifiedAfter each analysis, BLACKBOX writes structured findings (root cause, affected services, solutions, owners, and postmortem knowledge) back to FalkorDB, forming a feedback loop.53% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062676API
curl https://kongchang.com/api/v1/knowledge/claims/1062676MCP
get_claim(id=1062676)