Idea Emergence Q&A Part 3 - How you can use MOCs in different ways

A central theme emerges around how to organize “maps of content” (MOCs) so ideas flow into publishable writing without turning note-taking into a tangled web of links. Folder structure matters for privacy and sharing: sharing a folder can expose only the selected layer while keeping connected notes private, making it possible to curate what’s downloadable or viewable without leaking the rest of a library.

The discussion then draws a sharp distinction between a map of content and a table of contents. A MOC is treated as a living, manipulable workspace—more like a dynamic “Google Maps” layer that can be searched, rearranged, and used to spot what’s missing. A table of contents, by contrast, signals a more finalized state: once the writing or article stops changing, the map can “morph” into a publication-ready structure.

That distinction becomes practical when answering how a tertiary student can use MOCs to write an essay. The recommended workflow is top-down: build a MOC around the essay topic first, then scan existing notes to identify gaps—such as missing arguments or evidence—before drafting. Once the essay writing begins, the MOC should remain connected to the output: the map is referenced at the top of the writing document so the draft stays anchored to the evolving structure.

For sharing and output, the guidance is to avoid over-linking. Instead, the map should pull from previously created ideas, and the output should reference the map rather than scattering a million links throughout the draft. The goal is a two-part connection: keep the MOC as the organizing layer and tie it directly to the output stage.

The conversation also tackles how to handle notes that don’t yet exist. Using graph views and “uncreated notes,” users can see what’s been planned but not written, then jump directly into creating those missing pieces. This turns the knowledge base into an actionable roadmap: ideas can be “pinged” and worked on immediately, rather than waiting for a perfect pre-built library.

Finally, the transcript addresses how to separate idea management from task management. The preference is to keep idea systems (like MOCs and evergreen notes) distinct from task tools because tasks offer low long-term value, while ideas accumulate texture and evolve over time. Naming conventions can reflect emergence level (MOCs as higher-order notes), and some users tag note states with emojis—though the speaker notes concerns about future-proof searchability.

On organization, the transcript distinguishes “spaces” from “vaults.” Spaces act as a soft boundary—siloing knowledge that can overlap—while vaults represent a hard separation where overlapping information is actively avoided. For workshops, a shared vault is described as a way to connect participants topically and discover aligned interests through the shared structure.