A new open-source project landed this week that changes what counts as useful output in AI-assisted math.
It’s called LemmaTrail. The idea is simple: hard math problems generate a lot of structured thinking that currently disappears. When you or a model spends two hours working through a combinatorics problem or a number theory proof, you hit walls, backtrack, try substitutions that almost work, notice connections to papers you half-remember, and eventually stall out somewhere interesting. Raw AI transcripts get posted, partial solves get claimed, and the actual reasoning, the failed routes, the flagged gaps, the source connections, none of it lands anywhere usable for the next person working the same problem. The field produces a massive amount of intellectual effort and captures almost none of the process. LemmaTrail is a direct fix for that.
Here is the twist. LemmaTrail does not ask you to solve anything. A properly documented failed route is a first-class contribution. So is a gap review, a candidate claim with a clear breakdown of why it breaks, or a single verified derivation step. Think about what that actually means in practice: if you tried an induction approach on a problem, got three steps deep, and hit a dependency you couldn’t resolve, that is submittable. Document what you tried, where it broke down, and why the approach seemed plausible going in. The next researcher skips the dead ends you already mapped. That is real value the field has been quietly discarding for years. The assumption has always been that incomplete work is private work. LemmaTrail flips that. Incomplete but structured is exactly what collaborative math needs more of.
The six contribution types cover a wide range. A candidate claim means you have a proposed approach but haven’t verified it fully. A failed route means you followed a line of reasoning to a clear dead end and documented why. A source connection links the problem to a paper, theorem, or technique that might be relevant but hasn’t been formally connected yet. A gap review identifies a specific hole in an existing submission. A derivation is a single verified step. A next step is a concrete suggestion for where someone else could pick up. None of these require a complete proof. All of them require precision.
How to make your first LemmaTrail contribution:
- 🔍 Browse open problems in the GitHub repo
- Pick a contribution type: candidate claim, failed route, source connection, gap review, derivation, or next step
- Fill in the required fields for that type (the spec is tight but lightweight)
- Submit one atomic, checkable step, no full solution required
- 📎 The next contributor picks up from your documented stopping point
The key word in step four is atomic. One thing, clearly scoped, that someone else can independently verify without reconstructing your full context. That constraint sounds limiting but it is actually what makes the whole system work. If you document an insight, a contradiction, or a boundary condition in isolation, it stays useful even if every surrounding assumption turns out to be wrong. That is harder than it sounds when you are deep in a problem, which is exactly why the structured format matters so much.
Pro tip: The format’s strictness is the feature, not the friction. Loose collaborative math threads collapse into noise fast. Anyone who has watched a promising research thread on Discord or a forum devolve into half-stated ideas and unverifiable claims knows exactly what unstructured collaboration looks like at scale. Enforcing structure means every submission is verifiable by someone coming in cold. If it feels rigid, that is it working. The overhead of filling in required fields is low. The overhead of sorting through unstructured partial ideas left by ten different contributors is not.
The creator is specifically looking for feedback from prompt engineers on whether the format filters enough noise while staying practical to use. That framing is worth paying attention to. The question isn’t whether AI can contribute to math, it’s whether the output AI generates during problem exploration can be structured in a way that survives handoff to another researcher. If the format is too loose, the repo fills with noise. If it’s too tight, contributions dry up because the bar is too high. Getting that calibration right is genuinely hard, and prompt engineers who have built structured output pipelines have relevant intuition here. A website with LaTeX rendering and source trail visualization is on the roadmap if the project gets traction, which would make reviewing connected contributions significantly faster.
If you use AI for anything research-adjacent, this is worth 10 minutes of your attention. Browse the open problems, read one existing submission, and notice whether the format captures what you’d actually want to hand off to another researcher. That’s the feedback loop the project needs right now. 🚀
Frequently Asked Questions
Q: How is LemmaTrail different from just sharing an AI transcript or conversation?
Raw transcripts are messy and hard to follow. LemmaTrail enforces a structured format so each contribution is checkable, reusable, and actually helps someone else continue. The goal is to preserve the movement of reasoning, not just the final answer. This turns scattered explorations into a library others can build on.
Q: Do I have to solve the whole problem to contribute?
Nope. You can submit a failed route, a gap you uncovered, a derivation step, or a concrete next step. Small, checkable pieces are exactly what LemmaTrail is built for. Someone else will pick it up where you left off.
Q: What counts as a valid contribution?
LemmaTrail accepts six formats: candidate claims, failed routes, source connections, gap reviews, derivations, and concrete next steps. Each one logs a specific type of reasoning artifact. The creator is still refining the balance between being strict enough to stay useful and lightweight enough to not feel rigid.
Q: Why is this useful for people working with AI on hard problems?
When you’re using AI to explore complex reasoning, you usually get one final answer. LemmaTrail lets you log each step, dead end, and insight in a way others can actually learn from. It’s like building a searchable library of reasoning patterns instead of one-off solutions.
I built LemmaTrail, a structured format for AI-assisted math reasoning
by u/Due-Passenger-4003 in PromptEngineering