Skip to content

docs: record leaderboard publishing pitfalls in CLAUDE.md - #43

Open
haolin-chen-actava wants to merge 1 commit into
mainfrom
claude/leaderboard-update-status-e965bd
Open

haolin-chen-actava wants to merge 1 commit into
mainfrom
claude/leaderboard-update-status-e965bd

Conversation

@haolin-chen-actava

Copy link
Copy Markdown
Contributor

Three notes from auditing why merged results were not appearing on the public leaderboard.

  • The site's leaderboard is not generated from actava-ai/leaderboard — it is a hand-maintained array in actava-official-website/lib/benchmarks-data.ts. Merging a submission PR publishes nothing on its own, which is how both merged-but-unlisted entries and packet-vs-site number drift happened. Includes the commands to audit it.
  • Publishing is four independent manual steps (run → leaderboard PR → website PR → infographic) that drift apart. Generated post assets under ~/.codex/visualizations/ are where broadcast-but-unsubmitted results surface first.
  • Never cite a chi_bench_git_sha unreachable from main, with the concrete 4f39c1e case that motivated it (now resolved by Land frontier model evaluations (GPT-5.6 family, Kimi K3, Inkling, Nemotron 3 Ultra) #42).

🤖 Generated with Claude Code

Three notes from auditing why merged results were not appearing publicly:

- The site's leaderboard is a hand-maintained array in
  actava-official-website/lib/benchmarks-data.ts, not generated from the
  leaderboard repo, so merging a submission PR publishes nothing.
- Publishing is four independent manual steps (run -> leaderboard PR ->
  website PR -> infographic) that drift apart; generated post assets under
  ~/.codex/visualizations are where broadcast-but-unsubmitted results
  surface first.
- Never cite a chi_bench_git_sha that is unreachable from main, with the
  concrete 4f39c1e case that motivated it.

Co-Authored-By: Claude Opus 5 <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.

2 participants