Milestone map
Milestone map
3 milestones
Choose a domain and build your initial capture and processing system
2–3 weeks (system setup + first 20 notes)
A knowledge system is only as good as its capture process. Choose a domain where you want to build cumulative knowledge over time. Set up a capture workflow: a free tool for note-taking (Obsidian, Logseq, Notion, or a local text editor), a consistent tagging or naming convention, and a weekly processing block. Process your first 20 captured items (articles, book highlights, observations, or notes) into your system: each item should be in your own words, linked to at least one other item you already have, and tagged with the domain and concept type. The result is not a collection of copied quotes — it is a map of ideas you have processed.
Proof required
Submit a screenshot or export of your first 20 processed notes showing: the note is in your own words, each note has at least one link to another note, and the tagging or naming convention is consistent across all 20.
What gets checked
- Notes are in your own words — copied quotes with a source link is a bookmark collection, not a knowledge system.
- Every note links to at least one other note — isolated notes are not a knowledge system.
- The 20 notes are from at least 3 different sources — a single long book broken into 20 notes does not test the capture workflow.
Common mistakes
- Building an elaborate folder structure before adding content — the capture-first rule: add content before adding organisation.
- Notes that are long summaries of everything you read rather than single-idea atomic notes — long notes are hard to link.
- Skipping the linking step because you do not yet have enough notes to link to — start linking from note 2 onward.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Ask the student to describe the system without showing it — can they explain what a note looks like and how it connects to others?
- Pick any note at random and ask where it links to and why — tests whether linking is genuine or mechanical.
- Ask why they chose the tool they chose — tests deliberate selection over defaults.
You'll sign in first, then come straight back here.
Build to 100 notes and produce your first synthesis
6–10 weeks (building to 100 notes)
Grow your knowledge system to 100 processed notes in your chosen domain. At the 100-note point, produce your first synthesis: a 2-page written piece that draws on at least 8 different notes, arguing a non-obvious point about your domain. The synthesis must cite the source notes explicitly (by note title or link) and must be a genuine argument — not a summary of the 8 sources, but a claim that the 8 sources together allow you to make. This is the test of whether your system is producing compounded thinking.
Proof required
Submit your synthesis (2 pages, with note citations) and export 10 of the 100 notes showing the link graph at this point (screenshot of the graph view or a linked-note export demonstrating the map density).
What gets checked
- Synthesis makes a claim — 'I believe X because Y and Z' — not a summary of 8 sources.
- 8 source notes are cited by title, not by the original source — the synthesis draws on your processed notes, not directly on the original sources.
- Link graph shows real density — not 100 isolated notes with one link each.
Common mistakes
- Notes that accumulate but do not link — at 100 notes without a dense link map, the system has not been properly maintained.
- Synthesis that cites original sources rather than your own notes — the test is whether your system is the intermediary.
- Waiting until 100 notes to think about what the synthesis will be — the synthesis topic should emerge from recurring links, not be imposed at the end.
Resources
Foundationstart here
What a verifier looks for
- Ask the student what the synthesis argues — can they state the claim in one sentence?
- Ask which two notes in the system are most connected to each other and why — tests whether the link graph is meaningful.
- Ask whether the synthesis could have been written without the knowledge system — if yes, the system did not contribute.
You'll sign in first, then come straight back here.
Use your system to produce a public piece and reflect on the process
2–3 weeks (writing + publication)
Produce a public piece (blog post, essay, newsletter issue, or talk) using material from your knowledge system. The piece must draw on at least 15 notes across at least 4 weeks of system use. Publish it publicly (personal site, Substack, Medium, GitHub, or equivalent). Then write a 1-page retrospective on what the system enabled that would not have been possible without it: what connections you made, what the system surfaced that you had forgotten, and what you would change about the system after this exercise.
Proof required
Submit the public URL of your published piece and your 1-page retrospective. The retrospective must identify at least one specific connection the system surfaced that you would not have made without it.
What gets checked
- Public URL is publicly accessible — not a draft, not behind a login.
- Retrospective identifies a specific connection the system surfaced — 'the system was useful' is not specific.
- Published piece is non-trivial — a 200-word post is not sufficient to test the system's contribution.
Common mistakes
- Published piece that does not trace back to notes — the exercise requires that the system contributed to the writing.
- Retrospective that is all positive — a genuine retrospective includes what you would change.
- Publishing on a platform that requires a login to view — the piece must be publicly accessible without a paywall.
Resources
Foundationstart here
What a verifier looks for
- Read the published piece and ask the student to point to two places in it where a specific note in their system directly contributed.
- Ask what they would change about their system after this exercise.
- Ask what connection the system surfaced that surprised them.
You'll sign in first, then come straight back here.