The LYT Framework - Q&A Part 2: Note Size, Maps of Content, and Evergreen Notes

Evergreen notes work best when they’re treated as “stars” in a personal knowledge system—clear, opinionated anchors that connect to broader concepts—while maps of content (MOCs) provide the structure that turns scattered notes into answers. In the Q&A, the emphasis lands on building a pre-developed skeleton of ideas before lectures or reading, then filling in details as new information arrives. For college use, that means creating MOCs in advance for major topics, then branching into chapter- or section-level notes during study so the system is already in place when questions start forming.

A key practical distinction is how note “atomicity” should be handled. The approach aims for evergreen notes to be mostly atomic, but “atomic” isn’t treated as a universal rule—what counts as a single unit depends on the writer’s intent. Some notes should be broad and concept-centered, while others should be specific and opinionated. The library becomes a hybrid: evergreen notes with sharp, standalone statements, paired with concept or manual notes that lean more factual and less argumentative. This hybrid design prevents the system from becoming either overly fragmented (too many tiny atomic claims) or overly vague (notes that don’t sharpen thinking).

The system’s architecture is described in five levels of emergence. Notes sit at the base, then zettels (linked clusters) form higher structure. Maps of content pull related notes together, and maps link to other maps at the next stage, culminating in a home note that acts as the entry point. The practical payoff is that users don’t just link notes to each other; they link maps to maps, so navigation and retrieval become more like following a reasoning path than searching for keywords.

Breadcrumbs and linking strategy get attention as well. Tags are treated as weaker connections—useful for “we’re both interested in the same stuff”—but not as strong as “family links” that reflect direct conceptual relationships. Breadcrumbs, by contrast, are manually placed navigation links that move one level up, keeping the user oriented without clutter. The example workflow shows clicking from a lower map (like “habits”) back to the relevant home map instantly, with the links positioned so the content stays visually and cognitively “above” where it’s needed.

On workflow, there’s no fixed daily routine for evergreen notes. Creation happens in bursts driven by inspiration from reading or encounters. When inspiration strikes, the method is to assemble a temporary map of content first—collecting note links into a working structure—then refine by rearranging links and promoting the most relevant connections into clearer, higher-level placements.

Finally, the discussion addresses scaling and tooling concerns. Markdown keeps files small, with images being the main size driver; slowdown tends to appear beyond very large note counts, though that’s expected to improve over time. Exporting and future-proofing links are acknowledged as valid concerns, but the approach prioritizes building the system now—especially for a capstone project that will generate MOCs from a study of Cosmos (the series by Neil deGrasse Tyson and Carl Sagan)—rather than optimizing for migration later.