Verify Proof
Use the local proof verification service as the canonical verifier before accepting a solution. Do not use this skill for partial proofs, isolated subgoals, or branches that have not yet produced a full proof draft of the whole problem.
Input Contract
Read:
- target theorem statement
- assembled proof blueprint candidate from
results/{problem_id}/blueprint.mdas pure markdown text - relevant prior failure reports and branch context
Procedure
- Read the current
results/{problem_id}/blueprint.mddraft as pure text. - First check that
blueprint.mdcontains a full proof draft of the entire target theorem rather than a partial proof, fragment, or exploratory notes. If it does not, do not call the verifier yet. - Call MCP tool
verify_proof_servicewith:statement: target informal statementproof: the raw markdown text fromblueprint.md
- Read
verification_report.summary,critical_errors,gaps,verdict, andrepair_hints. - Return and persist exactly what the verification service returns. Do not rename keys, add keys, or change the JSON structure.
- Treat the proof as failed if any of the following hold:
verdictis"wrong"verification_report.critical_errorsis non-emptyverification_report.gapsis non-empty
- Only treat the proof as passed when none of the failure conditions above hold.
- If the proof passes, rename
results/{problem_id}/blueprint.mdtoresults/{problem_id}/blueprint_verified.md.
Output Contract
Append to verification_reports:
{
"verification_report": {
"summary": "string",
"critical_errors": [
{"location": "", "issue": "detailed description of the issue"}
],
"gaps": [
{"location": "", "issue": "detailed description of the gap"}
]
},
"verdict": "string",
"repair_hints": "string"
}
Persist the verification service response exactly as returned.
If verification fails, revise blueprint.md directly and append to failed_paths when a branch is invalidated.
MCP Tools
verify_proof_servicememory_appendmemory_searchbranch_update- Codex built-in web search and
search_arxiv_theoremswhen the verifier identifies a missing lemma or gap
Failure Logging
Always persist verification output, including successful checks.