Skip to content

docs: log Claim 4 (haskell multi-clause function counting) in beats-AST doc - #1617

Merged
squid-protocol merged 2 commits into
mainfrom
docs-haskell-claim4-multi-clause-recall
Aug 14, 2026
Merged

docs: log Claim 4 (haskell multi-clause function counting) in beats-AST doc#1617
squid-protocol merged 2 commits into
mainfrom
docs-haskell-claim4-multi-clause-recall

Conversation

@squid-protocol

@squid-protocol squid-protocol commented Aug 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Filing GitHub issues for haskell func_start recall (measured 50.5%) surfaced that the gap is almost entirely a tree_sitter_accuracy_audit.py ground-truth measurement artifact, not a real GitGalaxy defect — logged as Claim 4 in docs/why_gitgalaxy_beats_ast_here.md per CLAUDE.md's standing instruction for cases where GitGalaxy's structural signal beats tree-sitter's raw output.
  • Also removes an unrelated, pre-existing duplicate section ("How long can a gap like this actually last?" / "Why GitGalaxy doesn't hit this particular wall") that was accidentally repeated verbatim inside Claim 3 — noticed while editing this file, fixed as a drive-by since it's clearly wrong either way.

Detail

Re-walking the pinned 7-file language-crucible/data/haskell/pandoc corpus with a clause-collapse pass (merging consecutive same-name equation-clause siblings into one occurrence, the same semantics GitGalaxy's own _slice_by_indentation already applies per #1442) moves measured recall from 50.5% (275 real / 139 found) to 95.2% (146 real / 139 found), using the audit tool's own unchanged _align_occurrences_by_line/_get_param_count and unchanged GitGalaxy output.

Issues filed from this investigation, and their status:

Test plan

…ST doc

Investigating haskell func_start's measured 50.5% recall (issue filing pass)
found the gap is almost entirely a tree_sitter_accuracy_audit.py ground-truth
artifact: tree-sitter-haskell gives each pattern-match equation clause its own
node, while GitGalaxy correctly merges all clauses of one function into a
single reported entity (#1442). Clause-collapsed ground truth on the same
corpus measures 93.9% recall using the same alignment algorithm and unchanged
GitGalaxy output -- filed as #1614, with two smaller genuine residual gaps
as #1615/#1616. Also removes an unrelated pre-existing duplicate section
("How long can a gap...") accidentally repeated verbatim in Claim 3.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🐦‍⬛ Muninn Security Scan

✅ No security issues found.

🐦‍⬛ Powered by Muninn · Skald Lab

The initial writeup used a hand-rolled measurement script's approximate
148 real / 93.9% recall. The actual production fix (#1618) measures
146 real / 95.2% recall and leaves 7 residual misses, not 9 -- the
difference was the production fix's comment-sibling handling, which my
ad hoc script got wrong for two names (go, camelCaseStrToHyphenated)
that turned out not to be genuine misses. Updates the claim to cite the
real committed baseline and the actual issue/PR numbers now that #1614/
#1615/#1616/#1618 exist.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@squid-protocol
squid-protocol merged commit 4f376c0 into main Aug 14, 2026
4 checks passed
@squid-protocol
squid-protocol deleted the docs-haskell-claim4-multi-clause-recall branch August 14, 2026 20:09
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