odinfree/storm-ecdsa-harness / skills/lean-arklib-proofs
lean-arklib-proofs
VerifiedFormalize and verify mathematical or cryptographic claims in Lean 4 with ArkLib: exact-target builds, axiom audits, dependency checks, and the build evidence an evaluator expects.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| agents/openai.yaml | config | 274 B |
| references/acceptance-gates.md | markdown | 1.4 KB |
references/acceptance-gates.md
View on GitHub# Lean and ArkLib acceptance gates
Apply the gates required by the target project and record each command and result.
## Source gate
- Search the relevant source and generated artifacts for `sorry`, `admit`, placeholders, and unauthorized axioms.
- Check imports and namespaces so the theorem uses the intended ArkLib definitions.
- Inspect theorem assumptions and compare them with the original claim.
## Build gate
- Build the exact declared target from the authoritative worktree.
- Record Lean version, package lock, ArkLib commit, repository commit, and build command.
- Remove or bypass caches only when the project procedure requires it; never destroy unrelated user work.
## Trust gate
- Run `#print axioms` or the project's stronger dependency audit on every exported load-bearing theorem.
- Treat classical axioms or approved project axioms according to the repository policy; list them instead of silently assuming acceptance.
- Run any repository-specific checker that validates imports, declarations, or forbidden constructs.
## External gate
- Run the official evaluator or packaging checker when the target requires one.
- Preserve its exact output and identify the source commit it evaluated.
- Recheck any live threshold or acceptance rule immediately before promotion or submission.
The final receipt should separate statement review, successful compilation, trust audit, repository checker, and external evaluator. None substitutes for the others.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |