##### Special aspects of MOCs - non-destructive (the notes that are linked within are not affected) - non-limiting (you can create as many variations of “structure” as you want) - non-exclusive (MOCs don’t limit discoverability) - fluid (they are flexible and can form to whatever your purposes are) - coexisting (MOCs don’t impede other MOCs) - heterarchial (there is no hard-coded, rigid top-down structure) - augment-able (you can use MOCs to augment your viewpoint of your library) - overlapping (MOCs can link to the same notes, no big deal) - neighborly (MOCs are there when you need them; but they stay out of the way when you don’t—and your base notes are still just as usable) - delete-able (you can delete MOCs and your notes remain unaltered) - you’ve lost _value_, but you haven’t lost _information_ --- ### Transcript Fluid frameworks are non-rigid, highly-flexible organizing structures that you can use as needed. When we talk about fluid frameworks in the “Linking Your Thinking” System, we’re mainly referring to higher-order notes like MOCs and the Home note. _Fluid frameworks are not mutually exclusive._ That means a note with its link in an MOC, doesn’t exclusively live in the MOC note. A note can live and link freely. A note can be discovered in as many places as it’s referenced. These are the fundamentals of linking notes together. But now with higher-order notes like MOCs, we can fluidly add any structure, at any time, and this structure is: - non-destructive (the notes that are linked within are not affected) - non-limiting (you can create as many variations of “structure” as you want) - non-exclusive (MOCs don’t limit discoverability) - fluid (they are flexible and can form to whatever your purposes are) - coexisting (MOCs don’t impede other MOCs) - heterarchial (there is no hard-coded, rigid top-down structure) - augment-able (you can use MOCs to augment your viewpoint of your library) - overlapping (MOCs can link to the same notes, no big deal) - neighborly (MOCs are there when you need them; but they stay out of the way when you don’t—and your base notes are still just as usable) - delete-able (you can delete MOCs and your notes remain unaltered) - you’ve lost _value_, but you haven’t lost _information_ Wow…So a fluid framework is a non-essential supporting structure. Whereas, a typical framework—like a folder—is an essential supporting structure. Delete the folder, and you delete the files within. And that’s because folders are not fluid; they are a rigid framework. They reduce the number of ways you have to access the notes trapped within. Now it’s worth noting, we do have Global Search, and we can link to notes within folders…so that’s better than it used to be…but there is still no removing the friction that comes from having to twirl down folders X, Y, and Z, just to get to Idea Omega.) So even though folders alone are rigid, if you expertly use Fluid Frameworks—i.e. HIGHER-ORDER NOTES—to support your linked knowledge, then you can also work back in some smart applications of folders. That’s why we’re here: to become skilled and confident with how we are deploying the tools that we have to structure our notes in the best way possible. So with that as our segue, let’s really explore how we can become experts at making the right relationships between notes.