In development

Daily math practice that leaves a map behind

MathDaily is being built around one idea: five to fifteen minutes a day should leave behind a map of what you know and how it connects — not a streak.

There is nothing to sign into yet. No accounts, no daily sessions, no lessons served to a browser. What exists today is the part everything else has to stand on: the graph, and the mathematics written onto it. Both are described below, with numbers counted from the repository rather than typed into this page.

Skip to the early-access list

The map, as it currently stands

The real prerequisite graph for single-variable calculus: 69 concepts, 152 prerequisite links, 14 layers from the shallowest to the deepest. No progress is shown on it, because there is no one whose progress it could be.

Content packcalculus-single-variable@0.1.0

Why it is being built this way

Three kinds of product already exist. Each is missing the same thing in a different place.

Course platforms
Progress is a percentage of video watched. That measures how much went past, not what you can do — and once you fall behind there is no way back in except the beginning.
Solvers and answer apps
They settle one question and leave nothing behind. Nothing accumulates.
Gamified apps
Enjoyable, but the structure stays invisible. Where you are, what is missing underneath, and what you could sensibly learn next are never shown to you.

The tree is the product, not the decoration

The plan is to put your own graph on the first screen: lit for what holds, dim for what is slipping, outlined for what your prerequisites already allow. One object that is the progress bar, the map and the record at once, rather than three widgets that disagree.

Today: the graph and the renderer exist. The learner state that would colour them does not.

Start where you actually are

Someone five years into a job who wants probability should not have to begin at what a fraction is, and should not be dropped into measure theory either. The way in is designed as a short placement that walks the prerequisite chain by halving, and hands back a starting point rather than a score.

Today: the placement logic is written as a pure function with tests. There is no screen for it.

How you think is the second axis

Concepts run in one direction. Reduction, invariants, symmetry, limiting processes, construction, proof by contradiction — the moves themselves run in the other. Each fragment carries exactly one thinking tag, so getting better at mathematics becomes a second thing that can be counted instead of a feeling.

Today: 13 tags are defined, each with a written rationale and worked examples. 48 of the 69 concepts carry at least one; the rest are deliberately untagged, because a label on everything means nothing.

Review is the default, not a feature you remember to use

Strength decays, so the tree dims on its own. A day is meant to be one new fragment plus whatever came due, which means you never have to decide what to revise — and coming back after three weeks away costs you nothing worse than a slightly darker tree.

Today: the scheduling rules are written and tested. They act on concepts rather than flashcards, so one wrong answer dents a concept instead of resetting it.

Where this stands

The honest version. Every number below is counted from the content in this repository when the page is built.

Exists today

  • A prerequisite graph for single-variable calculus: 69 concepts, 152 prerequisite links, 14 layers deep. Every link is a mathematical claim, and two independently written checkers agree the graph is acyclic and that depth increases across every edge.
  • 276 misconceptions recorded alongside the concepts. They are not commentary — they become the wrong answers in the questions, so an invented one produces a worthless question.
  • 6 entry-layer fragments written, 56 minutes of reading in total. Each was drafted by one model and then checked by a different one, and the 64 checkable mathematical statements in them were verified one at a time.
  • 13 thinking tags, each with a rationale and worked examples of the move it names.
  • A scheduler that decays strength per concept, and the readiness rule that decides when a concept is open. Both are pure functions, both have tests.
  • All of it in this repository as versioned files. It can be diffed, reviewed and rolled back, and no language model writes to the database at runtime.

Does not exist yet

  • Any route from an email address to a lesson. There is no account, no daily session, and no content served to a browser.
  • A real tree. The knowledge tree renders today only on an internal preview page, from a learner we invented so that all four node states could be looked at. Nothing is stored for anybody.
  • Anything to buy. There is no price and nothing is on sale.

Who it is being built for

At school

Keeping up with what is being taught this term, and quietly repairing whatever is missing underneath it.

At university

Calculus, linear algebra, probability — where working backwards usually turns up one shaky piece of secondary-school algebra holding everything else up.

Changing field

Enough probability and linear algebra to do the work, reached by naming the destination and pulling the prerequisite chain backwards from it.

For its own sake

No exam and no deadline. The thinking axis is a perfectly good way to walk through it.

If your clearest memory of mathematics is being told you were slow at it: the first fragment written for this product is about fractions, negatives and where a rule stops applying. That was not an accident.

Early access

One message, when there is something you can actually use. It is not a newsletter and there is nothing to read in the meantime.

We keep the address and which language this page was in. Nothing else, and it is not sold or shared. Privacy policy