Pacheco-Vega defines a "combined" or "content index card" or one might say a content note as a one with "direct quotations, draft notes and ideas, conceptual diagrams, etc. that are associated with" the work in question. These seem similar to Ahrens' fleeting notes, though seem a bit more fleshed out.

Content addressing is when a piece of content has its own permanent address, a URI. Many copies may exist of the content, hosted by many in the network, all copies have the same address. Whoever is best situated to serve you a copy, does so. It makes the servers interchangeable. My blogposts have a canonical fixed address, but it's tied to a specific domain and only found on 1 server (except when using a CDN).

IPFS starts from content addressing.

Content addressing, assuming the intention 'protocol for thought' here, does match with atomic notes type of pkm systems. All my notes have unique names that could as human readable names map to CIDs. CIDs do change when the content changes, so there's a mismatch with the concept of 'permanent notes' that are permanent in name/location yet have slowly evolving content.

Dan Allosso's definition of a point note.

This is roughly equivalent to permanent notes or evergreen notes in Ahrens or Matuschak's frameworks respectively. Somehow I like what seems like a broader feel here, thought the name

Does this version contain within it the idea of growth or evolution over time? Evergreen note in Matuschak's version does, though the word evergreen stemming from the journalism space would indicate an idea that doesn't evolve over time but is simply reusable or republishable with little or no work. The linguistic link to evergreen articles in the journalism space creates cognitive dissonance for me in calling notes evergreen. Evergreen connotes reusability, which is useful, but ideas should have the ability to evolve and procreate with other ideas.