An MOC is just a note — a very special type of note. It uses proximity effectively and acts like a tag and a non-exclusive folder at the same time. - Tag-like: MOCs group the links of associated notes in a non-exclusive way. (The notes themselves live freely elsewhere.) - Folder-like: MOCs assemble notes in a tightly-packed grouping. - Proximity: MOCs grant you the ability to deliberately position each note in relation to the other notes. > In this way, MOCs don’t limit access, they **curate** it — while keeping your notes free. Using MOCs is like being in your own warehouse full of workbenches, where each workbench contains a selection of highly curated index cards for you to engage with. Another way to consider MOCs is through emergence. > MOCs are Evergreen notes, just at the next level of emergence (Emergence Level 3). In an MOC, the party is always happening. It’s the “room where it happens.” Individual notes can “shadow-clone” themselves and essentially be in multiple parties simultaneous — interacting and developing complexity from each party at the same time! _Q: How do MOCs compare to TOCs (Table of Contents)?_ A: Whereas MOCs are fluid, TOCs are rigid. This is by design. A table of contents is for assembling a specific and linear order. MOCs serve much broader purposes. Oftentimes an MOC can morph into a TOC as a project starts to finalize. --- ### Question In your own notes, write out the answers to these questions? _What do you want to get out of MOCs? How are you currently using them? What questions do you have about them?_ --- ### Training Exercise Make a new note. Put at least 5 links in it. Shuffle the links around. That’s a higher-order note. That’s an MOC!