Skip to content

Latest commit

 

History

History
33 lines (23 loc) · 1.31 KB

File metadata and controls

33 lines (23 loc) · 1.31 KB

Support

How to get help

  1. Read README.md, docs/PROJECT_SPEC.md, and docs/SPEC_INDEX.md for normative intent and document map. Start at docs/README.md for navigation.
  2. Search existing GitHub issues and discussions before opening a new one.
  3. For usage questions and design clarification, open a GitHub Discussion or an issue using the question template.
  4. For defects, use the bug report template and include reproduction steps, Lean toolchain version, and whether replay or discovery mode is involved.

What maintainers support

  • Clarifying trust-model and claim-strength questions.
  • Reproducing and triaging defects in Core, IR, checkers, adapters, and CI.
  • Reviewing RFCs and architecture proposals that affect protocol semantics.

What maintainers do not provide

  • Private Mathematica license provisioning.
  • Custom formalization consulting for unrelated Lean projects.
  • Guarantees that an untrusted backend answer is correct without Lean replay.

Security and conduct

  • Security vulnerabilities: follow SECURITY.md. Do not open a public issue.
  • Community conduct: follow CODE_OF_CONDUCT.md. Contact conduct@mathevidence.org.

Response expectations

Volunteer maintainers triage issues as capacity allows. Critical soundness and security reports take priority over feature requests.