Deep Beilinson Audit

Run this skill when correctness matters more than speed and the task is to challenge a claim, not merely improve its presentation.

Load first

• CLAUDE.md
• chapters/connections/concordance.tex
• metadata/theorem_registry.md
• archive/raeeznotes/raeeznotes100/red_team_summary.md
• the target files
• the directly cited dependencies

For status-heavy work, also load the relevant metadata files.

Audit protocol

1. Fix the audit surface exactly: file, theorem label, formula, paragraph, compute module, or claim cluster
2. State the current claimed status: proved here, compute-backed, conditional, conjectural, heuristic, or open
3. Try to kill the claim: dependency attack hidden-hypothesis attack scope attack notation or object-conflation attack sign or grading attack reduced/completed or finite-stage/limit attack counterexample or edge-case attack
4. Recompute formulas from first principles whenever feasible. Do not verify by pattern matching against nearby text.