Skip to content

Clarify published benchmark evidence coverage - #21

Closed
dajiaohuang wants to merge 1 commit into
Graphicle-AI:mainfrom
dajiaohuang:docs/benchmark-evidence-coverage-20261108
Closed

dajiaohuang wants to merge 1 commit into
Graphicle-AI:mainfrom
dajiaohuang:docs/benchmark-evidence-coverage-20261108

Conversation

@dajiaohuang

Copy link
Copy Markdown
Contributor

Summary

  • Scope the evidence index to artifacts that are actually published in docs/evidence/.
  • Clarify that the 2026-11-01 Graphicle 0.1.11 vs Graphify 0.9.100 figures are summarized in docs/benchmarks.md, but the evidence directory has no matching registered protocol or raw results.

Validation

  • git diff --check passed.
  • Documentation-only change; no tests run.

Signed-off-by: dajiaohuang <mikewushuwen@outlook.com>
VikramLex added a commit that referenced this pull request Nov 8, 2026
…phify 0.9.100

Add docs/evidence/graphify-comparison-2026-11-01/: the registered protocol and its notes (private identifiers removed, as listed in docs/evidence/README.md, with the registered and published SHA-256), the registered commit ranges and Graphify's package constraints as recorded. Link it from the section of benchmarks.md that reports the results. Wu Shuwen pointed out the missing record in #21.

Signed-off-by: VikramLex <vikramlex@karlexai.com>
@VikramLex

Copy link
Copy Markdown
Member

Thank you, Wu. You are right that docs/evidence/ had no record for the 1 November comparison of Graphicle 0.1.11 with Graphify 0.9.100. Rather than note the gap, we published the record: docs/evidence/graphify-comparison-2026-11-01/ now holds the protocol as registered before the first measured run, the notes added after registration, the registered commit ranges and Graphify's package constraints, and docs/evidence/README.md lists what was changed for publication with the SHA-256 of each file as registered and as published. The results section of benchmarks.md links to it. The commit credits this PR. Closing this one as resolved by that change.

@VikramLex VikramLex closed this Nov 9, 2026
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