Skip to content

docs: public-proof challenge packs and CoT refusal - #81

Merged
jkbennitt merged 1 commit into
masterfrom
cursor/public-proof-challenge-packs-0db5
Oct 7, 2026
Merged

jkbennitt merged 1 commit into
masterfrom
cursor/public-proof-challenge-packs-0db5

Conversation

@jkbennitt

Copy link
Copy Markdown
Member

Summary

Adds Comparator-style public-proof packing rules for RLE. A proof is a challenge file, an expected judgment name, and a pass/fail result over a printed receipt (summary.json, events JSONL, or a preflight-adapter JSON). Chain-of-thought, abridged reasoning_traces, and narrative math dumps are not receipts.

  • New spec: docs/public-proof-challenge-packs.md (pack fields, judgment-name catalog, predicate operators, N caveat).
  • Short pointers from the live-board note in README.md and from docs/bench-design-n-ticks.md.

Unchanged

Runtime, scoring, scenarios, and published board numbers are unchanged. The live cite remains spread-2026-09-07 (Crashlanded, 10 ticks, seed 42, N=1, scoring 1.2). This PR does not add a matrix, a pass rate, or a new board row.

Test plan

  • Read docs/public-proof-challenge-packs.md and confirm the pack shape (scenario, seed, tick budget, fixture or harness×model, scoring 1.2), the six judgment names, and the CoT refusal.
  • Confirm the README and bench-design pointers do not edit the published score tables.
Open in Web Open in Cursor 

Comparator-style packing for replayable RLE proof: a challenge file,
an expected judgment name, and pass/fail over printed receipts.
Chain-of-thought and abridged reasoning traces are not receipts.
Published scores and runtime are unchanged.

Co-authored-by: Jason <jkbennitt@users.noreply.github.com>
@jkbennitt
jkbennitt merged commit c444f4d into master Oct 7, 2026
5 checks passed
@jkbennitt
jkbennitt deleted the cursor/public-proof-challenge-packs-0db5 branch October 7, 2026 00:46
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