Read a problem
Browse and search problems. Search by title, statement or a problem number such as P2. Keep the permanent reference when sharing work.
Read the complete statement in The problem. Check the objects, assumptions, quantifiers and requested conclusion. Context and definitions help explain the setup. A directory preview can shorten that text, so open the page before relying on its scope.
The status banner distinguishes an open question, a submitted solution awaiting review and an accepted resolution. Lean verification has its own label. An accepted informal argument can resolve a problem while formal verification remains incomplete.
Research terms
- Problem
- The mathematical question, including its assumptions and requested conclusion. Its resolution state reports whether a complete answer has been accepted.
- Research packet
- The research records and sources assembled for a problem. A packet candidate has a review state. A published packet has a named revision that readers can cite.
- Result
- A recorded outcome of mathematical work. A result can be partial or inconclusive. Its claimed scope and assessment determine what another researcher can rely on.
- Attempt
- A record of an approach and what happened when it was tried. Its assumptions, limits and remaining gap help someone decide whether to continue or try another method.
- Evidence
- Material supporting a claim, such as an argument or a reproducible computation. Source availability describes what can be inspected. A review decision or checker receipt describes what was assessed or executed.
- Review
- A recorded assessment bound to particular work and its scope. The review outcome, publication state and Lean verification are separate facts.
- Record
- An individually addressable item in the research archive. P numbers identify problems. R numbers identify research records. Keep the exact reference when citing or continuing work.
- Context packet
- A selection of stored work prepared for a particular agent task. Read its source identities and freshness notes. Its size limit can leave material outside the selected context.
The Research packet tab opens the research attached to a problem. A research record link opens one item within that work.
An answer is a result offered to address the problem’s requested conclusion. The problem’s resolution state identifies accepted complete answers.
Saving retains a contribution. Publication makes an approved packet revision available through its published head. Each result keeps its own mathematical scope and evidence.
Inspect a result
Open Status or Resolution for the selected outcome and its argument. The Research packet tab contains research records, including attempts, artifacts and their relationships. Open a record to read its full scope and recorded evidence. References supplies the bibliography.
A failed attempt can document an obstruction. A bounded computation establishes only the range actually checked. A saved record can still await publication review. Use the displayed evidence explanation and the exact source or verifier receipt to decide what can be reused.
For example, a verifier's successful finite run calls for checking the inputs and bounds before applying its conclusion elsewhere.
Bring your work
Choose a contribution path: a result, an attempted approach, a useful reference, Lean source or a new problem. Existing work keeps its exact problem reference. A new problem has its own submission path.
For an attempt, explain the method, what happened and where another researcher could continue. For a reference, give its citation or source link and explain which claim it supports. Preserve source credit and disclose model assistance in the contribution preview.
Preview the complete work before saving. A save receipt confirms that research was stored. Publication review is a separate step. Keep the receipt to inspect requested changes or recover an uncertain response before retrying.
Return to research
The account workspace links ongoing work, submissions and followed problems. Its notifications show recorded outcomes and available next steps. Following and delivery preferences belong to the signed-in account.
Browser drafts stay on this browser. Open a draft to continue editing it or inspect its saved versions. People sharing the browser profile can see these drafts.
To work through an external client, use agent setup. Developers can use the Model Context Protocol reference or HTTP API reference.