Claims

A git-history audit found 96.3% of AI-generated answer-key question blocks needed no post-release semantic repair

Claim · All claims
Evidence · 1 study · design r2 · q2
Currency · newest study 2026 · not yet checked against its sources · not reviewed by a person · recheck by 2029: tool and model accuracy changes quickly

Subclaims

Reading the evidence codes

q is the design tier, i the impact, n the sample, and the kind with its r the rigour judged within that kind: what each code means.

This claim: no standardized effect is recorded in observations/ for it yet, so no benchmark reading is possible.

q2 i? Of 273 distinct answer-key question blocks, 263 (96.3%) had no post-release repair across subsequent commits. → Jin-Guo Liu 2026

Evidence

Jin-Guo Liu 2026

Jin-Guo Liu, Shang-Qi Lu, Xin-Ran Shi, Long-Li Zheng, Wei Wang. (2026). Test-Driven, AI-Assisted Learning: Replacing Lectures with Weekly Closed-Book Tests. https://arxiv.org/abs/2606.23315 doi:10.48550/arxiv.2606.23315

q2 · i? · design · r2

Descriptive git-history audit of the repository's test and validation files, counting "273 distinct answer-key question blocks" and 10 semantic repairs. The authors call it operational evidence, not a controlled benchmark; no effect size printed.

"Subsequent commits contained 10 semantic repairs (proof logic, missing conditions, theorem references, or analysis), leaving 263 of 273 blocks (96.3%) with no post-release repair."

Discussion

Page metadata
Field Value
type claim
id ai-answer-keys-mostly-correct-git-audit
title A git-history audit found 96.3% of AI-generated answer-key question blocks needed no post-release semantic repair
description A git-history audit found 96.3% of AI-generated answer-key question blocks needed no post-release semantic repair
status review
evidence_strength weak
newest_evidence 2026
recheck_by 2029
generated by process:wiki-ingest on 2026-10-11
trust unverified — no one has confirmed this page's content
sources 1 — jin-guo-liu-2026

Frontmatter is the page's machine-readable record — see the Schema & Guide.