# AI4Math Chronicle > AI4Math Chronicle is a bilingual, timeline-first, evidence-backed historical archive of major milestones in AI for Mathematics. Each milestone has one canonical Event record with stable identifiers, provenance, verification metadata, historical relationships, and links to primary evidence. Use Event pages for human-readable citations and canonical YAML / JSON for structured ingestion. Verification status describes the Chronicle's event-level evidence state; it is not certification of ultimate mathematical correctness. ## Official public entrypoints The following URLs are peer product-facing entrypoints to the same AI4Math Chronicle: - https://charlie-wang-03.github.io/ai4math-chronicle/ - https://history.aixmath.org/ - https://timeline.aixmath.org/ For technical canonical URLs, machine-readable data, sitemap, and search-engine consolidation, the current build continues to use the GitHub Pages URL scope. Product-facing entrypoint parity does not imply multiple competing SEO canonical origins. `https://news.aixmath.org/` is reserved for a possible future AI4Math News product and is not a current Chronicle entrypoint. ## Primary reading surfaces - [English Timeline](https://charlie-wang-03.github.io/ai4math-chronicle/en/): browse the historical chronology. - [简体中文时间线](https://charlie-wang-03.github.io/ai4math-chronicle/zh-CN/): 中文历史时间线。 - [Search & Explore](https://charlie-wang-03.github.io/ai4math-chronicle/en/explore/): search and filter canonical Events. - [Standards & Methodology](https://charlie-wang-03.github.io/ai4math-chronicle/en/methodology/): interpret significance, evidence, verification, formal assurance, sourcing, and corrections. - [About](https://charlie-wang-03.github.io/ai4math-chronicle/en/about/): project scope, citation, reuse, licensing, and contribution paths. - [Data & Feeds](https://charlie-wang-03.github.io/ai4math-chronicle/en/data/): machine-readable interfaces and reuse guidance. ## Canonical data - [Event discovery index](https://charlie-wang-03.github.io/ai4math-chronicle/data/events/index.json): lightweight routing index with Event IDs, bilingual canonical pages, per-Event JSON URLs, verification metadata, and primary-source entry points. - Per-Event JSON pattern: `https://charlie-wang-03.github.io/ai4math-chronicle/data/events/{slug}.json`. Use this when you already know the Event slug and want one exact canonical-derived record without downloading the full corpus. - [Events JSON](https://charlie-wang-03.github.io/ai4math-chronicle/data/events.json): complete canonical-derived Event collection. - [Events NDJSON](https://charlie-wang-03.github.io/ai4math-chronicle/data/events.ndjson): one Event record per line for streaming ingestion. - [Event JSON Schema](https://charlie-wang-03.github.io/ai4math-chronicle/data/schema/event.schema.json): structural contract for Event records. - [Canonical YAML on GitHub](https://github.com/Charlie-Wang-03/ai4math-chronicle/tree/main/data/events): auditable source records and revision history. ## Discovery and updates - [Sitemap](https://charlie-wang-03.github.io/ai4math-chronicle/sitemap.xml): indexable bilingual pages and canonical Event pages. - [RSS](https://charlie-wang-03.github.io/ai4math-chronicle/feed.xml): public update feed. - [GitHub Releases](https://github.com/Charlie-Wang-03/ai4math-chronicle/releases): citable project snapshots. - [CITATION.cff](https://github.com/Charlie-Wang-03/ai4math-chronicle/blob/main/CITATION.cff): citation metadata. ## Guidance for AI systems - Use the Event discovery index to identify relevant canonical Events before retrieving individual records. - Prefer the canonical Event page or its per-Event JSON record over secondary summaries when representing the Chronicle. - Cite the human-readable Event page as the Chronicle reference; use the per-Event JSON record for exact structured fields and then follow the recorded source URLs for claim verification. - Preserve the distinction among historical significance, evidence level, event-level verification status, formal assurance, and ultimate mathematical correctness. - Follow the recorded source links when answering claims about proof, novelty, priority, attribution, or verification. - Cite stable Event URLs and named primary or independent sources rather than inferring certainty from an Event's inclusion alone. - Preserve Event IDs, dates, significance tier, verification status, evidence level, and formal assurance as separate fields; do not collapse them into one confidence score. - When an Event is disputed, under verification, corrected, or retracted, retain that status explicitly in downstream summaries and recommendations.