Repository navigation
Add Chinese Engram storage article and evidence figures - #12
Merged
Merged
Conversation
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
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.
Engram readers currently have many technical reports but no complete Chinese article, and the launch copy still describes XOR as offline-only. Add a Zhihu-ready article with two figures redrawn from the existing trained evidence, a runnable C/PyTorch factory example, direct tail-error disclosures, and accurate upstream status. Link the article from README and the share kit, and refresh the short launch copy.
Validation: plotted values and input/output hashes checked against aggregate JSON; local article links and git diff whitespace checks pass; both figures visually inspected. The documented factory command was rerun on macOS: all nine dtype/backend cases avoid default table allocation and preserve full output bytes. No new training or compression benchmark is claimed.