This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
Fix stale references after the 2026-10 retirement - #449
Merged
Merged
Conversation
The project page no longer carries tables, so the docs point to the DBBench page; the dense id index has no environment switch; sentences that named the 2026-10 instrument as current or kept September rows now say what holds. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #448
After DECISIONS #196 retired the 2026-10 and September instruments (#429, #431, #432, #434), a sweep of README.md, bindings/python/docs, benchmarks/README.md, benchmarks/experiments/.md and the comments in benchmarks/experiments/.py for the removed names (make_2610_stages, make_october_stages, pass2_roster, runs_paper_oct, web_benchmarks_next, web_benchmarks_skeleton, generated_oct, LeanSession2/lean2, BENCH_ARCADEDB_EMBEDDED_XMS, BENCH_LARGE_RESULT_PATH, next_instrument_default, -Xmx4g as a default) found no live reference left; the earlier PRs had removed them. What was left were statements that no longer hold, fixed here.
The docs index, benchmarks/README.md, the vector search, server mode and cross-model examples and the overrides note in benchmarks/protocol.md sent readers to the ArcadeDB project page for benchmark tables, and two of them quoted outcomes of the retired rows. They now point to the DBBench page and say the first 2026-11 results are due in November 2026.
The override registry and a page_check description said the dense id index is off unless BENCH_DENSE_ID_INDEX=1; every dense adapter builds it unconditionally (test_instrument_method.py holds that), so the comment, the registered setting text and the description say so.
Sentences in CAMPAIGN.md, FAIRNESS.md, PROTOCOL.md and l1_tpc.py named the 2026-10 instrument as the current one, or said September's rows stay as measured; they now describe the published instrument and the retired rows. Left alone on purpose: runs_paper.csv (the live freeze name), cap_rule_2610.json (read by make_2611_stages.py), PUBLISH_INSTRUMENT, historical rows of the CAMPAIGN section 7 log, and the PRODUCT quantization text that #446 replaces.
Checks run locally:
mkdocs build --strictfor bindings/python (clean), the benchmark suite (922 passed, 25 skipped, 0 failed, unchanged),pre-commit run --fileson the 12 changed files.🤖 Generated with Claude Code