Domain Atlas

Choose the territory by the question you are trying to answer

Every domain is a route into the same learning loop: intuition, math, code, interactive evidence, and AI-assisted repair when the idea gets slippery.

84 concepts63 published notebooks71 interactive demos
01Foundationsgeometry, probability, calculus
02Mechanicsnetworks, attention, generation
03Systemsscaling, efficiency, decoding
04Frontiersalignment, interpretation, causality
AI companionask, test, repair

Reader Lenses

One atlas, different depths of use.

Learner

A guided route through prerequisites, notation, code, and demos.

Start from a path, predict the demo, then ask the companion to repair the exact gap.

Start foundations
Researcher

A quick way to inspect the mechanism, assumptions, and executable witness.

Use concept pages as small, testable models before jumping back to papers or experiments.

Inspect a bridge
Professor

A teachable sequence with visual hooks, derivation checkpoints, and failure regimes.

Use the same page as a lecture spine: intuition first, then math, code, and manipulation.

Open a lesson

Choose By Need

The same atlas should support first contact, research recall, and teaching prep.

01 / Foundations

I need the math underneath the model.

Start here when notation, geometry, probability, or optimization is the blocker.

02 / Model Mechanics

I want to see how the architecture actually behaves.

Move here once the primitives are clear enough to explain a network component.

03 / Systems & Practice

I care about how these ideas run at scale.

Use this band when correctness, latency, memory, and serving constraints matter.

04 / Frontier Bridges

I am connecting the atlas to open research questions.

Use these bridges when the same mathematics reappears as alignment, interpretability, or causal structure.