What is atomicity? How is atomicity? Why is atomicity?

One of the popular ideas in Zettelkasten is that a single "zettel" (note) should have a single idea. What does that mean in practice though? Where should we draw the line of something being a 'single idea'?

This is, of course, a subjective & personal decision -- do what makes sense for you!

Some examples from my use case...

• Sterilization (for medical devices)... this is a yuge... this isn't even a single topic. this is a struct struct.
  • EtO Sterilization... this has some overlap with Gamma, but enough unique that it should stand alone as a struct.
    • EtO (chemical)... zettel (note)
    • EtO process overview... zettel
    • EtO residuals... zettel
    • Product design considerations for EtO... zettel
  • Gamma Sterilization... struct
  • Steam Sterilization... quite different from either EtO or gamma -- struct
    • Sterilization process... zettel
    • Product/packaging design... zettel
    • Validation... zettel
    • Definitions... zettel
    • Link to Reusable Devices which is its own rabbit hole struct
    • Accumulated Lethality as basis for steam sterilization... the rare "single idea" zettel.
  • Microbiological topics... this applies to all of the modalities, but it's also a big topic, another struct.
    • Test of sterility... zettel

My idea of 'one idea' might still be broad, but I asked myself.. what is the purpose of atomicity? Besides that Sascha and Christian said to keep things atomic...

For this type of (typically technical reference) information I want to...

• Find information I need
• Not get overwhelmed
• Be able to connect and re-use ideas where applicable

And so this is the local minima I find myself in.

Articulating one thought as clearly as possible (Dan Sheffler)

• R6, "One Thought Per Note; Dan Sheffler"
• To Dan, atomicity means writing one thought as clearly as possible, really articulating the idea, to give himself a mental hook where he can now attach other ideas & pieces of supporting information.
• This helps us figure out "where do I put this particular chunk of information?" -- Is there already a struct or a zettel that explores this particular thing/idea that I can expand upon, or do I just make a new one?
• On first draft of this zettel I was reminded of (internal note) 03312007361_thinking_by_writing in that the end result of having some text in a file, however concise & cogent, is only part of the benefit; The remainder is from having done the thinking and thereby establishing the nets in your brain to match the text on the page.