The design philosophy of Lynx is based on data storage seen in nature.
Benjamin Wilson, the designer of Lynx considers himself a hobbyist of Evolutionary Biology. It is his view that nature provides a proven design for generational data storage in the form of DNA. Lynx is improving over time to be a closer contemporary replication of this design. Lynx operates similarly with easy replication, lilliputian medium and energy cost, practically endless storage capacity and a fault tolerant encoding method that eradicates data quality concerns or drift. Logware is only an onramp method for an external data set. Eventually, like DNA, Lynx will store its own code via Logware so it can be used to resurrect itself. The DNA of Lynx will be stored within itself so it will be capable of self replication one day, like a cell. Of course the robust data set it stores will be copied with each new node, furthering the durability of its structure, like a mesh or net of fault tolerant nodes.
Long term, Lynx will be capable of extraordinary durability due to its hive-like design. An analogy would be to compare the collective work effort of honey bees against a herd of cattle. The energy required to maintain the bees is lowest, loss of a single bee is hardly noticed, capacity to tolerate change is high and the destructive output or waste from the bees is hardly measurable (e-waste). Yet the cattle are expensive to feed, output destructive gas to the environment (e-waste), not very nimble to tolerate change and expensive when a single bull is lost to disease (bad actors and hackers). In the grander view, the beehive will live longer, retain its collective data set at a far lower cost and has so many points of failure that none of them matter in any real measurable way.