Lean 4 Package Evaluation, Pin Upgrades & Substrate Vendoring
Evaluate external Lean 4 packages on Reservoir/GitHub, plan compatible lean-toolchain + lake-manifest.json
upgrades, and execute license-verified, axiom-audited substrate vendoring when Lake require is unsuitable.
Routing
- USE FOR: package discovery (
lean_search(source: "reservoir")), Lake dependency vs. vendoring trade-offs, license/SPDX verification (Apache-2.0/MIT), and provenance-tracked vendoring. - DO NOT USE FOR: general theorem search (
@lean-research) or interactive tactic repair after bumping (@lean-proof-repair).
Workflow
- Evaluate Candidates -- Query Reservoir/GitHub for toolchain pin alignment,
sorry/axiom cleanliness, maintenance velocity, and transitive dependency weight. - Choose Integration Mode -- Prefer pinned Lake
requirewhen toolchains align; choose isolatedVendor/subtree vendoring only when extracting a narrowsorry-free slice across incompatible pins. - Verify License & Provenance -- Confirm permissive SPDX license (
Apache-2.0/MIT), preserve upstreamLICENSE+ copyright headers, and record exact upstream repo URL + commit SHA. - Compile & Axiom-Lock -- Build via
@lean-build, repair API drift via@lean-proof-repair, and run@lean-verification-gate(lean_axiom_closure) over every imported/vendored declaration.
Recovery & STOP
- Reject any upstream package with incompatible copyleft/missing license or custom
axiom/unsafedeclarations in the target slice. - Never hand-edit
lake-manifest.jsonhashes; always resolve pins throughlake update <pkg>.
Handoffs
- Predecessors:
lean-research,lean-setup. - Successors:
lean-build,lean-proof-repair,lean-verification-gate.
Detailed reference
- Layer-1 Fast Lookup Card (read first):
references/cards/lean-dependency-management-tables.md - Full handbook:
../../references/handbooks/lean-dependency-management-handbook.md
See also
../lean-setup/SKILL.md-- Toolchain & Lake project setup../lean-proof-repair/SKILL.md-- Repairing proofs across toolchain/Mathlib bumps
