Skip to content

docs(claude): scoring hygiene and the probe/ALFA split - #69

Open
opariffazman wants to merge 1 commit into
mainfrom
docs/scoring-hygiene
Open

docs(claude): scoring hygiene and the probe/ALFA split#69
opariffazman wants to merge 1 commit into
mainfrom
docs/scoring-hygiene

Conversation

@opariffazman

Copy link
Copy Markdown
Contributor

Writes the PR #68 findings into CLAUDE.md as rules, with the references behind them.

Corrects the noise-floor bullet. Issue #57's ≤0.013 floor is the scorer, not the training — ~1% of tasks give a different verdict for a byte-identical command. The causes are all task-side: find -mtime/-mmin/-atime against build-time file stamps, unsorted find -print, ps aux, dig, and the mtime gzip and tar write into their own headers. InterCode-ALFA's README documents none of it.

Adds a "Scoring hygiene" section. Scorer and container stay unmodified; everything listed controls the measurement around it — the same split lm-evaluation-harness draws with --use_cache:

  • verdict cache on (index, command) — 61% of our scoring calls repeat a command already scored for that task
  • one session, one image build per comparison
  • majority-of-3 on the known-flaky ~1%, the standard fix in the execution-benchmark literature
  • state the mxbai-embed-large digest next to the llama build
  • don't reach for libfaketime — changes the environment, ~10× slower, buys nothing one session doesn't

Adds "The probe and ALFA do not measure the same thing." Only 17% of ALFA-BM tasks the shipped model passes use a beginner tool; find alone is a third. Runs 10–13 traded ALFA for probe one inside-CI step at a time. Names the trade so the next run makes it deliberately.

References: lm-eval interface, arXiv 2405.14782, arXiv 2505.23419, arXiv 2310.15642, reproducible-builds.org, libfaketime.

Docs only — no code, no dataset, no model. The cache itself isn't implemented yet.

🤖 Generated with Claude Code

The issue #57 noise floor is the ALFA scorer, not the training: ~1% of tasks
return a different verdict for a byte-identical command because the task is
not deterministic (find -mtime against build-time stamps, unsorted find,
ps aux, dig, gzip/tar header mtimes). Records what to do about it without
touching the scorer or the container: verdict cache on (index, command),
one image build per comparison, majority-of-3 on the known-flaky set, and
the embed model digest alongside the llama build.

Also records that the probe and ALFA measure different tools, which is the
trade runs 10-13 made without naming it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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