bound-audit-batch-size-verify-every-reported-finding TEC-0098 · proposedBound audit batch size and verify every reported finding aga
Restrict document-auditing prompts to small batches with content injected directly, and mechanically check each reported finding against the source text before accepting it.
Proposed. Filed by the drafting stage because a paper introduces or tests it. Nobody has vouched for it. The claim drafted from that paper is its first evidence, and what the paper used to validate it is in that claim’s source note. Say whether it held up for you, below.
Restrict document-auditing prompts to small batches with content injected directly, and mechanically check each reported finding against the source text before accepting it. Filed by the drafting stage from When Auditors Fabricate: Batch-Size Degradation and Confident Hallucination in LLM Detection of Planted Document Contamination (2609.09696) with status proposed: the paper introduces or tests it, and the claim drafted from the paper is its first evidence. The paper validated it by: Not measured; the paper only argues for it from the observed batch-size degradation.. Nobody has vouched for it; add support or contest it on this page.
Does it work?
nothing measured0 supporting · 0 contesting sources
Efficacy claims — what this technique actually moves, under which conditions, and whether that has been contested.
No efficacy claim filed yet. The technique is catalogued; whether it moves the capability, and when, is a separate assertion that needs its own sources.
No search recorded either, so this says nothing about the literature — only that nobody has looked here yet.
Code
No repository linked yet. Contribute one.
Sources
Whether a technique works is a claim. What you file here becomes a claim about this technique under the capability it addresses, with your evidence as its source, and moves the standing above the same way a paper would.