Skip to content

1.1.0: plain-language questions (ripgrep holdout 0.042 → 0.500), stdout fix, cold start - #127

Merged
ParsaVictor merged 7 commits into
mainfrom
concept/gold-and-fixes
Oct 1, 2026
Merged

ParsaVictor merged 7 commits into
mainfrom
concept/gold-and-fixes

Conversation

@ParsaVictor

Copy link
Copy Markdown
Owner

Plain-language questions (Yoosef's report). Draft: holdout (ripgrep, gold locked in 97f106b) and latency still to come. Findings F88–F91 in docs/planning/stage5-findings.fa.md.

🤖 Generated with Claude Code

@ParsaVictor ParsaVictor changed the title Concept questions: BM25F file ranker (recall 0.286 → 0.679) 1.1.0: plain-language questions (ripgrep holdout 0.042 → 0.500), stdout fix, cold start Oct 1, 2026
@ParsaVictor
ParsaVictor marked this pull request as ready for review October 1, 2026 08:35
ParsaVictor and others added 7 commits October 1, 2026 12:24
…re any run

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…guesses

Plain-language questions (no identifier) were resolved one word at a
time and landed on whatever symbol shared a word. New set
tests/third_party/concept (14 q on this repo): recall 0.286 -> 0.679.

- F89: "How does this tool ..." made `tool` a strong identifier anchor;
  a lowercase word the prompt never marks as code is retagged stem:
- F90: neuromesh-graph/src/file_rank.rs - BM25F over path, defined
  names, comments and body, Snowball-stemmed (rust-stemmers); new
  comment_index in the graph (snapshot v4); W3 seeds the best file and
  up to two runners-up within 70%, and drops guesses far below it
- F91: general software thesaurus (thesaurus.txt, weight 0.35), with no
  topic of the ripgrep holdout in it
- NM_RANK_PROBE=1 in the gold harness shows where the ranker puts gold

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ose halves drop with the compound; word! is code

- file_rank index keyed on (generation, file count): learning bumped the
  node revision every query and rebuilt the index (CI 250 ms gate)
- guess pruning scores against every file, tests included
- compound-stem pair drops stem: halves too (F89 retag)
- `trainstep!` marks code (Julia/Rust macros): holdout-lang back to 0.589

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t retagged (predict / predict_proba); clippy

holdout-ml back to 0.478.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…big files seeded by their matching definitions

Cold start, fresh clone of this repo: first query 3.56 s -> 2.65 s
(includes the index build), warm queries 0.1-0.4 s.

- spawn_live_sync marks the gate Indexing before the scan thread runs:
  the gate said Ready over an empty graph and the first question got
  "no_seed_resolved"
- wait_for_index answers from a complete index only (finished scan or
  loaded snapshot; reset on clear), waits up to 120 s
  (NEUROMESH_INDEX_WAIT_SECS), never from a graph still filling
- reindex_incremental marks Ready before the optional embeddings refresh
- rank index built after ingest and snapshot load, not on the first
  question (CI 250 ms gate)
- a ranked file over 8k tokens is seeded by up to three definitions whose
  name/doc match the question, not whole
- NM_TIMING=1: index stages, rank build, seeds/select, MCP stages
- benchmark-holdout.sh: `concept` and `concept-holdout` sets
- ripgrep holdout run once: recall 0.042 -> 0.500 (F92-F94 open)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…acket not smaller); changelog 1.1.0, reply to upstream, benchmark-fast.sh, roadmap H-M

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…enchmark-fast.sh fix

Nine sets in 78 s warm with benchmark-fast.sh (was ~40 min), same numbers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ParsaVictor
ParsaVictor force-pushed the concept/gold-and-fixes branch from 25ee1be to 4b3debe Compare October 1, 2026 08:55
@ParsaVictor
ParsaVictor merged commit 541490c into main Oct 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant