Timeline: browse history
Read AI4Math chronologically. Search and lightweight refinement never reorder history, while year controls provide fast chronology jumps.
Open the timeline →About AI4Math Chronicle
A timeline-first historical archive for AI for Mathematics
AI4Math Chronicle organizes papers, formal proof artifacts, research repositories, institutional announcements, and independent corroboration into stable canonical Events so major developments are easier to discover, place in historical context, and verify against evidence.
What problem does the Chronicle solve?
The Chronicle is not a news feed, paper database, leaderboard, or Awesome List. It prioritizes historically or field-significant AI4Math events and preserves significance, AI and human contribution, sources, verification state, historical relationships, and revision history over time.
Reading model
How to use the site
The three core reading surfaces serve distinct jobs: browse history, find events, and interpret trust.
Search & Explore: find events
Use full-text search, structured multi-select facets, and sorting to locate systems, people, problems, methods, or evidence conditions.
Search & Explore →Standards & Methodology: interpret trust
Understand inclusion boundaries, H1–H3, S1–S5, E0–E4, verification states, formal assurance, uncertainty, and corrections.
Read standards & methodology →Use & contribute
Cite, reuse, and contribute
About also retains the responsibilities of the former Use & Contribute hub: research citation, machine reuse, and public maintenance.
Citation & research
Cite the Chronicle in papers, reports, teaching materials, or research projects. For reproducible work, prefer a GitHub Release snapshot or record an explicit access date.
View citation metadata →Data & AI workflows
Use JSON, NDJSON, JSON Schema, RSS, Sitemap, llms.txt, and canonical YAML for analysis, retrieval, knowledge workflows, or AI-assisted research.
Open Data & Feeds →Contribute
Submit missing events, source leads, factual corrections, verification updates, translation fixes, or website improvements through a GitHub-native, reviewable workflow.
Read the contribution guide →Open project and long-term maintenance
The website and main branch form an evolving living corpus; GitHub Releases provide more reproducible snapshots for citation. Source code uses the MIT License, while original Chronicle editorial content and data compilation use CC BY 4.0.
GitHubSource code, canonical Event data, and project history.GitHub ReleasesVersion snapshots for citation and reproducibility.CITATION.cffProject citation metadata.CC BY 4.0License for original Chronicle editorial content and data compilation.
Participate in public maintenance
Submit a source leadRecord a paper, repository, announcement, or independent analysis worth later triage.Propose a missing eventPropose a historical or field milestone that may be missing from the Chronicle.Report a factual or sourcing problemReport problems with dates, facts, sources, translations, significance, or verification information.Report a website problemReport navigation, search, filtering, rendering, accessibility, export, or build problems.
Open does not mean automatic publication
All public contributions remain subject to the existing editorial standards and human-in-the-loop review. Opening an Issue or Pull Request does not guarantee inclusion; H1 decisions, high-risk verification states, and material mathematical-correctness or priority judgments remain behind the established human gates.