Say what the graph is for: it writes, steers and checks the answer - #30
Merged
Conversation
The positioning undersold the point. "See the steps drawn as a graph" describes a picture; the graph here is load-bearing, and every load it bears has a measured number behind it, pinned in docs/claims/ and re-checked by CI. The README now leads with that: the strongest path writes the answer (54.9% to 91.2%), embeddings steer exploration away from drift and repetition (decisions a model cannot make about itself), an embedding gate decides whether a numeric answer is even on the table, arithmetic settles exactly through mpeqs (+32.5 points where arithmetic is the task, replicated), and every run accumulates into per-session tables and RDF. And the boundary is stated rather than implied: not a general knowledge-graph builder for documents or RAG -- the graph is built from the model's own reasoning and fed back into it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The positioning undersold the point — "see the steps drawn as a graph" describes a picture, but the graph is load-bearing. The README now leads with a table where every row is a pinned, CI-checked measurement:
And the boundary is stated: not a general knowledge-graph builder for documents/RAG — the graph is built from the model's own reasoning and fed back into it.
README stays short: 83 lines.