Repository navigation
Browse knowledge gaps in an embedding map with matched Mech definitions - #613
Merged
Merged
Conversation
This was referenced Nov 16, 2026
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.
Adds an embedding map to the knowledge-gap browser. Each indexed discussion combines its complete gap text with identifiers, names and native definitions/descriptions of the entries accepted by the existing term recognizer. Clicking a point opens the discussion, evidence, matched records and nearest discussions from the original embedding vectors.
The map uses the existing source, lifecycle, search and term/pair filters across all matching discussions, independently of result pagination. Coordinates and colors remain stable under filtering. It includes keyboard navigation, pan/zoom, a seventh magenta section link, and complete filtered JSON/CSV exports. Map loading failures preserve ordinary search and offer retry.
All 3,830 discussions and 3,380 matched native owner records are retained. 2,976 discussions include native descriptions; 240 use matched names only and 614 use gap text alone. The local, pinned BGE-large-en-v1.5 encoder chunks long inputs without truncation. Retained vectors, fixed PaCMAP coordinates, original-vector neighbors and diagnostics are versioned; CI validates and packages those artifacts without model downloads or inference. The map is an exploratory view of text similarity, with projection limitations explained in the interface.
The fixed PaCMAP graph excludes self by row identity even for duplicate vectors; all nearest, mid-near and far pairs are validated before fitting and checked unchanged afterward. Vector bytes and original cosine-neighbor lists are retained unchanged. The optional map download is 4.14 MiB gzip under a separate 5 MiB limit; its size is shown before loading.
Validation: 385 Python tests and 33 JavaScript tests pass in CI, including deterministic public-asset regeneration and production Jekyll build. Real-data browser checks cover desktop/mobile filtering, off-page point selection, matched definitions, history, keyboard/pointer access, stable marker size after zoom/resize, complete exports, empty states and isolated download recovery. Section-navigation/statistics checks cover 1280px, 620px and 390px, including no-JavaScript and failure/loading states.
Adversarial review and browser checks produced six findings, all fixed and independently re-reviewed: fresh canary execution, auxiliary model-file pins, numeric CSV coordinates, strict diagnostic serialization, duplicate-vector graph self exclusion, and mobile marker visibility. Method, refresh commands and retained evidence are under
_gaps/EMBEDDING_MAP.mdand_gaps/reviews/embedding-implementation-review.md.Closes #609. Fixes #610. Fixes #611. Fixes #612. Fixes #614. Fixes #615. Fixes #616.