docs(eval): compare Understand-Anything vs aspid-wiki#116
Draft
VPDPersonal wants to merge 1 commit into
Draft
Conversation
Run the Understand-Anything plugin full-repo on Aspid.MVVM and compare it against the curated aspid-wiki knowledge base to decide which to use. - docs/understand-anything-evaluation.md — comparison + recommendation (RU): keep aspid-wiki as canon; UA only as an optional onboarding/visual map. - .understand-anything/knowledge-graph.json — UA output (3904 nodes, 3937 edges, 10 layers, 12 tour steps; 1951 files) for reproducing the dashboard. Key findings: tree-sitter is blind to source-generated members (the public binding/command API is absent from the graph); the C# import resolver yields 0 edges (no deterministic backbone); ~45% of nodes are vendored third-party code (Zenject, Asset Store Tools, TextMesh Pro). fingerprints.json and intermediate artifacts are git-ignored (regenerable).
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.
Summary
/understand --full) on Aspid.MVVM and compared it head-to-head with the curatedaspid-wikiknowledge base (PR docs: add aspid-wiki knowledge wiki (EN + RU vaults + skill) #115) to decide which to use.docs/understand-anything-evaluation.md— the comparison + recommendation (RU)..understand-anything/knowledge-graph.json(3904 nodes, 3937 edges, 10 layers, 12 tour steps; 1951 files analyzed) so the interactive dashboard is reproducible without re-running the analysis.Verdict: keep
aspid-wikias the canon; use UA only as an optional onboarding/visual map. Three decisive limits on this codebase:OutText,InputText,SetOutText,*Changedevents,SayCommand, theIViewModelimpl) is absent from the graph. That API is the point of the framework.Source/is only 68 files).UA shines at the interactive dashboard, auto-layered overview, and a 12-step guided tour — good for a one-off visual onboarding map, not as a source of truth.
Notes for review
knowledge-graph.jsonis ~3.4 MB of machine-generated JSON (not human-reviewable line by line); it lives under.understand-anything/at repo root, outside the shipped Unity package. If you'd rather not carry it in history, say so and I'll drop it and keep only the eval doc.fingerprints.jsonand intermediate artifacts are git-ignored via.understand-anything/.gitignore(regenerable, auto-update only).merge-batch-graphs.pyon a 3.9 system; pnpm native-build gate) were applied to the local plugin cache only — they are not part of this repo. Documented in the eval.