Plan
PLAN.md →
The schedule — five phases of topics, in priority order, with checkboxes.
Priority follows how central each area is to the proposal: comparative-
judgement statistics and optimisation are core investigative content;
linear algebra/calculus is support for reading papers, not a goal in itself.
How to use it
Edit in place as you progress. One living document — never spawn a new
dated copy.
Resources
resources.md →
Curated pointers to books, papers, and links per topic, with chapter and
page references, plus Math Landscapes cross-references for MSC2020
classification.
How to use it
Add a resource only once you actually start using it — never
speculatively.
Study Methods
study_methods.md →
The how: binder and note-taking setup, how to read a math text,
and the three-level benchmark test (§3) that defines "have I actually
learned this" — mechanical, conceptual, application.
How to use it
Reference when starting a topic, or when deciding if you're done with
one. Rarely edited.
Topic Coverage
topic_coverage.md →
One line per topic, tracking pass/fail on Mechanical / Conceptual /
Application. The source of truth for "have I learned this" — separate
from what's scheduled (PLAN.md) or narrated
(log.md).
How to use it
Update after running the three-level benchmark test from
study_methods.md §3 — not just after reading.
Log
log.md →
Append-only weekly narrative: what got studied, what clicked, what to
revisit. Not a formal record.
How to use it
A few lines per week. Zero formatting overhead — the one low-friction
habit.
Reference Archive
reference/ →
The proposal itself (ntu_proposal_080526.md), plus a legacy
library carried over from math_wiki
(wiki-content/ — definitions, theorems, proofs, worked
examples, not converted to HTML). Its internal links to
sources//topics/ are stale; the content itself
still reads fine.
How to use it
Consult the proposal when questioning scope. Treat
wiki-content/ as a reviewable archive, not a source of new
topics.