wanshuiyin/Auto-claude-code-research-in-sleep / skills/skills-codex/proof-orchestrator
proof-orchestrator
VerifiedManage a stateful, run-directory-based proof project with Codex: continuation across runs, run-local source bookkeeping, manual GPT Pro handoff packages when a local attempt stalls, and an optional DeepSeek second opinion as additional evidence only. Use when the user asks for proof-run orchestration, a GPT Pro handoff, or cross-run proof continuation — use /proof-writer for ordinary proof drafting and /proof-checker for rigorous verification or submission acceptance.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.7 KB |
| references/audit-output-contract.md | markdown | 4.4 KB |
| references/deepseek-routing.md | markdown | 3.5 KB |
| references/dispatch-prompts.md | markdown | 7.6 KB |
| references/notation-audit.md | markdown | 5.2 KB |
| references/proof-audit-rubric.md | markdown | 4.3 KB |
| references/stress-tests.md | markdown | 1.8 KB |
references/audit-output-contract.md
View on GitHub# Proof Audit Output Contract
Use this format for saved audits. Keep chat-only audits shorter but preserve
the same verdict and issue semantics.
## Markdown Audit
```md
# Proof Audit
Target: <file/section/task>
Verdict: PASS | WARN | FAIL | BLOCKED | NOT_APPLICABLE
Claim status: PROVABLE AS STATED | PROVABLE AFTER WEAKENING / EXTRA ASSUMPTION | NOT CURRENTLY JUSTIFIED
Reviewer backend: llm-chat-deepseek | local-executor-fallback | local-codex-fallback
Reviewer model: <model name or unknown>
## Claim Restatement
<explicit statement with assumptions, quantifiers, domains, and conclusion>
## Obligation Ledger
| ID | Obligation | Location | Status | Notes |
|----|------------|----------|--------|-------|
## Issues
| ID | Severity | Category | Location | Summary | Minimal repair |
|----|----------|----------|----------|---------|----------------|
## Counterexample Pass
<attempts, successful counterexamples, or candidates>
## Recommended Repair
<minimal honest fix: add derivation, add assumption, weaken claim, add reference, or split lemma>
## Remaining Risks
<what was not checked or still depends on external material>
```
## Issue Record
For each serious issue, include:
```md
### I<n>: <short title>
- Severity: FATAL | CRITICAL | MAJOR | MINOR
- Category: <taxonomy label>
- Status: INVALID | UNJUSTIFIED | UNDERSTATED | OVERSTATED | UNCLEAR
- Impact: GLOBAL | LOCAL | COSMETIC
- Location: <file:line or section>
- Claimed step: <what the proof asserts>
- Problem: <why it does not follow>
- Counterexample: YES | NO | CANDIDATE, with details
- Downstream effect: <what breaks>
- Minimal repair: <add derivation / add assumption / weaken claim / cite result and verify conditions>
```
## Optional JSON Artifact
Write the machine-readable audit to the RUN DIRECTORY as
`prompts/<run-id>/PROOF_ORCHESTRATOR_AUDIT.json`, and only when a caller or
formal workflow requests one. Never write `<paper-dir>/PROOF_AUDIT.json` —
that path is `/proof-checker`'s canonical submission artifact, and this skill
must not create, overwrite, or shadow it. A proof-orchestrator audit is
additional evidence for the run, not a submission verdict.
Use paths relative to the run directory for files inside it. Use absolute
paths for files outside it.
```json
{
"audit_skill": "proof-orchestrator",
"audit_mode": "deepseek-second-opinion",
"verdict": "PASS | WARN | FAIL | NOT_APPLICABLE | BLOCKED | ERROR",
"reason_code": "all_proofs_complete | minor_gaps | critical_gap | no_theorems | source_unreadable | reviewer_error",
"summary": "One-line verdict summary.",
"audited_input_hashes": {
"main.tex": "sha256:..."
},
"generated_at": "<UTC ISO-8601>",
"reviewer_backend": "llm-chat-deepseek | local-executor-fallback | local-codex-fallback",
"reviewer_model": "deepseek-v4-pro | deepseek-chat | deepseek-reasoner | unknown",
"review_independence": "cross-family | same-family | none",
"acceptance_status": "provisional-evidence-only",
"executor_family": "<claude | gpt | other>",
"reviewer_family": "<deepseek | gpt | claude | unknown>",
"raw_reviewer_verdict": "<the reviewer's own verdict before any executor validation, or null>",
"details": {
"theorems_audited": 0,
"issues": [
{
"id": "I1",
"severity": "FATAL|CRITICAL|MAJOR|MINOR",
"category": "QUANTIFIER_ERROR",
"location": "sections/theory.tex:L182",
"note": "..."
}
]
}
}
```
## Verdict Mapping
- `NOT_APPLICABLE`: no theorem, lemma, proposition, corollary, or proof content.
- `BLOCKED`: required source is unreadable or missing.
- `PASS`: all proof obligations discharged.
- `WARN`: only minor issues, or major issues with explicit justification that the main conclusion survives.
- `FAIL`: any fatal or critical issue, or a major issue that may affect the main conclusion.
- `ERROR`: audit machinery failed.
## Independence Labeling
`review_independence` is derived, never asserted: `cross-family` only when the
verified reviewer model family differs from the executor's family (see
`deepseek-routing.md` for the verification requirement); `same-family` when
they match; `none` for `local-executor-fallback` / `local-codex-fallback`.
A `PASS` from a `same-family` or `none` review is provisional evidence for the
run and can never satisfy a cross-family acceptance gate — `acceptance_status`
stays `provisional-evidence-only` in every case; formal acceptance belongs to
`/proof-checker` and the paper workflows.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |