What we optimize for
Bounded scope. A useful request has a revision, toolchain, build command, failing declaration and acceptance criteria. We would rather narrow a request than sell certainty that cannot exist.
Reproducible evidence. A repair should survive a clean build and be understandable without the editor session that produced it. The handoff names changed files, assumptions and remaining boundaries.
Honest language. Lean checks formal terms. It does not automatically prove that a formal statement captures the author's intended mathematics. We keep that distinction visible.
Editorial policy
Guides are written as practical engineering notes, not invented case studies. Claims about Lean behavior are kept at the level a reader can reproduce locally. Product pages distinguish bounded effort from guaranteed outcomes, and we do not publish fictional ratings or testimonials.