Skip to content

Latest commit

 

History

History
50 lines (38 loc) · 2.17 KB

File metadata and controls

50 lines (38 loc) · 2.17 KB

Source gating

Selection order

  1. Prefer resolved work from 2024 onward.
  2. Expand through 2020 after checking the newer inventory.
  3. Use 2016–2019 only as a documented fallback.
  4. Prefer a proof-critical exact artifact over an interesting headline.

Required source record

  • title, authors, identifier, version, and first-publication date;
  • exact prior conjecture or open question;
  • theorem, proposition, example, or construction that resolves it;
  • solved, disproved, conditional, partial-case, or disputed status;
  • finite obligations and imported mathematical boundaries;
  • relevant installed producer and verifier candidates;
  • source, artifact, family, implementation, capability, provider, diagnostic, and root-cause overlap;
  • source decision and reason.

Accept only when

  • a primary source establishes the resolution status;
  • the bounded task is genuinely used in the result;
  • the prompt can be self-contained without revealing the conclusion;
  • success is externally scoreable without hidden reasoning;
  • the artifact fits current contracts or deliberately tests a documented boundary;
  • an independent clean-room oracle is feasible.

Reject or defer when

  • a headline exaggerates the theorem status;
  • the source only asks a question or presents a new classification;
  • the artifact is illustrative rather than proof-critical;
  • a rational substitution changes an algebraic or finite-field theorem;
  • checking a nearby determinant, rank, flat lattice, or specialization does not certify the published obligation;
  • the task requires private data or inaccessible certificates;
  • the same conjecture or artifact was already evaluated;
  • only one family supports a speculative new capability.

Record rejections immediately. Do not run model arms to confirm a known mismatch.

Independence labels

  • Independent oracle: separately implemented or derived exact evidence.
  • Source-supplied replay: rerun of author code, manifests, or certificates.
  • Imported metadata: a hash, count, theorem, or status not reproduced from retained bytes.

Do not merge these labels. Retain archive bytes when citing an archive-level digest; otherwise mark the digest as imported metadata.