All works → Software
Software
namaster-proof: Content-bound execution receipts as a shortcut detector for pseudo-Cℓ computations
Software that catches skipped or faked steps in a common CMB/LSS analysis — a general verification primitive, tested blind
Abstract
A narrow, installable Python verification layer for exact NaMaster bandpower-window inference, deterministic multipole-support contracts, and tamper-evident JSON result receipts. The paper makes software and reproducibility claims only; it does not claim a cosmological detection or a novel physical model.
Result summary
- derivedExact contraction of uniformly rotated EE/EB/BE/BB spectra through the complete NaMaster bandpower-window tensor
- openFixed-grid recovery and direct equivalence testing against the couple-cell/decouple-cell operator
- openAtomic JSON publication with coherent-snapshot SHA-256 receipts and fail-closed metadata validation
- openDeterministic field, bin, and harmonic-limit contracts whose final exclusive bin edge is ℓmax+1
Figures



Candidate figures — validated analysis outputs not yet included in the draft.



Readiness
0B / 0M / 0m / 0C open
Readiness is publication readiness only — science, evidence, review convergence, packaging, and Houston’s final sign-off. Venue and submission are tracked separately below, and never subtract from this number (directive P).
Publishing
Not part of readiness.
Review evidence (173 rounds)
Automated review is a gate on publication readiness, not a product. Full review timeline →
External peer review kit
Houston-driven manual round · paste prompt into any frontier LLM web UI with the PDF attachedOne click to copy a referee prompt scoped to this paper. One click to download the latest PDF. Paste both into Claude / GPT-5 / Gemini / Grok / Perplexity — return findings here and the autonomous cron will close them in the next bundled hard-fix wave.
preview prompt
You are an external referee for MNRAS / Physical Review D / JCAP (target journal depends on paper). Attached: Paper 1B v2B.0.23 — "namaster-proof: Content-bound execution receipts as a shortcut detector for pseudo-Cℓ computations" Source: arxiv/paper1b_namaster_proof.tex PDF: Software metapaper · 16 pp · v2B.0.23 · package 0.1.7 · 41 tests · updated Sep 5, 2026 · md5 60d1a18ab3ea499398106d6a92bc8a35 — all deferred text items from the v2B.0.20 R3 audit closed (batch-3 audit trail, rule-file digests, Table 1 trust category). ROUNDS STOPPED under R2; venue decision next. Read the FULL PDF end-to-end. Produce a referee report in MNRAS format with: 1. Recommendation: ACCEPT / MINOR REVISIONS / MAJOR REVISIONS / REJECT 2. BLOCKERS (must fix before publication) — list each with section/line + proposed fix 3. MAJORS (should fix) — same format 4. MINORS (polish) — same format 5. Strengths (>= 3 bullet points) 6. Specific scrutiny on: - Exact pseudo-Cℓ window inference - Tamper-evident workspace and artifact provenance - namaster-proof 0.1.7 regenerability and test evidence - Bounded final-hash confirmation, correspondence metadata, and Houston JORS sign-off CALIBRATION (do not burn findings on these known classes): - The current date is June 2026. arXiv identifiers of the form 25xx.xxxxx and 26xx.xxxxx are VALID, already-published preprints — do not flag them as "future-dated" or "nonexistent". Verify a citation against arXiv/ADS before claiming it does not exist. - Correction notes, retraction notices, and "an earlier version stated X" disclosures in the text are DELIBERATE transparency policy. Flag them only if their content is wrong, never for existing. - Companion-paper citations marked "posted concurrently on arXiv" are deliberate placeholders; real arXiv IDs are inserted during the coordinated submission sequence. - Explicitly labeled conservatism allowances, scaling estimates, ansatz/heuristic status labels, and disclosed queued follow-up computations are deliberate scoping, not oversights — flag only if the label itself is inaccurate. - PDF text extraction can mangle math (square roots, fractions, superscripts). Before flagging "garbled" or "wrong" math, consider extraction artifacts; flag only what is visibly wrong in the rendered PDF. VERDICT STANDARD (apply the SAME high bar a first-pass Physical Review D / MNRAS referee would — this is one of the most rigorous journals in the world): - Assign each finding's severity (BLOCKER / MAJOR / MINOR) by your own independent referee judgment. Do NOT default to any tier, and do NOT soften a finding because the rest of the paper is strong. Do not echo this prompt's context. - A reporting choice that headlines the more favorable of two numbers, an unstated assumption, an uncontrolled systematic, or an internal inconsistency IS a real finding — classify it honestly (MINOR at minimum), not as mere "style" or "opinion". - Truth-audit any claim that seems off by checking it against the published .tex / on-disk artifacts before flagging (this only filters out genuine extraction artifacts — it does not lower the bar on real defects).
Reproduce this
Lineage
Research Software · Exact-Window Verification. This work does not claim beyond its stated target and scope above.