Math / Structure
Math is the structure under the surface.
This route now branches in three directions. One branch is pure math made approachable through intuition-first pages on topology, symmetry, combinatorics, number theory, trigonometry, calculus, differential equations, field theory, category theory, and complexity. A second branch keeps the math honest inside shared systems through scale intuition and statistical analysis. The third branch stays close to the rest of the site’s software and design work: algorithm visualization, geometry, lattices, renderers, schedulers, and parsers. The point is not to force everything into one theory. The point is to keep the structural disciplines close enough that they can inform each other, especially when too many ideas are arriving at once and you need a calmer surface for pattern recognition. These pages are also part of a larger teaching goal: if authors are going to approach computation, ebooks, or lore surfaces, the structure has to feel less hostile first.
Ground Abstraction In Something You Can Taste Or Touch
A math idea becomes easier to keep when it lands in a sensory process. Use these cards as prompt handles: plain structure first, material image second, concrete experiment third.
Graph
Nodes are ingredients. Edges are substitutions, affinities, allergies, or route choices.
Try it as a bean stew map: black garlic, beans, greens, acid, starch, and three alternate paths for brightness.
Gradient
A gradient is a direction of change. In cooking, it is the path of more acid, less heat, deeper roast, or longer rest.
Try it on miso-maple carrots: salt, sweet, acid, heat, and char move one notch at a time.
Invariant
An invariant is what survives transformation. A comfort bowl can change cuisine, season, and garnish while keeping the same care structure.
Try grain, protein, bright vegetable, sauce, crunch, and warmth as the stable pattern.
State Machine
Prep, inoculate, wait, feed, taste, store, serve. Each state allows different actions and different risks.
Try it with sourdough, kimchi, yogurt, or a route draft that needs time before promotion.
Math Map
These are not separate silos. They are recurring structural lenses that show up in different parts of the site and codebase, from the parser map and renderers to category-theory composition, number-theory handles, unit-circle projection, rate-versus-area reasoning, and local direction fields.
How These Math Visuals Want To Be Read
When a math page feels abstract, it usually helps to ask the same four questions. What is changing? What stays invariant? What gets identified or collapsed? Where does this picture point next? Those questions are the public-facing semantics for the diagrams on this site, and they are also the kind of metaphor scaffolding that could later feed lore.land if computation starts being narrated as a more universal kind of magic. They are useful not only for engineers, but for authors who need the structure behind a system before they can turn it into story, lore, or ebook form. The newer trigonometry, calculus, and differential-equations pages reuse that same contract.
What changes
Track the legal move first: a residue travels, a curve steepens, a point deforms, or a transformation acts on a shape.
see: modular clockWhat stays invariant
The most useful diagrams reveal what survives the motion: a modulus, a composite result, an orbit pattern, or a structural law.
see: commuting squareWhat gets identified
Many fields become friendly once you notice where different-looking cases collapse into one equivalence class or one shared bottleneck.
see: prime fieldsWhere it leads next
These are not static posters. Each visual is meant to hand you off to another route: parser budgets, field extensions, topology handles, or blog-sized explanations later.
see: growth curvesThe same four questions cue attention on every math route, so the visitor does not have to rediscover what to look for each time a new diagram appears.
Short verbal anchors and portable diagrams work together here. The prose names the move while the picture lets the structure stay visible long enough to reason with it.
The reading grammar repeats across pure math and software-adjacent routes, so the learner practices recalling one lens and applying it to a new family of problems.
Pure Math Routes
These pages are deliberately more textbook-like than the older route stubs. They use familiar pictures, internal anchors, and short diagrams so you can build intuition before worrying about formalism. Number theory, trigonometry, calculus, differential equations, and category theory include portable interactive diagrams, and the newer routes cross-reference the parser field guide and software pages when the ideas touch implementation. The shared reading grammar is simple: notice the move, notice the invariant, notice the collapse, then follow the neighboring route. Small continuation stubs for vector calculus and numerical methods keep the next studies visible without pretending the full field guide is done.
Topology
Start with rubber-sheet intuition and learn what topology remembers when exact measurement is allowed to drift.
route: Topology intuitionSymmetry
See algebra as a family of legal motions, starting from rotations and reflections that already feel visually familiar.
route: Symmetry intuitionCombinatorics
Translate counting questions into paths, partitions, and graphs so finite structure becomes something you can actually see.
route: Combinatorics intuitionNumber Theory
See arithmetic as a texture of divisibility and recurrence, with an interactive modular clock for comparing prime and composite behavior before jumping into prime fields.
route: Modular clockTrigonometry
Turn rotation into coordinates, phase, and reuse rules through a unit-circle lab that makes sine, cosine, and tangent share one picture.
route: Unit circle labCalculus
Read one curve two ways: local slope for immediate tendency and accumulated area for historical consequence.
route: Rate and area labDifferential Equations
Keep change laws visible through slope fields, initial conditions, and solution families instead of treating the final formula as the only event.
route: Slope field labField Theory
Study arithmetic habitats where inverses behave cleanly, beginning with prime fields and growing outward into extensions that later rhyme with structure-preserving maps.
route: Prime fieldsCategory Theory
Make abstraction feel lively through commuting squares, process equivalence, and parser-friendly composition thinking.
route: Commuting squareComplexity
Treat complexity as the budgeting discipline behind parser experiments, memoization, reductions, and memory tradeoffs.
route: Parser budgetsReference Studies
These studies are useful because they show repetition, volume, projection, and change over time without needing formal notation first. They pair well with the counting map, topology diagrams, and renderer route.
Software-Adjacent Routes
These remain useful if you want the places where mathematical thinking touches rendering, parsing, scheduling, and the rest of the site’s technical practice. If you arrived here through category theory or complexity, this is the software-facing half of the same conversation.
Geometry
Curvature, projection, and the Poincaré disk as a way to think about infinite space inside finite surfaces.
route: Geometry modelLattices
Partial orders, joins, meets, and the math beneath type relationships and semantic maps.
route: LatticesRenderers
The bridge between abstract signal and visible surface: transforms, light, type shaping, and pipelines.
route: RenderersSchedulers
Priority, phase, and event-loop timing when math takes the form of consequence rather than shape.
route: SchedulersParsers
Grammar and tree structure as the mathematics of turning raw text into recoverable meaning, with direct ties to composition and resource budgets.
route: Parser map